Hi Gurus,
Hope you are doing well.
I've planned activity to fail-over SharePoint (SQL 2012 SP4) three node cluster Servers with AG's group configured.
We have three node cluster with synchronous commit (Automatic) between primary and secondary node and third secondary node is acting as asynchronous-commit (manual). Also there are 60 databases running with only one AG group.
Fail-over is not very simple with sharepoint databases as we had encounter lots of issues and really had bad experience in past. whenever we try to perform fail-over there are few databases in sharepoint ,which doesn't fail-over smoothly and the end result is "not syncing" and have to restore log backup and full db backup in order to run as normal.
The error seems normal
-The availability replica might be disconnected.
-The data movement might be suspended.
-The database might not be accessible.
-There might be a temporary delay issue due to network latency or the load on the primary or secondary replica.
Is there anything I need to check or any pre-requisite in AG configuration, to prevent this issue?
Anyway to avoid these above errors? what if I stuck after perform failover which is failed?
can I manually fail-over individual databases in case fail-over fails?
What's the best practice to perform clean and successful failover?
Please help me.
Regards,
Ken