Select the product you need help with
A Hyper-V update rollup is available for Windows Server 2008 R2Article ID: 975354 - View products that this article applies to. On This PageSUMMARYThis article (KB975354) provides an update rollup for various Hyper-V issues in Windows Server 2008 R2 and on Windows 7-based computers that have the Hyper-V role installed. These issues occur when you back up or restore Hyper-V virtual machines (VMs). For detailed information, see the “Symptoms,” “Cause,” and “Resolution” sections of this article. To download the fix for these issues, click the View and request hotfix downloads link that is located on the upper-left of the screen. For details about the most recent Hyper-V updates, including all the updates that were released since this update rollup, visit the following Microsoft website: List of Hyper-V updates for Windows Server 2008 R2
(http://technet.microsoft.com/en-us/library/ff394763(WS.10).aspx)
SymptomsIssue 1Consider the following scenario:
The number of reverted volumes does not match the number of volumes in the snapshot set for virtual machine "'virtual machine name' (Virtual machine ID <GUID>)" Issue 2Consider the following scenario:
Issue 3 Consider the following scenario:
Issue 4 Consider the following scenario:
CAUSEIssue 1 When a virtual machine (VM) is being backed up, the VSS writer of the server that is running Hyper-V makes a call to the guest VM to check whether any iSCSI connections exist. This call has a default time-out of 60 seconds. If this call does not return within the time limitation, the VSS writer of the server that is running Hyper-V incorrectly assumes that there is no iSCSI connection. Therefore, the backup operation fails. Issue 2 When the virtual machines (VMs) on different nodes are backed up in parallel, every node waits to become the cluster shared volume owner to create the snapshots. However, the Cluster service moves the volume owner from one node to another node immediately after a snapshot is created without waiting for post-snapshot tasks to be completed. If another node requests the same shared volume for a backup operation before the post-snapshot tasks are completed, the Cluster service changes the volume to another node. Therefore, the VSS writer that is in the previous node cannot find the cluster shared volume locally when it performs post-snapshot tasks. This behavior causes the VM backup operation to fail. Issue 3 The application backup operation in the virtual machine (VM) is incorrectly affected by the VM backup operation on the server that is running Hyper-V. Issue 4 The snapshot files are not restored successfully when you restore the virtual machine (VM). RESOLUTIONImportant This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756 Note You may still experience issue 3 after you install this hotfix. You can apply the following registry entry in a virtual machine to fix issue 3 for that virtual machine:
(http://support.microsoft.com/kb/322756/
)
How to back up and restore the registry in WindowsLocation: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Virtualization\VssRequestor
If this registry entry is created and its value is set to 1, application backup will not be affected by the virtual machine backup operation on the server that is running Hyper-V. If this registry entry does not exist, or if its value is 0, issue 3 occurs. Name: BackupType Type: REG_DWORD Value: 0 or 1 Hotfix informationAfter you install this hotfix on the Hyper-V server, you must update the Integration Components in the virtual machines. To do this, open the Virtual Machine Connection for the virtual machine in Hyper-V Manager, and then select the Insert Integration Services Setup Disk option on the Action menu.A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix. If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesTo apply this hotfix, the computer must be running one of the following operating systems:
Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfix.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Windows Server 2008 R2 and Windows 7 file information noteThe MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature. For all supported x86-based versions of Windows 7Collapse this table
For all supported x64-based versions of Windows Server 2008 R2 and of Windows7Collapse this table
For all supported Itanium-based versions of Windows Server 2008 R2Collapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: 824684
(http://support.microsoft.com/kb/824684/LN/
)
Description of the standard terminology that is used to describe Microsoft software updatesAdditional file information for Windows Server 2008 R2 and for Windows 7Additional files for all supported x86-based versions of Windows 7Collapse this table
Additional files for all supported x64-based versions of Windows Server 2008 R2 and of Windows 7Collapse this table
Additional files for all supported Itanium-based versions of Windows Server 2008 R2Collapse this table
REFERENCESFor more information about the cluster shared volumes, visit the following Microsoft website: More information about cluster shared volumes support for Hyper-V
(http://technet.microsoft.com/en-us/library/dd630633(WS.10).aspx)
PropertiesArticle ID: 975354 - Last Review: February 12, 2011 - Revision: 4.0 APPLIES TO
| Article Translations |
Back to the top
