none
DPM 2012 R2 Repoting Protection Status as OK but no replica exists for the volume RRS feed

  • Question

  • 2012R2 server running 2012R2 DPM. I am using LeftHand SAN as my DPM disks for storing backups. Our production SAN is an EMC VNX5300. I have created a mount point of a LUN and attached it to the DPM server. I have attached a snapshot to the mount point. When I brought the volume online in Disk Management, it assigned it a drive letter. I removed the drive letter and connected it to a mount point in an empty folder in C:\ActiveVolumes. I am able to browse the folder and look at data in the folder without issue (except having to elevate for some of the folders when browsing through GUI). In DPM, I created a new protection group. I added the mount point path (C:\ActiveVolumes\MyMountPoint) as a member of the PG. I walked through the wizard and configured my short term and long term protection options as I have done for other jobs. I had it create the group. At the end of the process, it reported success. Based on having done this with other mount points in similar ways, I was expecting the volume to spend some hours creating its replica as it is multiple hundreds of gig in size. After less than 15 minutes, it was sitting there with a Green OK display for Protection Status. That seemed entirely to quick so I started to investigate. When I tried to create do anything, it failed. I looked in Monitoring/Failed jobs for yesterday and today. There was a failed job for the PG that said as follows:

    Type: Replica creation

    Status: Failed

    Description: The Operation failed since DPM was unable to access the file/folder \\?\Volume{GUID}\Company\Logs\Cleanup\filename.txt on dpm01.domain.pri. 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))

    There is a second error stating that No recovery point was created, either because synchronization has not occurred since the last recovery point was created, or because no changes were found during synchronization. (ID 208)

    When I check the file in question on the original source, it is fine. When I connect to the mount point on the dpm server, browsing to the location, I find that the file says it is indeed corrupt. I will open a call with EMC as well, but it is a little concerning that a single file can prevent a whole replica from being created. I also tried deleting the corrupt file and tried to synchronize again and it failed on another file in the same folder.

    Some additional stuff I noticed as different:

    In PG setup wizard, when expanding the DPM server under available members, after a few minutes, I get the following error:

    "DPM is unable to enumerate contents in <longalphanumericstring> on the protected computer dpm01.domain.pri. Recycle Bin, System Volume Information folder, non-NTFS volumes, DFS links, CDs Quorum Disk (for cluster) and other removable media cannot be protected. (ID:38)"

    Followed by the following:

    "The database of this DPM server is located on a remote instance of SQL server.

    To protect the database of this DPM server, you must install a protection agent on the computer running the remote instance of SQL server. After the protection agent is installed, open this wizard, navigate tot eh remote instance of SQL server, and select the DPM database for protection.

    Production server name: dpm01.domain.pri

    DPM SQL DB name: MSSQLSERVER

    DPM Protection agent: Not Installed"

    The above is inaccurate because I am running the SQL on the same machine as my DPM server in the default SQL instance name. I have gotten both of the above errors before when trying to backup other mount points but I was able to back up those mount points without issue.

    I also noticed a difference since I created my first mount point backup. I created two folders on the root of the C: drive. ActiveVolumes and StaticVolumes. I had attached mount points under StaticVolumes previously (c:\staticvolumes\imagefolder1, etc.) and was able to back those up without issue. When I was configuring that one, it allowed me to select to backup StaticVolumes and then it gave me a warning about mount points and did I want to back those up to. To which I replied yes, back them up. When I was configuring this one, backing up ActiveVolumes was not an option, only the mount point below it. And it never gave me the warning about mount points. I don't know if this has anything to do with this problem.

    Any assistance you can provide on figuring out why this isn't working would be much appreciated. I tried deleting the PG and starting over and got the same results. I am at a loss for how to back this up right now.

    Wednesday, October 1, 2014 3:37 PM

All replies

  • Hi,

    Not sure what you want help with.  Did you fix the underlying volume corruption issue ?  For future posts, please limit the scope to a single well defined problem so the community can assist you best.

    Please re-define a single problem statement if you still want assistance, other wise mark the post as resolved.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, October 16, 2014 7:05 PM
    Moderator
  • There wasn't any actual corruption on the real volume. The corruption was on a specific snapshot. When I replaced the snapshot, the problem still persisted. I did define a single problem. I just provided all of the information of what I experienced in trying to get to where I was. The above is still a problem though I have deleted the protection group and will try to address the problem again shortly. I was travelling for business last week and haven't had a chance to get back to it this week yet.

    Thursday, October 16, 2014 7:19 PM
  • Hi,

    OK - best I can tell then the source of the error / problem still remains on the clone volume.  Please work with LeftHand to resolve that issue and we can see what happens after that.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, October 16, 2014 7:35 PM
    Moderator