Support Tip: Hyper-V hosts fail and log Event ID 5120 when being backed up - The Official System Center Data Protection Manager Team Blog - Site Home - TechNet Blogs

Support Tip: Hyper-V hosts fail and log Event ID 5120 when being backed up

Support Tip: Hyper-V hosts fail and log Event ID 5120 when being backed up

  • Comments 25
  • Likes

Michael Vargo | Senior Support Escalation Engineer

imageUPDATED 1/6/2014 – New hotfixes available

Some customers are experiencing failures on Windows Server 2012 Hyper-V hosts that utilize Cluster Shared Volumes (CSVs) when backing up virtual machines (VM’s) using System Center 2012 Data Protection Manager (DPM 2012) with Service Pack 1 (SP1) or later.

When this occurs the following error is logged on the Hyper-V hosts.

Log Name: System
Source: Microsoft-Windows-FailoverClustering
Event ID: 5120
Logged: <date/time>
Details: Cluster Shared Volume 'Volume2' ('ClusterStorage Volume 2') is no longer available on this node because of 'STATUS_CLUSTER_CSV_AUTO_PAUSE_ERROR(c0130021)'. All I/O will temporarily be queued until a path to the volume is reestablished.

You may also see the VM’s pause temporarily, go in to a paused state, shut down, see memory spikes or CSV go into a failed state on the Hyper-V hosts. Configuring serialized backups doesn't help the problem.

It has been determined that any backup product using shadow copies results in the same errors, thus this isn't necessarily a DPM 2012 issue. 

The Windows and DPM teams have released a series of fixes to address some general Cluster, CSV backup and DPM issues and are now available for download. 


KB2886362 - Hotfix for System Center 2012 SP1 Data Protection Manager (

NOTE The above fix requires a prerequisite fix:  2836751 - Description of Update Rollup 3 for System Center 2012 Service Pack 1 (


KB2878635 - Update is available that improves the resiliency of the cloud service provider in Windows Server 2012: December 2013 (

Also see KB2784261 - Recommended hotfixes and updates for Windows Server 2012-based Failover Clusters (

Michael Vargo | Senior Support Escalation Engineer | Microsoft GBS Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up:
System Center – Configuration Manager Support Team blog:
System Center – Data Protection Manager Team blog:
System Center – Orchestrator Support Team blog:
System Center – Operations Manager Team blog:
System Center – Service Manager Team blog:
System Center – Virtual Machine Manager Team blog:

Windows Intune:
WSUS Support Team blog:
The AD RMS blog:

App-V Team blog:
MED-V Team blog:
Server App-V Team blog:

The Forefront Endpoint Protection blog :
The Forefront Identity Manager blog :
The Forefront TMG blog:
The Forefront UAG blog:

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Same here. KB2878365 fixed it for us on our 2012 Cluster. Now we're 2012 R2 with DPM 2012 R2 the issue looks like it's returned. Feeling the R2 team were unaware that this was an issue in 2012.

    Also just like Boudewijn commented we have 3 CSVs and the errors only appears on one. Glad I saw this post as I was about to move 30+ machines off of that CSV, as I thought it must be bad. Now I'm thinking that wouldn't fix anything.

  • hi,
    any fix for this issue on windows 2012 r2 cluster?
    i'm experiences this issue with Veeam backup.

  • I have this issue with 3 node WS2012R2 HV cluster with one CSV and DPM2012R2.
    The workaround for me is to place all VMs on one node (the current CSV owner), turn off dynamic optimization in VMM and then backups works fine. You can try this. Please give us a feedback if it works for You too.

    I have ticket opened in Microsoft, so if i Have any sollution will publish it.

  • MS says that it's known issue with EQL Hardware Provider and are cooperating with DELL to solve this. I think I fou nd another workaround. You can distribute VMS on all nodes and have Dynami Optimization on if you limit DPM server and agents to backup only one VMs i time. You have to change/create registry key inHKLM\Software\Microsoft\Microsoft Data Protection Manager\2.0\Configuration\MaxAllowedParallelBackups. You should have there DWORD Microsoft Hyper-V and have to set it's value to 1.
    Second thing to do is to change file DsResourceLimits.xml located on DPM server in C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\bin and on the Hyper-V hosts in C:\Program Files\Microsoft Data Protection Manager\DPM\bin. Change MaxLimit value to 1 in line with job type="8": . So it shoul look like:

    My first backup off 19 VMs on 3 node cluster succeeded.