Troubleshooting DpmPathMerge
Published : September 27, 2005
To troubleshoot DpmPathMerge, you must understand the steps that occur when you run that command.
When you restore replica data to the DPM server from tape, the volume contains the path of the reallocated replica (Replica Path) and the folder that contains the restored data (Restored Path). Table 6.13 illustrates the process by which DpmPathMerge restores the correct path information for data that was archived by using DpmBackup. The changes made by DpmPathMerge in each step are shown in bold format.
Table 6.13 How DpmPathMerge Works
Step |
Replica Path Name |
Restored Path Name |
---|---|---|
Starting paths upon data restore: |
C:\Program Files\Microsoft Data Protection Manager\DPM\Volumes\Replica\FS01\C-7fa3a5e6-929c-11d9-a3b7-000c76289bfb\ReplicaDir\ProtectedFolder |
C:\Program Files\Microsoft Data Protection Manager\DPM\Volumes\Replica\FS01\C-7fa3a5e6-929c-11d9-a3b7-000c76289bfb\ReplicaDir\Program Files\Microsoft Data Protection Manager\DPM\Volumes\ShadowCopy\FS01\C-7fa3a5e6-929c-11d9-a3b7-000c76289bfb\ReplicaDir\ProtectedFolder |
1. Rename Restored Path to Replica Path_temp. |
C:\Program Files\Microsoft Data Protection Manager\DPM\Volumes\Replica\FS01\C-7fa3a5e6-929c-11d9-a3b7-000c76289bfb\ReplicaDir\ProtectedFolder |
C:\Program Files\Microsoft Data Protection Manager\DPM\Volumes\Replica\FS01\C-7fa3a5e6-929c-11d9-a3b7-000c76289bfb\ReplicaDir_temp\Protected Folder |
2. Rename Replica Path to Replica Path_old. |
C:\Program Files\Microsoft Data Protection Manager\DPM\Volumes\Replica\FS01\C-7fa3a5e6-929c-11d9-a3b7-000c76289bfb\ReplicaDir_old\ProtectedFolder |
C:\Sales\Program Files\Microsoft Data Protection Manager\DPM\Volumes\ShadowCopy\FS01\C-7fa3a5e6-929c-11d9-a3b7-000c76289bfb\ReplicaDir_temp\ProtectedFolder |
3. Rename Replica Path_temp to Replica Path. |
C:\Program Files\Microsoft Data Protection Manager\DPM\Volumes\Replica\FS01\C-7fa3a5e6-929c-11d9-a3b7-000c76289bfb\ReplicaDir_old\ProtectedFolder |
C:\Program Files\Microsoft Data Protection Manager\DPM\Volumes\Replica\FS01\C-7fa3a5e6-929c-11d9-a3b7-000c76289bfb\ReplicaDir\ProtectedFolder |
4. Delete Replica Path_old. |
C:\Program Files\Microsoft Data Protection Manager\DPM\Volumes\Replica\FS01\C-7fa3a5e6-929c-11d9-a3b7-000c76289bfb\ReplicaDir\ProtectedFolder |
The restored data now has the correct path information.
Table 6.14 describes how to troubleshoot errors that can occur during the path merge process. To identify the DpmPathMerge action that failed, examine the existing folders at the destination path name and restored path name that you specified in the DpmPathmerge command.
Table 6.14 Troubleshooting Errors That Occur During the DpmPathMerge Process
DpmPathMerge internal action |
If the action fails, do this: |
---|---|
Rename Restored Path to Replica Path_temp. |
|
Rename Replica Path to Replica Path_old. |
|
Rename Replica Path_temp to Replica Path. |
|
Delete Replica Path_old. |
This completes the replica restoration. |
Table 6.15 describes how to respond to specific error messages that you might receive when you run DpmPathMerge.
Table 6.15 Responding to DpmPathMerge Error Messages
Error |
Cause |
To troubleshoot this error |
---|---|---|
Error 4211: You do not have sufficient privileges to perform this operation. |
This error occurs when you run DpmPathMerge using an account that does not have the user right to back up files and directories. |
|
Error 4216: DpmPathMerge could not query the specified database. Make sure that the SQL Server services are running with appropriate privileges. |
This error occurs because of a SQL Server exception. |
|
Error 4217: DpmPathMerge could not access the registry. Make sure that Data Protection Manager is installed correctly. |
This error occurs when DPM registry keys have been changed incorrectly or are corrupt. |
|
Error 4218: DpmPathMerge encountered an internal error. Please try the path merge operation again. |
This error can have numerous causes. |
|
Error 4219: Either because this replica was restored from a backup that was not created using the DpmBackup tool, or because the GUID of the protected volume has changed since the backup was created, DpmPathMerge cannot automatically remove extraneous path information. To ensure that this replica is consistent with the protected data, run the FsPathMerge tool to manually remove extraneous path information from the restored replica. |
This error can occur when you run DpmPathMerge in the following situations:
|
|