SP1 for dataprotection 2007 is now available, but if there are some prerequisites and known issues with Hyper-V protection:
Prerequisites:
Before protecting Hyper-V virtual machines with DPM, ensure that the following updates are installed on the target Hyper-V server:
- The customer should be running Hyper-V RTM. The corresponding Windows update is KB950050 (http://go.microsoft.com/fwlink/?LinkID=132735). HyperV Manager version should be 6.0.6001.18016.
- Install the following updates:
- KB951308 (http://go.microsoft.com/fwlink/?LinkID=132733) on each cluster node for cluster deployment.
Increased functionality and virtual machine control in the Windows Server 2008 Failover Cluster Management console for the Hyper-V role. - KB959962 (http://go.microsoft.com/fwlink/?LinkId=136583) on the Hyper-V host and the guest virtual machines. This update for Hyper-V writer is required for backing up Hyper-V VMs with DPM.
![Dd347840.note(en-us,TechNet.10).gif]()
Note KB959962 is scheduled to release in January 2009, it enables online protection of Hyper-V guest machines. Until the update is available, virtual machines can be protected by configuring them for offline backup within each machines’ Integration Components service settings. Open the Settings window for the virtual machine and select Integration Services in the left pane. Clear the check box for Backup (volume snapshot) service and click OK. If you have set the DWORD AllowOffline registry key under HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Data Protection Manager\Agent make sure the value is not zero (0). - KB960038 (http://go.microsoft.com/fwlink/?LinkId=136584) on all Hyper-V hosts. This update for Windows Server 2008 fixes a crash of the Hyper-V host server which you may experience when backups are made using Hyper-V writer.
- KB951308 (http://go.microsoft.com/fwlink/?LinkID=132733) on each cluster node for cluster deployment.
- The version of Integration Components running inside the VM should be the same as the version of Hyper-V on the host. For Hyper-V RTM it is 6.0.6001.18016.
You can confirm this in the Device Manager inside the guest VM. Under System Devices in Device Manager, right-click on the entry Hyper-V Volume Shadow Copy and choose Properties. Check the version under the Driver tab. If the version does not match, insert the integration services disk by choosing the option under the Action menu in the VM console. Install the integration components and reboot the VM.
Note Known Issues:
|
Issue |
Symptoms |
Cause |
Workaround |
Solution |
Recommendation |
|
Hyper-V server stops working when DPM runs backups on the server. |
You may experience a Stop 0x7E when you backup a server that has the Hyper-V role installed. |
This is a problem in the volsnap.sys driver when interacting with the Hyper-V VSS writer. |
N/A |
Download and install KB960038 on the Hyper-V host to solve this problem. |
We recommend that you deploy this in the next available downtime window on the Hyper-V host. |
|
Backup of Hyper-V virtual machine fails |
Hyper-V virtual machine backups (backups using child partition) fail with following error for multiple volume virtual machines: DPM encountered a retryable VSS error. (ID 30112 Details: Unknown error (0x800423f3) (0x800423F3)). |
. |
Perform an offline backup of the virtual machine. |
Download and install KB959962 on the Hyper-V host to solve this problem. |
We recommend that you install this update on all Hyper-V hosts protected by DPM. |
|
Recovery of Hyper-V virtual machine fails |
The Hyper-V Virtual Machine Management service stops when you are restoring a virtual machine. |
This issue can occur if the virtual machine is configured to use a legacy network adapter. |
Restart the Hyper-V Virtual Machine Management service. |
Download and install KB959962 on the Hyper-V host to solve this problem. Then recover the data to an alternate location. |
We recommend that you deploy this update on all Hyper-V hosts protected by DPM. |
|
Backup of the Hyper-V virtual machine fails |
Hyper-V VSS writer is in a bad state and does not identify itself to VSS anymore. The VSS application writer or the VSS provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation (ID 30111 Details: Unknown error (0×80042319) (0×80042319)). Please check that the Event Service and the VSS service are running, and check for errors associated with these services in the Application Event Log on the server hyper01.contoso.com. Please allow 10 minutes for VSS to repair itself and then retry the operation. |
This is a problem in the Hyper-V writer in Windows Server 2008. |
To get the writer back to a stable state, restart the Hyper-V Virtual Machine Management service. Perform offline backups of the virtual machines to prevent the writer from going into a bad state. |
Download and install KB959962 on the Hyper-V host to solve this problem. |
We recommend that you deploy this update on all Hyper-V hosts protected by DPM. |
Grtz,
Alexandre Verkinderen
http://scug.be/blogs