8.12 Reporting Conflicts for Duplicate Files

You should always use the merged view when creating, modifying, or deleting files in a pair. Dynamic File Services manages a file so that a single instance of it exists on either the primary or secondary location.

For information about how duplicate files can occur and how Dynamic File Services handles them, see Section 4.17, Duplicate Files in a Standard Pair.

8.12.1 Viewing Errors in the Policy Execution History

If a policy run is interrupted because one or both of the media become unavailable during the policy run, you can check the policy run history to find out which file move might not have been completed. An Invalid File Handle error is reported in the policy move log in the Statistics > Policy execution history > Files not moved > Comment field for the file. The valid file is the instance on the source location of the move.

8.12.2 Generating a Duplicate Files Report

The Pair Check utility is typically used for standard pairs to detect duplicate files that are hidden by the merged view. Duplicate files do not occur in a retention pair because the retention repository in the secondary location has a different file structure than the primary path.

To identify duplicate file conflicts, you can run a duplicate files report by using the Dynamic File Services Pair Check utility (DswPairCheck.exe). The -files option detects duplicate instances of a file that exist on the primary and secondary paths, and reports them. You must log in as a user with rights to all of the paths in the pair. For information, see Dynamic File Services Pair Check Utility in the Dynamic File Services 2.2 Client Commands and Utilities Reference.

To generate a duplicate files report:

  1. Log in to the Dynamic File Services server as a user with file system rights on the primary and secondary paths in the pair you want to manage.

    If remote shares are being used, ensure that you have sufficient access rights on the secondary locations.

  2. Open the Management Console, select the pair, then verify that the pair status is in the Idle state.

    Policies must not be running against the pair when you start the Pair Check utility. If policies are running, wait until they are done, or stop them manually. Wait until the pair status is idle before continuing.

  3. Open an Administrator Command Prompt console. Select Start > All Programs > Accessories, right-click Command Prompt, then select Run as Administrator.

  4. Change directory to go to the C:\Program Files\Dynamic File Services folder (or the folder where you installed Dynamic File Services).

  5. At the command prompt, enter:

    DswPairCheck.exe -pair="<pairname | guid>" -files [-xml="reportname"] [‑csv="reportname"]
    

    For example, to identify duplicate files in a pair named MyPair and to create an output report named myXmlReport in XML format, enter the following command:

    DswPairCheck.exe -pair="MyPair" -files -xml="myXmlReport"
    

    This command looks in the pair database for the source and target paths of the pair named MyPair. It checks for files that have same path and file name in the source and target paths. It produces a report in XML format in the myXmlReport.files.xml file.

  6. When you are prompted, enter the user name of a user with rights to all of the paths in the pair.