This article describes issues in which Data Protection Manager (DPM) filter driver can't track changes on Cluster Shared Volumes (CSV) or virtual machine (VM) configuration resource online fails due to invalid resource state in Windows Server 2012 R2. An update is available to fix these issues. Before you install this update, see the Prerequisites section.
Assume that you use Microsoft Data Protection Manager to back up Hyper-V VMs that are hosted on a CSV volume. When you restart a node in the Hyper-V cluster, the DPM replicas for those data sources become inconsistent.
The replicas become inconsistent because the DPMFilter.sys file can't track the changed blocks on the CSV volume. The reason why the tracking of blocks get corrupted is that DPMs Minifilter (and all other Minifilters) can't complete their cleanup-code before the CSV volume is unmounted on a node that is currently being restarted. The same problem occurs if you stop the cluster service on any node as this also unmounts the CSV volume on that node.
When a provider resource is being stuck in the WaitingToTerminate state because of storage or network issues, the resource group doesn't allow group online, offline, or moving because this resource group can't reach a stable state.
How to get this update
Important If you install a language pack after you install this update, you must reinstall this update. Therefore, we recommend that you install any language packs that you need before you install this update. For more information, see Add language packs to Windows.
For more information about how to download Microsoft support files, select the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
To apply this update, you don't have to make any changes to the registry.
You may have to restart the computer after you apply this update.
Update replacement information
This update doesn't replace a previously released update.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about the terminology that Microsoft uses to describe software updates.
The English (United States) version of this software update installs files that have the attributes that are listed in the following tables.
Windows Server 2012 R2
The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
6.3.960 0.18 xxx
Windows Server 2012 R2
GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.