Synchronization failures

  • Article

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

Summary

This alert is generated when all synchronization jobs have been failing since the specified time. To help you determine whether the issue is critical, the alert specifies the number of synchronization jobs that have failed.

Causes

There are multiple causes for synchronization failures. The alert details in DPM list the error conditions and recommended action associated with the most recent synchronization failure.

Some possible causes include:

  • The replica is inconsistent with the data source.

  • The DPM server cannot communicate with a protected file server.

  • The synchronization log has run out of disk space on the file server.

  • The replica and shadow copies have run out of disk space in the DPM storage pool.

  • A recovery job was started while a synchronization job was running. Recovery jobs take priority over other DPM jobs so the synchronization job was canceled.

Resolutions

Review the alert details, determine why synchronization jobs are failing, and take the appropriate action.

  1. To determine if the synchronization failure was caused by an inconsistent replica, review all active “Replica is inconsistent” alerts. For more information on grouping alerts by type, see How to display alert details.

  2. If the replica is inconsistent, perform a manual synchronization with consistency check. For more information, see How to synchronize a replica.

To resolve communication issues between the DPM server and the file server

For information about possible causes of communication issues between the DPM server and the protected file server, see Unable to connect to DPM File Agent.

  1. Determine if the synchronization log on the file server has run out of disk space.

    • In DPM Administrator Console, click Protection on the navigation bar.

    • Select the protection group associated with the synchronization log.

    • In the Actions pane, click Modify disk allocation.

    • In the Recommended disk allocations table, click Change.

    • The Space to allocate for synchronization log box displays the current disk allocation for the synchronization log.

    • To determine if the synchronization log is running out of disk space, compare the allocated disk space with the log usage data provided in the Disk Utilization Report.

  2. To minimize the risk of synchronization failure, increase the disk space allocated for the synchronization log if the average synchronization log usage exceeds 75 percent. For more information, see How to modify disk allocation.

  1. Compare the disk space used to the disk space allocated for the associated replica and shadow copies. You can use the data in the Disk Utilization Report to help you with the comparison.

  2. If the “Disk Used” size is nearly as large as the “Disk Allocated” size, you should increase the disk space allocated for the replica. For more information, see How to modify disk allocation.

You can manually synchronize the replica or you can wait for the next scheduled synchronization to occur.

DPM automatically reports the “Synchronization failures” alert as inactive after the next successful synchronization job is completed.