Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Virtual machine backup operations fail in Windows Server 2008 when Hyper-V virtual machine files are saved on a volume that is mounted on a failover cluster by using a volume GUID

Virtual machine backup operations fail in Windows Server 2008 when Hyper-V virtual machine files are saved on a volume that is mounted on a failover cluster by using a volume GUID

View products that this article applies to.

Symptoms

Consider the following scenario:
  • Hyper-V virtual machine files, such as the configuration.xml file or .vhd files, are saved on a volume in Windows Server 2008.
  • This volume is mounted on a failover cluster by using a volume GUID.
  • This volume does not have a drive letter or a mount point assigned.
  • You try to back up these virtual machine files by using a backup application, such as System Center Data Protection Manager 2007.
In this scenario, the backup operations fail and the virtual machine files cannot be backed up.

Note If you use System Center Data Protection Manager 2007 to back up the virtual machine files, you may receive the following error message:

One or more volumes are missing for the following applications:
Backup Using Child Partition Shapshot\vmname (ID:3504)
Ensure that the dependant volumes for the data sources are online.

↑ Back to the top

Cause

This problem occurs because the file path is misreported in the writer metadata that is sent to the backup applications by the Hyper-V Management service (Vmms.exe). Therefore, backup applications cannot recognize the volume, and the backup operations fail.

↑ Back to the top

Resolution

Service Pack Information

To resolve this problem, obtain the latest service pack for Windows Server 2008. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
968849 How to obtain the latest service pack for Windows Server 2008

Hotfix information

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.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To install this hotfix, you must have Windows Server 2008 with Hyper-V installed.

Restart requirement

You have to restart the computer after you apply this hotfix..

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The 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 file information notes
The .manifest files and the .mum files that are installed in each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.
For all supported x64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Vmms.exe6.0.6001.222763,871,23230-Sep-200805:22x64

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

Additional file information for Windows Server 2008 and Windows Vista

Additional files for all supported x64-based versions of Windows Server 2008 and of Windows Vista
File nameAmd64_5cc2907db9c74eb808b86102a5bc72a8_31bf3856ad364e35_6.0.6001.22276_none_c47345c1ed587b42.manifest
File versionNot Applicable
File size703
Date (UTC)30-Sep-2008
Time (UTC)16:57
PlatformNot Applicable
File nameAmd64_microsoft-hyper-v-vstack-vmms_31bf3856ad364e35_6.0.6001.22276_none_92f8941d309b1f84.manifest
File versionNot Applicable
File size249,723
Date (UTC)30-Sep-2008
Time (UTC)05:58
PlatformNot Applicable
File namePackage_1_for_kb958184~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot Applicable
File size1,893
Date (UTC)30-Sep-2008
Time (UTC)16:57
PlatformNot Applicable
File namePackage_2_for_kb958184~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot Applicable
File size1,893
Date (UTC)30-Sep-2008
Time (UTC)16:57
PlatformNot Applicable
File namePackage_for_kb958184_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot Applicable
File size1,528
Date (UTC)30-Sep-2008
Time (UTC)16:57
PlatformNot Applicable
File namePackage_for_kb958184_sc~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot Applicable
File size1,430
Date (UTC)30-Sep-2008
Time (UTC)16:57
PlatformNot Applicable
File namePackage_for_kb958184_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot Applicable
File size1,532
Date (UTC)30-Sep-2008
Time (UTC)16:57
PlatformNot Applicable
File namePackage_for_kb958184_server~31bf3856ad364e35~amd64~~6.0.1.0.mum
File versionNot Applicable
File size1,438
Date (UTC)30-Sep-2008
Time (UTC)16:57
PlatformNot Applicable

↑ Back to the top

Keywords: kbhotfixserver, kbqfe, kbbug, kbfix, kbhyperv, kbautohotfix, kbclustering, kb, kbexpertiseinter

↑ Back to the top

Article Info
Article ID : 958184
Revision : 1
Created on : 1/7/2017
Published on : 10/8/2011
Exists online : False
Views : 165