Nothing should ever be feared, even migrating your DPM server.

The documentation from Microsoft covers it pretty well but I’ll give you the basic run down if you’re trying to move the environment from one machine to another, say because you need to expand your hard drive storage?

First rule.  It’s like Microsoft Exchange when moving the Information Store.  The New machine and the Old machine have to have the SAME NAME.  (not necessarily the Same IP Address)

Second rule.  You won’t be able to migrate the data, but you CAN migrate the Reports and Report history (very important if you’re dealing with SOX/PCI/HIPPA and other nasty regulations)

Third rule.  the DPM Backup ONLY GETS the DPM Database.   Your reports and Report history are part of the SQL Report Server.  I know this for a fact.

Fourth rule.  DON’T PANIC 🙂

Your first and most important task, document

Document what Service packs you’re running at for your the O/S, for SQL and for DPM, Document the IP address of the Server.

Heck document the color of the background if need be.   You want as much to be the same as before.

Most importantly as I stated, Document the physical “NETBIOS” name of the server. 

Next, backup.

Using the SQL Enterprise Manager Backup ALL the databases.  In truth, you only deep the Report Server database and DPM Database, but it never hurts to be cautious.   Note, I have found Report Server quite busy, so you may have to stop the Reporting service to get the Report Server database in SQL to backup using the SQL backup procedures.   Just right click on the Database in question, choose All Tasks, then “Backup” for each Database there.

Run DPMBACKUP.EXE to backup your DPM Database. The procedure is VERY simple.  Just run.


You will find that backup stored under “Program FilesMicrosoft Data Protection ManagerDPMVolumesShadowCopy”

Also make sure you run “RSKEYMGMT –e –f Filename –p StrongPassword” and get that Report Server encryption key exported.  If you’re storing the key into a folder called C:Backup with a password of DuMbPassw0rd then the command line will look like

RSKEYMGMT –e –f C:BackupKeyFile.txt –p DuMbPassw0rd

Now take all of that backed up information and copy it somewhere else, over the lan, onto USB, external drive, whatever.  

Shutdown the old DPM server.  *** DO NOT ERASE IT, WE’RE NOT DONE WITH IT!  LEAVE IT ALONE! ***

Now go to your new environment.  Install the same Server operating system as before (Server 2003, Server 2008, Server 2008R2), (x86 or x64), Patch levels etc etc.   Name the computer and give it the same name as the old one.   Reboot.  Join your domain and reboot again.

Now install DPM from your media as normal.  Let it run through.  Download and install the same updates as last time.  If you didn’t do updates to DPM ever and are planning to?  Don’t do it now.   Right now, we’re going to try and keep as many “what if’s” out of the equation.  Do it well after this process is done.

Make sure your SQL server is at the same version as well (Mine was SP3 before I started on the old server).  One of the things I did in advance was to download ALL the necessary service packs and updates before I needed them.   That never hurts.

Reboot your server and copy all of that nice documentation and those backup files and put them into a folder so you DON’T have to run about.   I chose one called (conveniently) “C:DPMBACKUP”. And remember Copy ‘em, don’t move ‘em.  We don’t take chances, and never should you.


Next time around, we’re going to show you how finish the job right!


The Energized Tech