none
Synchronization fails on Windows 2012 Server RRS feed

  • Question

  • Hello, Running DPM 2012 R2, Protected computer Windows 2012 Standard

            I'm backing up only folders (19 GB) on a Windows 2012 server which also have SCCM 2012 installed on it.  The initial replica and recovery point creations are successful.   Any scheduled synchronization job scheduled after will fail.    The job display "In progress" but there is 0 MB data transferred and will remain in that stage for days until I cancel the job.  A reboot of the protected server resolves the issue temporarily where I might get a couple days of successful synchronization\recovery points but then the job will freeze again.  I have looked in the event logs and the logs in Monitoring on the DPM server and also on the protected computer but have not found any error that points to the cause.  Has anyone seen this issue?  Will be grateful if someone can point me in the right direction of troubleshooting this issue.  Thank you. 

    Wednesday, June 18, 2014 3:58 PM

All replies

  • Hi,

    It sounds like we might be stuck creating the shadow copy of the volume we're protecting.  DPM cannot transfer any data until a shadow copy is created and mounted.

    From an administrative command prompt, run this command after it gets hung again and see if a shadow copy was made shortly after the DPM job was started.

    C:\>VSSADMIN LIST SHADOWS


    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.

    Wednesday, June 18, 2014 4:39 PM
    Moderator
  • I ran VSSADMIN LIST SHADOWS on the protected computer and "No item found that satisfy the query" was the returned message.  Thanks.
    Wednesday, June 18, 2014 4:59 PM
  • Hi,

    OK - that appears to be the issue, on the protected server you can run the following to see the VSS activity to see if it gets hung while creating the snapshot for the volume.  You can look at the times when a good sync occurred and one where it was hung and see what the last request was that didn't progress.

    cd C:\Program Files\Microsoft Data Protection Manager\DPM\Temp
    find /i "CVssSnapshotRequestor:" dpmracurr.errlog >CVssSnapshotRequestor.txt
    notepad CVssSnapshotRequestor.txt


    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.

    Wednesday, June 18, 2014 6:07 PM
    Moderator
  • Not seeing any errors that stands out. Here is the log from today's synchronization job that is hung.

    2B98 2AC0 06/18 14:50:54.265 31 vsssnapshotrequestor.cpp(2078) [00000000028FD320] 123F41D6-B559-4121-A184-AA68B4359C35 NORMAL CVssSnapshotRequestor::DoFailureCleanup [00000000028FD320]
    2B98 2AC0 06/18 14:50:54.265 31 vsssnapshotrequestor.cpp(1630) [00000000028FD320] 123F41D6-B559-4121-A184-AA68B4359C35 NORMAL CVssSnapshotRequestor::ReleaseVolumesForSnapshot [00000000028FD320]
    2B98 2A40 06/18 15:05:54.409 31 vsssnapshotrequestor.cpp(119) [00000000028FD320] 123F41D6-B559-4121-A184-AA68B4359C35 NORMAL CVssSnapshotRequestor::~CVssSnapshotRequestor [00000000028FD320]
    2B98 2A40 06/18 15:05:54.410 31 vsssnapshotrequestor.cpp(2044) [00000000028FD320] 123F41D6-B559-4121-A184-AA68B4359C35 NORMAL CVssSnapshotRequestor::CleanUp [00000000028FD320]
    2B98 2A40 06/18 15:05:54.410 31 vsssnapshotrequestor.cpp(1630) [00000000028FD320] 123F41D6-B559-4121-A184-AA68B4359C35 NORMAL CVssSnapshotRequestor::ReleaseVolumesForSnapshot [00000000028FD320]

    I ran the VSSADMIN LIST WRITERS command after  I cancelled the job and this is the returned message. 

    "Waiting for response.

    These may be delayed if a shadow copy is prepared."

    Wednesday, June 18, 2014 7:31 PM