Idea Details

SQL Server Always On Multi-site Asynchronous Replication should be recognized as normal by the sqls

Last activity 12-07-2018 04:30 PM
Alquin's profile image
08-25-2016 01:33 PM


With SQL Server Always On you can replicate both synchronously and asynchronously. When the distance between the replication is far away such as the case when you are doing multi-site replication between countries or across countries the replica databases are always going to be in the state (1) or SYNCHRONIZING never SYNCHRONIZED.

The sqlserver 5.0 probe which supports Always On monitoring does NOT recognize the SYNCHRONIZING state as OK nor does it really provide the option to recognize it as OK. As a result, when you enable monitoring you end up with alarms for all the databases that are being replicated asynchronously.



The SQL Server probe should recognize that the replica db is being asynchronously replicated and provide a means to the monitoring user to suppress alarms related to the state SYNCHRONIZING as this is NORMAL.


Reference: Multi Site Clusters for SAP on SQL Systems: Recommendations & FAQ | Running SAP Applications on the Microsoft Platform 


12-07-2018 04:30 PM

This is STILL and issue with the sqlserver v5.40 probe today. What is going on with this request?

Its 2018 and this is a standard now and we have these alert hitting our console b/c the mirrored DB is in a state of RESTORING which is normal.

"state Principal /Synchronized and is meant to be in Mirror,Synchronized /restoring state on the DR host as these Db's are mirrored here."

Has anyone figured out how to work around this?