Troubleshooting DpmPathMerge

  • Article

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.

  1. Manually delete the existing Replica Path_temp for the specified replica.

  2. Restore the data from tape again.

  3. Run DpmPathMerge again.

Rename Replica Path to Replica Path_old.

  1. Manually delete Replica Path, and Replica Path_old if it exists.

  2. Manually rename Replica Path_temp to Replica Path.

  3. This completes the replica restoration.

Rename Replica Path_temp to Replica Path.

  1. Manually delete Replica Path_old.

  2. Manually rename Replica Path_temp to Replica Path.

  3. This completes the replica restoration.

Delete Replica Path_old.

  • Manually 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.

  1. Verify that the account you are using to run DpmPathMerge is a member of the Backup Operators or Administrators groups.

  2. In the Local Security Policy snap-in, verify that the Backup Operators and Administrators groups are granted the right to back up files and directories. This user right is located in Security Settings\Local Policies\User Rights Assignment.

  3. Run DpmPathMerge again.

  4. If the previous steps do not resolve the problem, restart the DPM server and then run DpmPathMerge again.

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.

  1. Check the application event log for SQL Server messages.

  2. Verify the presence and functionality of the SQL Server databases by using the SQL Server Enterprise Manager MMC snap-in.

  3. Restart SQL Server services.

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.

  • If you are aware of changes to the registry, revert the changes to the previous state.

  • You can attempt to resolve this problem by uninstalling DPM, using the retain data option, and then reinstalling the same version of DPM.

  • If you do not know of any changes to the registry or you are unable to restore the registry, contact Microsoft Help and Support (https://go.microsoft.com/fwlink/?linkid=45276).

Error 4218: DpmPathMerge encountered an internal error. Please try the path merge operation again.

This error can have numerous causes.

  • Verify that no users or applications are accessing the files that you are restoring, and that the DPM File Agent service (msdpmreplicaagent.exe) and the DPM service (msdpm.exe) on the DPM server are stopped, and then run DpmPathMerge again.

  • Verify that you have sufficient access to delete the original contents of the Replica Path and to move the contents of the Restored Path.

  • Verify that none of the files or directories in the hierarchy are locked or read-only, and then run DpmPathMerge again.

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:

  • You are restoring a replica where the backup hierarchy and the replica folder hierarchy do not match, and the backup was not created by using DpmBackup.

  • The backup was created by using DpmBackup and the volume GUID of the protected volume changed between the backup time and restore time.