That’s an acronym-filled title!
Just a quick one – If you’re currently planning, or are underway with a deployment of Data Protection Manager 2010 (RC), and you plan to protect Hyper-V R2 VMs, on Cluster Shared Volumes, DPM will tell you to install a couple of patches on the Hyper-V R2 hosts in the cluster.
The first one, is KB975921, and is specifically aimed at solving the following: “You may be unable to perform certain disk-related operations after an exception when a hardware provider tries to create a snapshot in Windows Server 2008 R2 or in Windows 7”
The second (set) is KB975354, and has the more general title of “A Hyper-V update rollup package is available for a computer that is running Windows Server 2008 R2”, but when you drill into the details, you can see that many of the fixes are aimed at VSS, backup and the like. Now, when you request, download, and extract KB975354, you’ll notice there are actually 2 patches to install. One is Windows6.1-KB975354-x64, and the other is Windows6.1-KB975354-v2-x64. It’s important that you install Windows6.1-KB975354-x64 first, and Windows6.1-KB975354-v2-x64 second. If you don’t, you’ll find that when you come to install Windows6.1-KB975354-x64 (assuming you’ve already installed the v2 patch), you’ll get a pop up message stating that ‘the update is not applicable to your system’. If you’ve got that already, uninstall the v2 patch, and install the first one, first. All being well, you should have no problems from this point forward.
One key point to note though, After 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.
Hope it doesn’t catch you out!
I installed the updated KB975354 hotfix dated 22 Nov 2010 which came in the form of a single file named 396469_intl_x64_zip, which expanded to Windows6.1-KB975354-v2-x64, aka Fix287961. There was no link in the hotfix download email for Fix293742, nor was there a checkbox to select it when requesting the download.
After installation of Windows6.1-KB975354-v2-x64 on the Hyper-V host, I still receive the error message stating I need KB975354.
When I go Management tab to update the agent i cannot, as the DPM server is also the Hyper-V server and there is no agent to refresh. I would assume a restart would have updated that anyway.
I have updated the Integration services on the Hyper-V guests, and I've restarted both host and guests. Both KB975354 and KB975921 show as being installed on the host.
Still no luck. This isn't really enthusing me with a great deal of confidence in the product.
the v1 patch is not a part of the zipped file. With just v2 patch, DPM won't backup HyperV.
So is this confirmed that Windows6.1-KB975354-v2-x64 now contains Windows6.1-KB975354-x64?
I've been tracking down an annoying issue with Backup Exec 2010 R2 and backups failing.
To be honest guys, I've been struggling to get a straight answer. I think the fix is rolled up into SP1, which is now publicly available, so it may be worthwhile utilising this if you possibly can. Ill continue to look into it but I keep coming up against brick walls which is proving frustrating.
Sup guys, i encountered the same issue in my DPM server, i was suspecting that this hotfix was included in sp1, looked for a list to confirm and yes indeed, it is already included. Spoke to a senior colleague and he had the same issue time ago, he told me it was simple to resolve, just reboot the physical server that hosts the VM you want to include in the protection group and it shall work.