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!
darn I thought the v2 version was a revision to the non v2 is that not correct.
Hi Tony - nope, you need both I'm afraid!
This is where I see that DPM fails. It's 6 months after R2 releases that it's even a beta, and just like the DPM 2007 there is a list of patches that all must be applied, in order, just to make it work.
Why doesn't it have a setup like Exchange, look to the internet get the latest pre-req's etc, and do all this for you so it's not a problem?
This is good feedback, and I'm sure the DPM team would want to take this on board - I agree with you, it's not an ideal scenario, however we're at RC, rather than beta, with release imminent, so the development lifecycle is almost complete, and with regards to the patches, they are not specific to DPM as such - if you look into the details of KB975354, you'll see that it's focussing on the VSS writer, which can also be used by alternative backup technologies, not just DPM.
I admit, we should make it easier, and clarify the process of installation with consise documentation, and hopefully this will come on release, with a look to getting the process as streamlined as that of Exchange in the future.
DPM 2007 was (so far!) a lot harder - just do a search for DPM rollup hotfix on the web, and you'll find a few entries!
I agree with Dave. The patches required, although not DPM specific, are for Microsoft products so this is a big downfall in my view.
They are for Microsoft products, i.e. Windows Server, yet they apply to non-Microsoft backup technologies that want to intergrate in the same was as DPM.
Whilst I can appreciate where you're coming from, I think to state that the fact that a product needs some patches to work more effectively, mean it's a downfall is a little unfair. Patching both Microsoft, and non-Microsoft technologies is part of any IT infrastructure. I would hope that most organisations would have some process around patching, and thus if considering deploying DPM 2010, with the due diligence around research and installation procedure, they would know to apply these patches to Hyper-V R2 enabled hosts, using their preferred patch mechanism they have in place for this very purpose (WSUS, SCCM etc). Would you not be worried if Microsoft stopped producing patches for a technology as soon as it RTM'd? The whole point of patches isn't just about security, it's about bug fixes that may have been missed in unique test cases, yet it's also potentially about adding slight changes to functionality to respond to customer feedback. There's no point including these hotfixes within Windows right now, as it's not going to apply to everyone, hence why you have to request the hotfix, and install it manually.
Would you apply the same level of critique to VMware patches? What about hardware firmware updates, BIOS updates, or SAN firmware updates? Would you not purchase a particular SAN because the vendor was keen to ensure it was compatible with as much other technology as possible, in an ongoing fashion, and thus push out patches to address this?
The point I'm making is, it's as much about the process/awareness of patching, as applying th patches themselves.
Not sure is this is the right place topost this.. We are having issues with DPM 2010 RTM working with 2k8 R2 Hyper-V CSV. Is there a step through guide avaliable?
We keep getting prerequisites errors, yet have installed them (in their correct order). Little info avaliable on the net too. Errors when trying to create protection group are as follows:
One or more prerequisites for protecting this data source is missing.
Ensure that the following prerequisite software is installed on all the nodes in the cluster:
Windows Server 2008 with
Knowledge Base article 948465 (http://support.microsoft.com/kb/948465)
Knowledge Base article 971394 (http://support.microsoft.com/kb/971394)
- OR -
Windows Server 2008 R2 with
Knowledge Base article 975921(http://support.microsoft.com/kb/975921)
Knowledge Base article 975354(http://support.microsoft.com/kb/975354)
If you have already installed the required prerequisite, refresh the agent status in the management tab and try again.
The best place for this question would probably be here:
http://www.microsoft.com/communities/newsgroups/list/en-us/default.aspx?dg=microsoft.public.dataprotectionmanager, however could I ask, did you reboot after installing KB975354, and then again, after installing KB975354v2?
We are using DPM 2007 w/ Sp1 and are experiencing some issues with recovery points being extremely slow on Hyper-V backups. This has just happened in the past few weeks. It is so bad DPM does not have enough time to finish all jobs in a day and most are not even being created now.
It appears to be just on Hyper-V server backups. All other recovery points are fast such as protection of C, E drives on hosts and sharepoint farms.
Hi Josh - could you provide more details? Is this Hyper-V R1 or R2? Are you using CSV's for your VMs or 1 LUN per VM? Is there anything in the event log that is standing out? Do you have the Hardware Provider installed?
If you can provide more info, we can try and figure out what it is.
ekkk ... I've got to apply these to my production farm tonight.
Wish me luck!
When I requested KB975354 all I get is Windows6.1-KB975354-v2-x64.msu. How do I get the first file?
Did you tick both boxes on the hotfix request page? There should be 2 listed, one called Fix287961 and one called Fix293742.
is there any change to KB975354? I had previously got 2 patches as detailed. But when I tried to download the hotfix today 28th Nov, it only has 1 v2 patch. That didn't work and I had trouble finding the previous Windows6.1-KB975354-x64
Hi - you know, I think they may have been rolled up into one update, as there has been a revision on the 22nd November.
Hope that helps!