This documentation is archived and is not being maintained.

Manual Replica Creation Issues

Updated: April 21, 2010

Applies To: System Center Data Protection Manager 2010

When you create a manual replica, it is critical that you retain the same directory structure and properties (time stamps and security permissions) as those for the data that you are protecting. For guidance in selecting the specific settings, consult your backup software documentation and the white papers included in the Featured Technical Content area of the DPM product site (

If the replica is created correctly, the directory structure of the ReplicaDir folder of the replica on the DPM server will map to the directory structure of the volume being protected.

The following table provides troubleshooting guidance on issues for manual replica creation.

Manual Replica Creation Issues


Issue Possible Cause Resolution

Transferring data to an incorrect directory creates an incorrect replica hierarchy.

The replica must be created in the location that is specified in the Properties pane in DPM Administrator Console when you select manual replica creation. If you transfer the data to an incorrect location, you can use FsPathMerge to move the data or you can delete the replica data and create the replica again.

If you have already started synchronization with consistency check, you need to do the following:

  • Remove the protected volume or share from the protection group and choose to delete the replica.

  • Add the volume or share to the protection group.

  • Manually create the replica again.

In the case of an incorrect replica hierarchy, synchronization with consistency check can potentially synchronize the entire replica over the network from the file server, consuming valuable network bandwidth and CPU resources.

Re-creating junction points rather than using existing junction points.

This issue occurs when you use a tape backup that was created from a DPM server. If you do not choose to use existing junction points during the restore operation, data may be restored to the incorrect path.

If this occurs, manually delete the data and the path, and then manually create the replica again.

Failing to restore security settingswhen you restore the data.

The backup of the data includes the security settings of the source data. If you restore the data from the backup without restoring the security settings, the correct access control lists (ACLs) will not be configured on the files and folders.

Wait until synchronization with consistency check completes successfully. Incorrect replica data security settings can allow nonprivileged users to have access to the data. Failure to restore the security settings also means that synchronization with consistency check will take longer to complete and transfer more data over the network.

Incorrect time stamps cause synchronization with consistency check to take longer to complete.

Changing the file and folder time stamps because of user error or by-design behavior of the backup software causes synchronization with consistency check to take a long time to complete. For example, backup software might set the time stamp of the restored files and folders to the restore time rather than using the time stamp that the files and folders had at the time of backup.

Do not set the time stamp of restored files and folders to the restore time. We recommend that you use the time stamp that the files and folders had at the time of backup.