.png)
Deploying Hyper-V protection
Updated: January 15, 2013
Applies To: System Center 2012 SP1 - Data Protection Manager
This section provides information about how you can deploy Data Protection Manager (DPM) to effectively protect Hyper-V virtual machines.
Deploy DPM on a stand-alone host
In this deployment, you must have one or more virtual machines on a stand-alone host computer. You must install the protection agent on the host computer to enable protection.
Deploy DPM on a clustered host
In this deployment, the virtual machine is on a clustered host. If you use a clustered host for your virtual machines, you have to install the DPM protection agent on all the computers in the cluster.
Deploy DPM by using an SMB disk
In this deployment, the virtual machine and its storage are on different computers. You have to install the DPM protection agent on both computers – the one that hosts the virtual machine and the one that hosts the storage. DPM supports this configuration if the application server and storage server are stand-alone or clustered.
 Note |
|---|
| You must provide full-share level permissions and folder-level permissions to the application server (machine$ account) on the SMB share. |
DPM transfers the backup data from remote SMB to DPM through the server that runs Hyper-V.
Virtual Machine Live Migration – Uninterrupted data protection
In this deployment, your virtual machines are set up so that they can be migrated from one host computer to another, depending on your requirements. Windows Server 2012 supports various scenarios for Hyper-V Live Migration, such as inter-cluster migration, intra-cluster migration, migration from stand-alone to clustered computers, migration from clustered to stand-alone computers, and migration between stand-alone computers. DPM supports protection for all these scenarios even when they use remote SMB shares. DPM communicates to the Virtual Machine Manager (VMM) server to keep track of the computer on which the virtual machine is when the backup is to be performed.
DPM will continue to do express full backup for all virtual machine Live Migrations with no storage migration.
|
Note |
|---|
| The DPM server, VMM server, and Hyper-V hosts should be in the same domain. |
Users should create separate protection groups to protect virtual machines that are hosted on Windows Server 2012.
To protect this deployment, you must perform the following steps for DPM:
-
Install the DPM protection agent on all the computers that will host the virtual machine.
-
Install the VMM console on the DPM server to allow the DPM server to communicate to the VMM server.
The VMM Console should be installed on the DPM server. -
The DPMMachineName$ account should be a read-only administrator account on the VMM server.
-
Set Global Property on the DPM server for the KnownVMMServerName by using DPM Management Shell:
Set-DPMGlobalProperty -dpmservername <dpmservername> -knownvmmservers <vmmservername>.
 Important |
|---|
| Enable the DPM-VMM communication first; all virtual machines in Hyper-V hosts should be discovered first before you configure the Creating Protection Groups for Live Migration scenarios to work seamlessly. If the virtual machine was not discovered and the protection group was created before theDPM-VMM communication setup, the Live Migration scenarios will not work. The user will have to stop protection with Retain Data and re-protect the same computer. |
Ensure that Live Migration is properly enabled
-
Ensure that the service DPM-VMM Helper Service is running. If it is not running, start it. If it is, continue to the next step.
-
Open SQL Server Management Studio and connect to the instance that hosts DPMDB.
-
On DPMDB, run the following query
SELECT TOP 1000 [PropertyName] ,[PropertyValue] FROM[DPMDB].[dbo].[tbl_DLS_GlobalSetting]This query will contain a property, called KnownVMMServer. This value should be the same as the value that you provided with the Set-DPMGlobalProperty cmdlet.
-
Run the following query to validate the VMMIdentifier parameter in the PhysicalPathXML for a particular virtual machine:
select cast(PhysicalPath as XML) from tbl_IM_ProtectedObject where DataSourceId in (select datasourceid from tbl_IM_DataSource where DataSourceName like '%<VMName>%')Replace VMName with the name of the virtual machine.
Open the XML that was returned by this query and validate that the VMMIdentifier field has a value.
Reconfigure the DPM-VMM Helper Service port
-
If you want to change the default port (6070) that is used by DPM to host DPM-VMM Helper Service, open RegEdit.
-
Under
HKLM\Software\Microsoft\Microsoft Data Protection Manager\Configuration, create a 32-bit DWORD, namedDpmVmmHelperServicePort -
Write the new port number as part of this registry key.
-
Open <Install directory>\Microsoft System Center 2012\DPM\DPM\VmmHelperService\VmmHelperServiceHost.exe.config and change the port number from 6070 to the new port.
For example: <add baseAddress="net.tcp://localhost:6080/VmmHelperService/" />
-
Restart the DPMVMMHelper service.
-
Restart the DPM service.
Continue protection after you upgrade VMM
If you upgrade your VMM server, you must also upgrade the VMM Console on the DPM server to continue protection.
For more information on how to upgrade the VMM Console, see the VMM documentation.
Continue protection after upgrade DPM
If you are upgrade DPM, you must run the following command to continue protection.
Set Global Property on the DPM server for the KnownVMMServerName by using DPM Management Shell: Set-DPMGlobalProperty -dpmservername <dpmservername> -knownvmmservers <vmmservername>.
-----
For additional resources, see Information and Support for System Center 2012.
Tip: Use this query to find online documentation in the TechNet Library for System Center 2012. For instructions and examples, see Search the System Center 2012 Documentation Library.
-----
