Administrator Guide

Determining whether to recover or rebuild
If you have trouble with a DPM server, you can either perform DPM recovery or you can rebuild the DPM server. Use the following steps to
determine which method to choose.
1 Log on to the backup host (or browse through a network connection), and do the following:
a Browse to H:\<DPMVMName>\Virtual Hard Disks.
b For each DPM VM, verify that there is a <Prex>DPM0#-Scratch VHD le listed.
2 On the Console VM, in the VMM console, check the DPM VM properties.
a In the VMs and Services workspace, right-click the DPM VM, click Properties, and then click the Hardware Conguration tab.
b Under Bus Conguration, click each disk to see the locations of the backup VHDs. In the path of the VHDs, look for names in
the format <
DPMName
>Backup#.vhdx. There should be 20 (unless you added more).
3 If all VHDs exist, try to recover DPM.
4 If the disks are not intact, or you tried recovery and it was unsuccessful, rebuild the DPM server.
Recovering a DPM server
If you determine recovery of the DPM server is required, do the following:
1 Remove the host from VMM.
a In the VMM console, open the VMs and Services workspace.
b Under the All Hosts host group, remove the backup host on which the DPM VM resides.
2 Remove the corrupted DPM VM from Operations Manager.
a Open the Operations Console.
b In the Administration workspace, expand Device Management > Agent Managed.
c Right-click the corrupted DPM server, and then click Delete.
3 On the Console VM, open Hyper-V Manager and connect to the backup host.
4 Delete the corrupted DPM VM.
5 Log on to the backup host on which the DPM server resides.
6 From a command prompt, change directories to D:\<DPMName>\Virtual Hard Disks, and delete all the VHDs in this folder.
7 At a command prompt, run the following commands to enable the default local Administrator account, and to make sure the password
is set correctly. For this procedure, this account must have a specic password assigned:
net user administrator /active:yes
net user administrator pass2015@MSPCS
8 Log o, and then back on to the Console VM as the default local Administrator account with the password pass2015@MSPCS.
9 Update the manifest .XML le for redeployment.
a Open the .XML le at C:\Program Files\Microsoft Cloud Solutions\DeployDriver\Manifests\DeploymentManifest.xml.
b Update the backup host conguration. Search for the backup host name in the .xml le, locate the name of the backup host (for
example, S20B01) in the <BackupConguration> section of the le, and change the DeploymentStatus to "DomainJoined". For
example:
<BackupConfiguration>
<Nodes>
<Node Name="S20B01" DeploymentStatus="DomainJoined" ConfigurationID="828bc360-fd65-4304-
bc50-81ea4027ad7f" Password="" SerialNumber="22PGD42">
c Update the DPM node conguration. Search for <BackupVMs> in the le. For each DPM server, update DeploymentStatus
to "DomainJoined". For example:
<BackupVMs>
86
Operations