Troubleshooting FsPathMerge

  • Article

Published : September 27, 2005

To troubleshoot FsPathMerge, you must understand the steps that occur when you run that command.

When you restore replica data to the file server or the DPM server from tape, the FsPathMerge command will contain the path of the protected folder (Destination Path) and the folder containing the restored data (Restored Path). Table 6.10, which uses the example of data that was archived by using DpmBackup, illustrates the process by which FsPathMerge restores the correct path information to the restored data. The file name changes made by FsPathMerge in each step are shown in bold format.

Table 6.10   How FsPathMerge Works: An Example

Step

Destination Path Name

Restored Path Name

Starting paths upon data restore:

C:\Sales

C:\Sales\Program Files\Microsoft Data Protection Manager\DPM\Volumes\ShadowCopy\FS01\C-8d2a01f3-4b01-11d9-b735-806e6f6e6963\ReplicaDir\Sales\Data

1.  Rename Restored Path to Destination Path_temp.

C:\Sales

C:\Sales_temp

2.  Rename Destination Path to Destination Path_old.

C:\Sales_old

C:\Sales_temp

3.  Rename Destination Path_temp to Destination Path.

C:\Sales_old

C:\Sales

4.  Delete Destination Path_old.

  

C:\Sales

The restored data now has the correct path information.

Table 6.11 describes how to troubleshoot errors that can occur during the path merge process. To identify the FsPathMerge action that failed, examine the existing folders at the destination path name and restored path name that you specified in the FsPathmerge command. For example, using the path names in Table 6.10, if the folders C:\Sales_old and C:\Sales_temp have been created but the folder C:\Sales is missing, then you can determine that FsPathMerge failed in step 3.

Table 6.11   Troubleshooting Errors That Occur During the FsPathMerge Process

FsPathMerge internal action

If the action fails, do this:

Rename Restored Path to Destination Path_temp.

  1. Manually delete the existing Destination Path_temp.

  2. Restore the data from tape again.

  3. Run FsPathMerge again.

    Note

    If the path exceeds 255 characters, you cannot delete the path manually. Instead, run FsPathMerge with the –D switch.

Rename Destination Path to Destination Path_old.

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

  2. Manually rename Destination Path_temp to Destination Path.

  3. This completes the data restoration.

Rename Destination Path_temp to Destination Path.

  1. Manually delete Destination Path_old.

  2. Manually rename Destination Path_temp to Destination Path.

  3. This completes the data restoration.

Delete Destination Path_old.

  • Manually delete Destination Path_old.

This completes the data restoration.

Table 6.12 describes how to respond to specific error messages that you might receive when you run FsPathMerge.

Table 6.12   Responding to FsPathMerge Error Messages

Error message

Possible causes

Possible fixes

You do not have sufficient privileges to perform this operation.

This error occurs when you run FsPathMerge if you are 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 FsPathMerge 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 FsPathMerge again.

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

FsPathMerge encountered an internal error. Please try the operation again.

This error can have numerous causes. It can occur when you run FsPathMerge with the –D switch and the destination path does not exist.

  • Verify that no users or applications are accessing the files you are restoring, and then run FsPathMerge again.

  • Verify that you have sufficient access to delete the original contents of the Destination 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 FsPathMerge again.

Note

Errors generated by FsPathMerge do not display DPM error message numbers.