The Backup Restore alert notifies you when its configured condition is met on SQL Server instances so you can investigate and respond.
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 Mini DBA evaluates this alert once a minute so changes are detected quickly.
This alert shows that a backup or restore is in progress. That work may be expected, but its I/O can affect other databases that share the same storage, especially when it starts during a busy period or runs much longer than normal.
Enable it when you need visibility into backup or restore activity that may compete with production workloads. Use it selectively where the schedule, duration, or shared-storage impact would require an administrator to investigate.
This alert is based on a state or event rather than a numeric threshold. Tune its schedule, scope, severity, and notification route so that the response matches the importance of the instance.
Confirm which backup or restore is running, who owns it, whether it was scheduled, and whether user workloads are being affected. Let expected recovery work continue unless the service impact justifies intervention; reschedule, throttle, or redesign unexpectedly disruptive jobs after reviewing recovery requirements.
This alert describes valid activity, so avoid routing every expected backup to an urgent channel. Scope it to important systems or investigation windows, and use scheduling or severity to distinguish routine work from unexpected or unusually long operations.