Hi, Connect. I am working on a project for a high-profile client in New York, NY using on-premises Nintex Workflow 2013 Enterprise, Nintex Forms 2013 Enterprise, and SharePoint Server 2013 Enterprise. The client is hosting their production SharePoint 2013 farm on-premises. In the event of failure, they have a secondary, DR (disaster recovery) farm hosted in Microsoft Azure running on virtual machines. The DR farm is a hot spare farm, meaning it is online 24/7 and maintained just as rigorously as the production farm. In order to achieve automatic fail-over, the SharePoint content databases are replicated asynchronously from the AlwaysOn group on-prem to the AlwaysOn group in Microsoft Azure. In Azure, the SharePoint content databases are read-only. They only become writable in a fail-over scenario. My client would like to achieve the same level of fail-over with the Nintex content databases.
The main challenge here is to keep the Nintex content databases and SharePoint content databases paired correctly and to prevent data loss and data corruption during a fail-over to the DR farm in Microsoft Azure. To address this challenge I've compiled a list of questions for the community here to discuss regarding disaster recovery for Nintex Workflow with a hot spare SharePoint farm.
Solved! Go to Solution.
In case anyone is still curious about this topic, I've posted a full summary of a successful HA/DR setup in the Tech Blog:
The answers to the questions above are:
1. Yes, but not if the Nintex configuration database is read-only. Best practice: define your database topology in Farm A before replicating everything to Farm B.
2. Use identical SQL host names (read: aliases) in PROD and DR
3. SharePoint Workflow Timer Server + IIS (you cannot allow the workflow timer service to run in the original farm or allow users to access the web sites otherwise the system may create/process workflow data)
4. Yes, but IIS can and should stay on in the DR farm. SharePoint understands the site collections are read-only and prevents users from editing items which may engage workflows.