Use the Backup Restore alert in Mini DBA to monitor Azure SQL Database instances and make this condition visible before it becomes a wider database incident.
Mini DBA describes this alert as: Backup/Restore in progress (this is valid behaviour so use of this alert is recommended to be limited to very occasional to help identify unexpectedly large IO during busy periods of the day) This can negatively effect database performance of any databases that share the same drive as the database being backed up. Can often occur at unexpected times and require better scheduling The default evaluation frequency is Minute, so the alert is intended to be close enough to operational reality for live triage.
This alert gives Mini DBA a focused signal for a condition that can affect Azure SQL Database reliability, performance, or operational visibility. It helps the team move from a general problem report to a specific metric, threshold, and investigation path.
Enable it on systems with recovery objectives and on any database where a missed backup or archive problem would require business escalation. Test and lab systems can use looser settings if they are recreated from source control or seed data.
This alert is not primarily driven by a numeric threshold in Mini DBA. Tune the schedule, scope, severity, and notification route so that the alert matches the importance of the instance. Use higher thresholds on batch-heavy, development, or intentionally bursty systems where brief pressure is expected. Use lower thresholds on latency-sensitive production systems, small instances with little headroom, and services with strict recovery or availability commitments.
Run or restart the missing backup after checking storage and job history. Confirm that restore requirements are met, clear failed schedules, and make sure backup monitoring reports the next successful run.
For recovery and replication alerts, route notifications to the people who own recovery objectives. Higher thresholds can be reasonable for reporting replicas, but production failover paths normally need tighter settings and explicit escalation.