Shadow copy failed

  • Article

Published : April 8, 2005 | Updated : August 17, 2005

Summary

This alert is generated when the most recent shadow copy jobs for the specified volume have failed. To help you determine whether the issue is critical, the alert specifies the number of shadow copy jobs that failed.

Causes

Shadow copy job failures can be caused by issues with the Volume Shadow Copy Service (VSS), by insufficient disk space allocated in the storage pool, by an inconsistent replica, or by synchronization failures.

Note

When synchronization fails for a replica, the subsequent shadow copy job also fails. A shadow copy is only created if the replica has changed since the last shadow copy.

Resolutions

Review the alert details, determine why the shadow copy jobs failed, and take the appropriate action.

  1. From the Alerts tab in the Monitoring task area, check for a “Disk threshold exceeded” alert.

  2. If a “Disk threshold exceeded” alert exists, review the details and perform the recommended action.

  1. From the Alerts tab in the Monitoring task area, check for a “Replica is inconsistent” alert.

  2. If a “Replica is inconsistent” alert exists, you must synchronize the replica with a consistency check.

  1. Investigate the pattern of synchronization job failures. For information about analyzing trends in synchronization jobs, see the Synchronization Report.

  2. Identify and resolve issues related to specific synchronization failures. For information about a specific synchronization job, review the job details in the Monitoring task area.

DPM automatically resolves this alert after the next successful shadow copy job is completed.