DPM2012R2 - cannot backup one 2012R2 VM, VSS writers inside the VM fails RRS feed

  • Question

  • Situation:

    Two node 2012R2 Hyper-V cluster, both nodes patched up to latest state.

    Physical DPM2012R2 server, also patched up, DPM latest rollup installed and also agents updated

    One 2012R2 VM backup fails, because of the VSS writers inside the VM. When i start a system state backup from DPM, it works without any problem and after that, VSS writers are in normal state.

    After VM backup some VSS writers are in retryable or failed state.

    VM has latest integrations tools, has also the latest Windows updates. Is is a file server, with RRAS  role.

    I have tried migration the VM from one cluster node to another, same problem occurs. When i restart the VM, couple of days backup works, but then again starts failing.

    All other 2012R2 VM´s are backed up without any problem!

    When i check the logs inside VM, i found:

    "The shadow copies of volume \\?\Volume{62bb0d19-e367-11e6-80d3-00155d370a22} were aborted because the shadow copy storage volume was not present."
    "Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {74600e39-7dc5-4567-a03b-f091d6c7b092}. Routine details PostFinalCommitSnapshots({2765cc9f-f643-40f3-9218-1e880b59f16d}, 5) [hr = 0x80070002, The system cannot find the file specified.].
       Executing Asynchronous Operation

    Context:   Current State: DoSnapshotSet"

    "The shadow copies of volume \\?\Volume{42643f0d-e458-11e6-80d3-00155d370a22} were aborted because the shadow copy storage volume was not present."

    One error that occurs, is mysterious, because i do not have a J: volume on the VM.

    "The shadow copies of volume J: were aborted because the shadow copy storage volume was not present."

    When i check the Hyper-V cluster node log:

    VSS writers inside virtual machine "'' failed to perform BackupComplete to its shadow copy (VSS snapshot) set: Catastrophic failure (0x8000FFFF). (Virtual machine ID 01E25571-8F19-490D-907E-6996F03AB240)

    The description for Event ID 10150 from source Microsoft-Windows-Hyper-V-VMMS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event:


    The locale specific resource for the desired message is not present

    On the DPM error log:

    The VSS application writer or the VSS provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation. (ID 30111 Details: VssError:The writer experienced a non-transient error.  If the backup process is retried,
    the error is likely to reoccur.

    Friday, January 27, 2017 8:21 AM

All replies

  • Hi,

    "J:\" is created during backup.
    It is a mounted snapshot.

    You could try following:

    - Choose properties of the VM
    - Switch to Hadware Configuration/[...]/Integration Services
    - Uncheck "Backup" (Volume Snapshot) - Save config of vm
    - Same place - enable / check (Volume Snapshot) gain - save config.

    Make sure DPM doesn't try to backup the system during that time.

     All information is supplied without guarantee.



    My postings are provided "AS IS" with no warranties and confer no rights

    Wednesday, February 1, 2017 3:26 PM