Using FsPathMerge to Repair Paths on a DPM Server
Typically, you only need to use FsPathMerge to repair paths when performing a restore operation from tape directly to a protected file server. However, you need to use FsPathMerge on the DPM server 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.
If the protected file server volume GUID does not change, select the root of the volume that hosts the replica volumes as the restore location of the tape backup and the data will be restored to the directory from which it was backed up.
Original backup hierarchy:
C:\Program Files\Microsoft Data Protection Manager\DPM\Volumes\Replica\FS01\C-8d2a01f3-4b01-11d9-b735-806e6f6e6963\ReplicaDir\Sales
After the protected file server volume GUID changes, the replica volume hierarchy is:
C:\Program Files\Microsoft Data Protection Manager\DPM\Volumes\Replica\FS01\C-8175ee13-a398-4029-b96c-5ad4504c77c0\ReplicaDir\Sales
When data is restored from tape, the resulting data directory on the DPM server is:
C:\Program Files\Microsoft Data Protection Manager\DPM\Volumes\Replica\FS01\C-8175ee13-a398-4029-b96c-5ad4504c77c0\ReplicaDir\Program Files\Microsoft Data Protection Manager\DPM\Volumes\Replica\FS01\C-8d2a01f3-4b01-11d9-b735-806e6f6e6963\ReplicaDir\Sales
To fix the path, run FsPathMerge as follows:
FsPathMerge.exe –FS “C:\Program Files\Microsoft Data Protection Manager\DPM\Volumes\Replica\FS01\C-8175ee13-a398-4029-b96c-5ad4504c77c0\ReplicaDir\Program Files\Microsoft Data Protection Manager\DPM\Volumes\Replica\FS01\C-8d2a01f3-4b01-11d9-b735-806e6f6e6963\ReplicaDir\Sales” “C:\Program Files\Microsoft Data Protection Manager\DPM\Volumes\Replica\FS01\C-8175ee13-a398-4029-b96c-5ad4504c77c0\ReplicaDir\Sales”
Synchronization with consistency check can now be performed.
Windows tools cannot show paths longer than 256 characters. Therefore, when using FsPathMerge to repair paths, use the backup logs to obtain the path information. For more information on path limitations, see Microsoft Knowledge Base article 177665, “Path Too Long Error Message When Exceeding MAX_PATH” (http://go.microsoft.com/fwlink/?LinkId=51995).
For more information on FsPathMerge, see “Using FsPathMerge to Repair Paths on File Servers,” earlier in this chapter.