Now we detected a problem with Nintex Workflow 2010, regarding high availability:
· To ensure high availability for our production and development SharePoint 2010 farms, we implemented a mirrored SQL server 2008 R2 infrastructure, consisting of a
- Principal SQL server,
- Mirror SQL Server (with synchronous mirroring) and a
- Witness SQl Server
as suggested by Microsoft.
SharePoint 2010 is supporting a new feature named “Database failover server”, which has not been available in SharePoint 2007. With this new feature we can specify a failover database server for all SharePoint databases, which will be used by SharePoint in case of a failure of the principal database server. In such case SharePoint can automatically switch over to the mirror database server and continues to work, after a very short delay. So users normally will not be affected by this situation.
· Now Nintex Workflow 2010 has come into the game and we detected, that Nintex Workflow 2010 obviously is not supporting this new feature of SharePoint 2010!
There seems to be no way to specify a failover database server for the Nintex database.
So in case of a failure of the principal database server SharePoint 2010 is continuing working, using the mirror database server, but Nintex Workflow fails, because Nintex Workflow cannot access it’s database anymore. Although we mirrored the Nintex database in the same manner than the SharePoint databases, Nintex Workflow seems not to know that there is a mirror database server!
So there remain a few questions we need to ask to Nintex:
· Is it true, that Nintex Workflow 2010 is not supporting this “database failover” feature of SharePoint 2010?
· Are there any plans to support this feature in near future?
· Is there any workaround we can use in the meantime?
· Can Nintex ensure high availability, when we change our high availability concept from mirrored databases to a database cluster?
Your quick answer would be highly appreciated!