none
Replica is inconsistent, corrupt folder on replica volume RRS feed

  • Question

  • I am receiving a critical alert, "Replica is inconsistent" when running a synchronization job for a file server. The problem appears to be that there is a corrupt folder on the replica volume on the DPM server. Excerpts from the eror message below:

    ----------------------------------

    Affected area: E:\

    Description: The replica of Volume E:\ on fileserver.example.com is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent.

    The Operation failed since DPM was unable to access the file/folder \\?\Volume{94d9cd14-3d0d-11e0-9ae2-0026b9447092}\path\to\folder\ on  backupserver.example.com. This could be due to the file/folder being corrupt or the file system on the volume being corrupt. (ID 2036 Details: The file or directory is corrupted and unreadable (0x80070570))

    More information
    Recommended action: 1) Run chkdsk on the affected volume and then run synchronization with consistency check.
    2) If running chkdsk does not solve the problem, and the server indicated above is a protected server (and not the DPM server), consider deleting this file from the source and then running synchronization with consistency check.

    ------------------------------------

    I have tried deleting the corrupt directory from the replica, but am unable to do that. I also tried renaming the folder on the source volume, which appeared to work at first, but then the errors resumed at the next synchronization job.

    Information that I have found so far indicates that the recommended action, run chkdsk on the affected volume, should in fact not be done on replica volumes.

    Any suggestions for resolving this problem?

    Tuesday, March 15, 2011 9:56 PM

Answers

  • Hi,

    You can run chkdsk on the replica volume.

    1) Under Protection tab - Locate the data source you need to run chkdsk for.

    2) Highlight the datasource, then click on the "Click to view details" for the Replica path: - and copy the path into notepad.

    It will be in the form of the below:

    PS_server.contoso.com\User data   C:\Program Files\Microsoft DPM\DPM\Volumes\Replica\Non VSS Datasource Writer\vol_571ad355-e8b0-4fd8-be1d-766ccb7002a8\e96ce814-cda8-45ea-a797-f286aacb3473\Full

    Remove the source path and only keep the Destination path C:\Program file\Microsoft DPM\DPM\Replica\... string.

    Just copy this section into buffer.  C:\Program Files\Microsoft DPM\DPM\Volumes\Replica\Non VSS Datasource Writer\vol_571ad355-e8b0-4fd8-be1d-766ccb7002a8    [This represents mounted volume path for the replica volume]


    3) Open a command prompt with administrative privilages

    4) Modify the properties of the window so it's  Screen buffer size is 9999 and it's Windows Size Width is 200.

    5) Run mountvol.exe to display volumes and associated mountpoints.

    6) Locate the Destination path C:\Program file\Microsoft DPM\DPM\Replica\... string from step two. 

       C:\Program file\Microsoft DPM\DPM\Replica\... string.

    7)  Note the \\.\volume{guid} above the path, that is the volume we need to run chkdsk against.

    Example of mountvol output.

    \\?\Volume{c7ec71b9-3d04-11df-bb0d-00248117d06e}\
        C:\Program Files\Microsoft DPM\DPM\Volumes\Replica\Non VSS Datasource Writer\vol_571ad355-e8b0-4fd8-be1d-766ccb7002a8   


    8) Now run chkdsk /f \\?\Volume{c7ec71b9-3d04-11df-bb0d-00248117d06e}  it may ask if you want to force dismount the volume, say YES.



    Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Tuesday, March 15, 2011 11:04 PM
    Moderator