Administrator Guide

Table Of Contents
c On the DPM VM, open a command prompt with elevated permissions, and then run the DPMSync –sync command. This
command r
estores the old database that has the backup disks added in the storage pool table, but the disks are oine or in an
unusable state.
d In the DPM Administrator console, open the Management workspace, and then click Disks.
e Right-click each disk, and then click
Remove.
18 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, add the pending <
DPMName
>-Backup#.vhdx les to the DPM VM. (The VHDs are either in the I:\,
J:\, K:\ or L:\, M:\, N:\ volumes of backup host. There should be 20 disks in this format (unless you added more).
19 On the DPM VM, in Disk Management (
diskmgmt.msc), check that all VHDs are in an Online state. (If not, right-click, and then click
Online.)
20 In the DPM Administrator console, add the disks to the DPM storage pool. For information about how to do this, see Congure
st
orage pools and disk storage.
21 Next, if using Azure Backup, you must congure Azure to allow re-registration of the DPM server to the same backup vault.
a Sign in to the Azure portal, click Recovery Services, and click the backup vault.
b Click Registered Items.
c In the Type list, click Windows Server.
d Select the server that you just recovered, and then click Allow Re-registration.
Figure 45. Allow re-registration
22 Next, re-register the DPM server with the same backup vault.
a Download the vault credentials le fr
om the Azure portal to a location on the Console VM, and make sure that you have the
passphrase that you used as an encryption key when you opted in to Azure Backup.
b In the DPM Administrator console, open the Management workspace.
c Click
Online.
d On the ribbon, in the
Online Protection group, click Register, and complete the wizard .
e Run the
Complete-BackupDeployment runbook to nish the process.
23 After you perform a sync operation, all the data sources should be marked as inconsistent. In the DPM console, trigger a consistency
check.
24 After all these steps you should be done, with the DPM server up and recovered.
90 Operations