返回
-
标题
'Availability Group Database is not Failover Ready' fired by mistake when database role is secondary. -
说明
A SQL Server agent sometimes throws false alarms for the "DBSS - Availability Group Database is not failover ready" rule -
原因
CAUSE 1
This issue can be caused by the following:
- 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.
Each of the described reason might cause an alarm that might seem false.
The warning would appear but when the DBA investigates the issue there would be no visible problem.CAUSE 2
The alarm raised does not check the database role.
-
解决办法
RESOLUTION 1
Review the following
- Check the network health on the availability group network.
- Check the network utilization (among/between the relevant servers) at the time of the warning, high utilization might cause synchronization issues that should raise the alarm even though the problem might fix itself a short while after the warning was raised.
The sync process should be 1 -2 seconds behind, which means that network failures last or more than 1-2 second and should be easy to track.RESOLUTION 2
WORKAROUND
None
STATUS
This issue was logged as FOG-207 and has been fixed in the 6.0 and higher releases of the SQL Server cartridge.
-
缺陷ID
FOG-207