DR test and Data Protection Manager rebuild
-
sábado, 02 de julio de 2011 8:21
Hi,
I have a DR test in a few week and will need to do a test restore my Data Protection Manager 2010 server as if it had died. We have two Data Protection Manager 2010 servers. One at the office and this has the tape drive and another one off site. I really don't want to mess with these server during the test, but I still need to prove we can rebuild the primary and recover files from tape if need be. Of course in a real DR I would hope the secondary would have all the files I require. The DR site will provide all hardware I require.
Can I just build a new Data Protection Manager server with the same version of Windows, QFE level and restore the backed up database from the secondary Data Protection Manager server and test from there? Does the new server have to be the same server name as before and on the same domain?
Best wishes
Michael
Todas las respuestas
-
domingo, 03 de julio de 2011 8:18Moderador
Hi Michael,
The method you are thinking of (Building new DPM server) using should work. Your new DPM server does not need to be on the same hardware or have the same name but it should be in the same domain.
HTH
My Blog | www.buchatech.com | www.systemcenterdataprotectionmanager.com- Propuesto como respuesta BuchatechMVP, Moderator domingo, 10 de julio de 2011 1:24
-
jueves, 07 de julio de 2011 16:39
That worked a treat. The only issue I have is, it won't let me install an agent on a new server I have built to recover to.
It tries to install the agent. It seems to work, but the agent just disappears.
Would it have been better to install an agent before installing the database. It shows no agents installed at all and can't even restore to itself, the windows with server options to recover to is blank, not even the domain.
Best wishes
Michael -
domingo, 10 de julio de 2011 1:24Moderador
Hi Michael,
Yes you can try installing the agent before hand. Also have you tried installing the agent manually?
My Blog | www.buchatech.com | www.systemcenterdataprotectionmanager.com -
domingo, 10 de julio de 2011 17:09Moderador
MCurtis,
The rebuilt DPM server needs to be the exact same name and in the same domain so to do this test restore you should build a virtual envirnonment and re-build the DC using BMR from production domain, then go through the DPM server rebuild. I think you will find everyting works fine.
Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.- Propuesto como respuesta Mike JacquetMicrosoft Employee, Moderator domingo, 10 de julio de 2011 17:10
-
domingo, 10 de julio de 2011 21:21Hi Mike, Thanks for the reply. As a feature request, it would be nice if the primary Data Protection Manager server could sync the tape recovery points to the secondary server. I have a secondary Data Protection Manager server at the DR site, but I need to be able to show I can restore from tape as well. I will build a Hyper-V environment for the test. I assume I will have to delete the old Data Protection Manager server from the restored Domain Controller before building a new one with the same name. Is it only the name Data Protection Manager cares about or is it the GUID as well? Best wishes Michael
-
domingo, 10 de julio de 2011 21:57Moderador
The same DPM name is a requirement, but ideally, using the same AD machine account helps as well since we use DCOM and machine SID's for communications. What you will most likely have to do if you dom't use the same AD machine account for the DPM server is you will need to run setdpmserver -dpmservername <dpmservername> on each protected server to make sure the new dpmserver is added to local groups to allow agent communications.
Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. -
miércoles, 13 de julio de 2011 21:06
Hi,
I got this working. I rebuilt the Data Protection Manager server with the same name. I then restored the database via the backup on the secondary Data Protection Manager server. I stopped the Data Protection Manager and SQL services. I moved the newly installed database into a new folder and then replaced them with the restored files from the secondary Data Protection Manager server. I rebooted.
Once I had remapped the tape drives all was good. it is a shame the new server has to have the same name. This makes a DR test quite hard. Hopefully this can be fixed in 2012.
Best wishes
Michael -
miércoles, 27 de julio de 2011 13:42 Hello,
The reason that the DPM server has to be the same name is that the name of the server is too heaviliy ingrained into the SQL database.
One of the most common gotchas on a DPM restore is this very subject. If I had to list the top gotchas, it would be:
a.) keep the DPM server the same
b.) leave the storage pool alone to keep your recovery points
c.) not having a healthy backup of the DPM database
d.) not bringing the DPM patch level up to the same version as it was when the DPM database backup was taken.
Thanks
Shane- Propuesto como respuesta ShaneB. _ jueves, 28 de julio de 2011 14:07
- Marcado como respuesta Yegor StartsevMVP, Moderator jueves, 31 de enero de 2013 7:39
-
miércoles, 27 de julio de 2011 20:41Not only did I have to do this for a DR for tape restore testing, I have just had to do this for real as our raid died.
Data Protection Manager has come back well. My only issue now is, I can't backup the primary Data Protection Manager database to the secondary. The replicas are inconsistent. I have removed the old backups and deleted them from dpm2 and remade them, but they still stay inconsistent.
Looking at the primary Data Protection Manager server I see the SQL VSS Write is failing with an Event 7.
Their is a thread here
http://social.technet.microsoft.com/Forums/en-US/dataprotectionmanager/thread/d10aa53e-2913-4601-baf8-cfe4dcb23c18/
I only mention here as I agree about C from above. Data Protection Manager can be restored nicely, but the db is critical.
Best wishes
Michael
.png)
