How do you use cloud databases? Take the survey.
Options
Backup overdue alerts incorrectly firing
deproanja
Posts: 1 New member
Once a week I get a 'Backup overdue' alert, where the last backup date was shortly before the alert fired.
For example:
Time raised: 8 Oct 2017 03:39 Time ended: 8 Oct 2017 03:49
Last full database backup before this alert was raised was at 8 Oct 2017 03:10
So it knows the last full backup was taken 29 minutes before it fired the alert, but sent it anyway.
Alert is set to notify if the backup is more than 7 days overdue.
How can I stop this from alerting incorrectly?
Indonesia Furniture Manufacturer
For example:
Time raised: 8 Oct 2017 03:39 Time ended: 8 Oct 2017 03:49
Last full database backup before this alert was raised was at 8 Oct 2017 03:10
So it knows the last full backup was taken 29 minutes before it fired the alert, but sent it anyway.
Alert is set to notify if the backup is more than 7 days overdue.
How can I stop this from alerting incorrectly?
Indonesia Furniture Manufacturer
Tagged:
Answers
Sorry you're seeing this issue with SQL Monitor. This looks like an alert that was generated over 6 years ago (2017), has this only just arrived in your alerts inbox?
Can you please advise the version of SQL Monitor you are currently running/seeing this issue with?
Tom Claringbold | Redgate Software
Have you visited our Help Center?