So last time we restored the DPM Database and reallocated the Storage pool

Now we’re going to bring back the report history.  If you don’t NEED that report history in the DPM server from it’s predecessor?  You’re done.   But I wasn’t

Now BEFORE you can into the SQL server database to manage it, you’ll need permission. 


Yes.  I have found when you’re using a completely integrated DPM 2007 server install with the provided database, YOU can’t manage the SQL database.   But that’s an easy fix.

The account that can is automatically created by DPM 2007 to run the Report Server.  It’s name is “MICROSOFT$DPM$ACCT”, it’s a local computer account and the password is WHATEVER you provided to DPM at the beginning of the install process.  You did document it right?

So you’ll need to login locally on the computer with that Account name and the password you gave to DPM.   Access SQL Server Enterprise Manager and grant yourself rights to the Report Server (and while you’re there anyhow) the DPM Database.  You could just restore the Report Server in this account, but you’ll need rights to the Report Server database in order to access those old reports.   I found I had some rights issues initially when I brought it back so I wanted to eliminate problems and granted myself full Database and Sysadmin access.  You can always turn things down and remove it when you’re done.

So log back in as yourself and test you can access via SQL Server Enterprise Manager.  We’re ready to restore the Report Server database so you can get your history back.


Now personally, I backed up the Report Server Database on the new install first before trying to restore so I *COULD* just give up in case the reports wouldn’t migrate and still have a working DPM server.

You’ll need to login to the SQL Server and restore the database for the Report Server.  Again, you may have to down the ReportServer service to allow this restore to happen.   Also make sure when you do the Restore in the SQL Enterprise Manager you select “Overwrite old Database” or it will fail everytime.

Once you’ve restored the Report Server database, you’ll need to put the Security key back into the Report Server.   Start the ReportServer service backup and run RSKEYMGMT.EXE.  We’re “assuming” the keyfile is called “KeyFile.txt” with a password of “DuMbPassw0rd” from the previous article.


RSKEYMGMT.EXE –a –f C:DPMBACKUPKeyFile.txt –p DuMbPassw0rd


This is absolutely necessary in order to access the configuration and content of the old Report Database.   If you don’t it will APPEAR to run as far as the configuration is concerned but you’ll get a lot of strange errors if you don’t.

You should probably restart the services when you’re done (for good measure).

If all goes well, you should find all your DPM configuration completely intact.  You will need to run an Integrity Check on all the Storage groups to get everything operational.   You should however be able to view your Reports, History and Content from the original DPM Server.


You should also as a result, be able to immediately pickup and go.   Your agents for DPM ONLY care about the name of the DPM server and as such, work immediately.   No redeployment necessary.  


If you run into problems, here’s what I’ve noticed that helped me

  • Service Pack.  If you’re not at the same revision of SQL *OR* DPM when you do this, you’ll have problems. 
  • Agents.   Agents will complain if again, you’re not at the same service pack.  But in the Management console, if you click on a Server?  You can see it’s agent version.  A query against Microsoft and DPM will tell you what Service Pack it’s expecting for DPM.
  • DPM Keeps Crashing over and over when I try to modify the configuration.   I had that when I tried to change the machine name.  Give up.  It doesn’t and it won’t work. 🙂

Some positive results I’ve discovered

  • If you use Server 2008R2, you’ll have fewer issues with the Report Server and won’t get the classic “ID: 3013” error for your Handler Mappings in The DPM Management console
  • Expansion.  You CAN replace your storage pool from the old Server with a larger on the new server. 

And one thing I’ve found with the Report Server, every issue I’ve encountered was well documented online.

Life will be good, and your boss WILL be happy 🙂

The Energized Tech