Backup failed

A failed alert needs context before it needs action

A failed status doesn't always mean the whole backup has stopped, though it does need checking. It might be one folder, one mailbox or everything the job covers, and the alert on its own rarely says which.

What a failure like this can involve

• Expired or changed credentials.
• Storage that is full or unavailable.
• A network interruption.
• Service or licence limits.
• A protected system that was offline.
• A configuration change.
• Retention or capacity limits.
• A problem on the vendor's platform.

What we check

For in-scope backup services, we review the alert, identify the affected workload, check the connection it depends on and work towards getting normal backup operation running again.

The same review answers the questions that usually matter more than the alert itself: what's covered, who performs a restore, and whether the recovery priorities still match how your business runs.

Leave the current backup history in place

Keep existing backups, alerts and protected systems as they are until someone has checked what a reset or a removal would delete.