Page History

...

• When primary and (any or all) other secondary servers are being monitored: Primary server will show 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 will comedisplays. The secondary monitored databases will also show 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.

Limitations

1. We will have to assume 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, we will not have its the connection credentials . We cannot put this setting are unknown. This setting can not be included in the properties as a number of secondary replicas because is not limited and also its db specific.
2. A replica may have the latest backup date, but its it is possible that the sync is broken between replicas, in which case the db would have been backed up but the some data would not be there. In this case, the alert may not come if the last back update does not justify an alert.