Backup overdue Alert firing for Secondary node in AG Setup

mehmood108

Hi,

I've SQL 2014 Enterprise with 2 node AG setup. Backup (Full & Log) keep firing for secondary node which is part of AG setup. Backups are configured at AG level (primary preferred). 

It should not alert for secondary node if DB is part of AG setup.

Please advise a solution

Alex B

Hi @mehmood108,

I will need to gather the log files along with some further information from you from the SQL Monitor data repository.  I'll reach out through a support ticket to the email address used for registering with the forum.

Kind regards,
Alex

Alex B

Just updating here after the investigation internally.  

There was no issue after all, the AG had failed over and the alert was raised on the now primary node due to the backups having been taken on the former primary and it taking about 20 minutes for the former primary to come back up and be discovered as the now secondary server, where it could see the backups that had been taken on it.

Kind regards,

Alex