Page History

Versions Compared

...

When primary and (any or all) other secondary servers are being monitored: The primary server displays the last backup date alert by checking all other secondary servers for the latest backup date of that database. If the latest backup date across that Availability Groups justifies the alert, it displays. The secondary monitored databases also display the same alert, as the latest backup date for an Availability Group across all replicas will be the same.
When only primary replica of a database is being monitored: In this scenario the alert displays after SQLDM checks the latest backup date across all replicas and if that date justifies the displayed alert.
When some secondary replica is being monitored but no primary replica: In this scenario, the alert displays after SQLDM checks the latest backup date across all replicas and if that date justifies the displayed alert.

Warning

title	Limitations

The Days since last backup alert does not work function properly for unreadable databases.
The assumption is that the connection credentials of all the replicas are the same. At this point SQLDM stores connection credentials only of the monitored servers. If a secondary replica is not monitored, the connection credentials are unknown. This setting can not be included in the properties as some secondary replicas because it is not limited and also is db specific.
A replica may have the latest backup date, but it is possible that the sync is broken between replicas, in which case the db would have been backed up but the same data would not be there. In this case, the alert may not come if the last back update does not justify an alert.

...