Alert: Policy Backup Missed

Cause:

These alerts typically occur when a scheduled backup does not start at its intended time. In most cases, this is because the previous backup task is still in progress and has not yet completed or failed.

This scenario often arises in environments with a high change rate or large volumes of data, where backup jobs take longer than expected to complete.

In the following example, we have a policy with a daily RPO where a backup is intended to start at 3:00PM everyday. Since backup 2 is taking over 24hrs, we now see that backup 3 did not yet start and will send an alert for this missed intended start time.

Symptoms

Alert Type: Backup missed

Alert Raised On:Time period when the first attempt failed

Datasource: Name of the datasource

Entity: Number of entities (click inside alert to find out individual entities)

Cause: Backup(s) failed to start due to lack of resources.

Resolution

No immediate action is required from your end. These alerts are typically the result of timing delays between backup tasks and do not necessarily indicate a failure.

Clumio actively monitors these conditions. If further action is needed or if the issue persists, our support team will investigate and escalate as appropriate.

Contact [email protected] with any questions or concerns.