locked
Can BMR be configured to protect volumes other then the System Volume? RRS feed

  • Question

  • Using Data Protection Manager 2010, is it possible to have BMR protect ALL volumes on a Windows Server 2008 R2 machine?

    For instance, we have an Sharepoint 2010 server with two volumes, C:\ and D:\. The OS and boot volume is C:\. Sharepoint and SQL are installed on D:\. When the system is recovered using BMR, the C:\ volume is restored, and the Sharepoint and SQL Data that reside on the D:\ volume must be recovered via the DPM GUI after we have performed the BMR.

    We tested another implementation where the sharepoint machine has only one volume, C:\. OS, Boot, Sharepoint, and SQL are all installed on the C:\ volume. When a BMR recovery is performed, everything is restored perfectly, including Sharepoint and SQl.

    If we could configure the first machines BMR to protect all volumes, a recovery from a crash of that machine would be as painless and reliable as recovering the second machine. In the first scenario, we were never able to get Sharepoint to give us a clean health check after the restore. In the second scenario, Sharepoint was in perfect shape again post restore, plus we only had about 15 minutes of total downtime.

    Wednesday, September 8, 2010 3:18 PM

Answers

  • Hi ,

    On the protected server,open the C:\Program Files\Microsoft Data Protection Manager\DPM\bin\Bmrbackup.cmd file in notepad.

    Modify this line and add an -include: statement to add the drive letter of the additional volumes to be included in the BMR backup.

    <FROM>
    rem Start a wbadmin.exe to create a BMR backup
    start  /WAIT %SystemRoot%\system32\wbadmin.exe start backup -allcritical -quiet -backuptarget:%1

    <TO>
    rem Start a wbadmin.exe to create a BMR backup
    start  /WAIT %SystemRoot%\system32\wbadmin.exe start backup -allcritical -include:D: -quiet -backuptarget:%1

    You will need to adjust the replica volume and recovery point volume sizes on the DPM server to account for the additional space required for the extra volume(s) being included in future BMR backups.

     


    Regards, Mike J [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Wednesday, September 8, 2010 9:39 PM

All replies

  • Hi ,

    On the protected server,open the C:\Program Files\Microsoft Data Protection Manager\DPM\bin\Bmrbackup.cmd file in notepad.

    Modify this line and add an -include: statement to add the drive letter of the additional volumes to be included in the BMR backup.

    <FROM>
    rem Start a wbadmin.exe to create a BMR backup
    start  /WAIT %SystemRoot%\system32\wbadmin.exe start backup -allcritical -quiet -backuptarget:%1

    <TO>
    rem Start a wbadmin.exe to create a BMR backup
    start  /WAIT %SystemRoot%\system32\wbadmin.exe start backup -allcritical -include:D: -quiet -backuptarget:%1

    You will need to adjust the replica volume and recovery point volume sizes on the DPM server to account for the additional space required for the extra volume(s) being included in future BMR backups.

     


    Regards, Mike J [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Wednesday, September 8, 2010 9:39 PM
  • Mike,

    Thank you for the instructions. I will get that implemented and give our test servers a run through. Will this have any negative impact if I do a BMR on a server with just a C:\ volume?

    Thursday, September 9, 2010 4:25 PM
  • The C:\Program Files\Microsoft Data Protection Manager\DPM\bin\Bmrbackup.cmd is unique to each protected server, so just include volumes not normally included in BMR for that server.  BMR will fail if you include a non-existent volume.
    Regards, Mike J [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Thursday, September 9, 2010 5:53 PM
  • Worked like an absolute champ Mike, thank you for the info. I'll be getting this change in effect for all our BMR servers we want to do this with. Best part is it can be configured for D:, E:, F:, Z:, whatever that individual server has. 

    Monday, September 13, 2010 4:27 PM