Return
-
Title
Backup alarms for AlwaysOn misfire if backup performed on a secondary replica -
Description
Database "Backup - ..." alarms for AlwaysOn misfire if database backup was performed on a secondary replica. -
Resolution
That was done by design. We think backup is not required if database that is on secondary replicas.The backup collection script isn’t smart enough because it assumes the backup is being done of the primary database but users can backup either the primary or the secondary and get a good backup.Spotlight on SQL Server incorrectly raises backup alarms for the primary database because it is unaware that the backup of the secondary is sufficient for recovery purposes.In the meantime the workaround is to ignore the alarm but only for primary databases. To do this right click the alarm, select Ignore this alarm, and then select Ignore for this value only in the dialog that opens.Enhancement has bee implemented in the current release of Spotlight. Latest version of Spotlight can be downloaded from here. -
Defect ID
SOSSE-3882 -
Additional Information
11.0.x, 11.1.x, 11.2.x Eventually until then you can add a tag to all my instances in question and create alarm action to suppress the database, days since last backup alarm on those SQL instances.