SQL Server Backup Restore Alert

Start Here

Manual Home Installation Getting Started Licensing Servers Connect Database Servers Troubleshoot Connectivity Host OS Login Enable WMI Multi-Engine Settings

Console

Console Overview Enterprise View AI Assistant Execution Plans Alerts Custom Alerts Reports Settings Service Log Connectivity Log Web Log About

PostgreSQL

Overview Connection and Permissions Activity Databases Queries Waits Memory I/O Indexes Deadlocks Server Log Settings Permissions Health Checks Alerts Performance Tuning

MySQL/MariaDB

Overview Connection and Permissions Activity Databases Queries Memory I/O InnoDB Permissions Deadlocks Health Checks Alerts Performance Tuning

Oracle

Overview Connection and Permissions Activity Databases Queries Waits Memory Health Checks Alerts Performance Tuning

Settings And Integrations

Security SQL Options Email Server Alert Recipients Recipient Groups Server Groups Cloud Providers Web Proxy Slack Microsoft Teams PagerDuty Jira Performance Logging AI Provider MCP Server

Legacy Documentation

Use the Backup Restore alert in Mini DBA to monitor SQL Server instances and make this condition visible before it becomes a wider database incident.

Screenshot pending: Mini DBA SQL Server Backup Restore alert screenshot placeholder

Alert Summary

Platform: SQL Server
Alert category: Disk
Default enabled: false
Default evaluation frequency: Minute

What Mini DBA Checks

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.

Why This Alert Is Helpful

This alert gives Mini DBA a focused signal for a condition that can affect SQL Server reliability, performance, or operational visibility. It helps the team move from a general problem report to a specific metric, threshold, and investigation path.

When To Enable It

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.

Threshold Guidance

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.

Remediation For An Active Alert

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.

Investigation Workflow

Confirm the alert is still active and note the first seen time, affected instance, and severity.
Review the affected disk, tablespace, log stream, backup job, retention setting, and recent growth pattern in Mini DBA before changing configuration or ending sessions.
Compare the current value with the normal baseline for the same time of day or maintenance window.
Record the cause, corrective action, and whether thresholds or routing should be adjusted after the incident.

Avoiding Alert Noise

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.