Move the DPM server to a different computer
Updated: May 13, 2016
Applies To: System Center 2012 SP1 - Data Protection Manager, System Center 2012 - Data Protection Manager, System Center 2012 R2 Data Protection Manager
There are a couple of ways in which you can move the DPM server to a different computer:
Move DPM to a new server with the same settings— In this configuration you’ll move the old DPM server to a new server that retains the same name, domain settings, and operating system version.
Move DPM to a new server with different settings— In this configuration you’ll install System Center 2012 – Data Protection Manager (DPM) on a new server that doesn’t have the same settings as the old one.
Move DPM to a new server with the same settings
You’ll need to back up the DPM database, install the new DPM server with the same settings as the old one, and then restore the database. No actions are required for protected clients since server settings have been preserved.
Step 1—Back up the DPM database
If the DPM database is on the DPM server open an elevated command prompt on the server and navigate to \Program Files\Microsoft DPM\DPM\bin. In the database is on a remote SQL Server, on that server open an elevated command prompt and navigate to Program Files\Microsoft Data Protection Manager\DPM2010\SQLPrep.
Type: DPMBackup.exe –db and press ENTER. This creates the backup.
From the backup application, if the backup is located on the DPM server go to Microsoft Data Protection Manager\DPM\Volumes\ShadowCopy\Database Backups. If the backup is on a remote SQL Server go to \Program Files\Microsoft DPM\DPM\Volumes\ShadowCopy\Database Backups. The backup that was created is DPMDB.bak.
Select the media to which you want to back up the database and start the backup.
Step 2—Remove the old server and install the new one
Remove the old server from the network. This is required since you’ll be using the same FQDN for the new server.
Install DPM on the new server. It should be running the same operating system as the old server. Keep the same FQDN and domain settings. After installation is complete, verify that updates installed on the old server are also installed on the new one.
Step 3—Restore and synchronize the DPM database
At the command prompt, type DpmSync –restoredb –dbloc <DPMDB location>, and then press ENTER.
The default location of DPMDB is C:\Program Files\Microsoft DPM\DPM\DPMDB. When you use an existing instance of SQL Server for DPM, the default location of DPMDB is the path on the instance of SQL Server where the SQL databases are located.
At the command prompt, type DpmSync -sync.
Step 4—Verify settings
- In the DPM Administrator Console on the new server, in Monitoring, restart any failed jobs. Then Run a consistency check for all data sources.
Move DPM to a new server with different settings
You’ll need to install DPM on the new server, and then update protected client settings This procedure assumes that the old and new DPM servers are running the same operation system version, and that you’re using the same SQL Server settings on the old and new DPM servers.
Step 1—Install DPM
Install DPM on the new server.
Step 2—Update protected clients
Update protected clients with the new server settings. To do this, run the Windows PowerShell cmdlet
SetDPMServer.exe -DPMServerName <Name of new DPM server>on each protected computer.
Associate the client computers with the new DPM server. To do this, run
Attach-ProductionServer.ps1from the DPM Management Shell on the new DPM server. You’ll prompted for the DPM server name and the protected client (production server) name.
On the new DPM server create protection groups and add the protected computers to them.
Step 3—Run side by side
You’ll need to maintain the previous DPM server until the recovery points from inactive replicas on it are no longer required.
Migrate disk storage
The procedures above presume you’ll use the same disk storage on the new DPM servers. If you do want to migrate disk storage you’ll need to use the MigrateDatasourceDataFromDPM.ps1 script, as follows:
Connect the new disk to the DPM server.
Retrieve the following information—
List of the protection groups using the Windows PowerShell command Get-ProtectionGroup
The data sources for each protection group using Get-Datasource.
The disks that were connected to the DPM server using Get-DPMDisk.
Then run MigrateDatasourceDataFromDPM.PS1 script. For more information, see Run MigrateDatasourceDataFromDPM in the TechNet library.