none
DPM critical app aware? RRS feed

  • Question

  •  Just discovered the following in test env


    I have 2 Protection groups, each to protect BMR on identical SQL servers. SQL servers have the following disks

    C:

    D:

    E:

    One Server is the SQL server for SharePoint and the DB's contains data. The second server has a new install of SQL with only 1 DB that is 12GB. All of which is whitespace.

    Both PG jobs run and complete fine. When recovering to a network location. The first SQL server folder contains 3.vhd files C:, D, E:. Which is good so SQL DB's can be reattached. The second PG recovery only contains the .vhd file of the C: and not the other 2 disks.

    There is no -exclude within the Bmrbackup.cmd

    Would there be a reason why DPM has not included the D: and E drives on the second server. Only thing I can think of is that there is a O/S file on the 2 drives on the first server. But I have looked and there is nothing there (show hidden files has been enabled)? I have also checked using the WSB gui within server manager and when BMR is selected all disks are auto selected. The disks are not auto selcted on the 2 server.

    THanks

    • Edited by CCBOYNO Wednesday, April 18, 2012 2:12 PM
    Wednesday, April 18, 2012 1:56 PM

Answers

  • Hi,

    DPM used Windows Server backup for protecting systemstate and BMR.  To see what volumes Windows backup is going to include in a BMR backup, Do the following:

    1) Set up a network share on a remote machine \\server\bmrshare

    2) From an administrative command prompt on the PS, type:

                  wbadmin.exe start backup -allcritical -backuptarget:\\server\bmrshare

    This should show you the list of volumes included in the BMR backup and ask "Do you want to start the backup operation?. - Type N to exit.

    If you want to ADD more volumes to the BMR set. 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.

     -Include  Specifies the comma-delimited list of items to include in the backup. You can include multiple files, folders, or volumes.
              Volume paths can be specified using volume drive letters, volume mount points, or GUID-based volume names. If you use a
              GUID-based volume name, it should be terminated with a backslash (\). You can use the wildcard character (*) in the
              file name when specifying a path to a file. Should be used only when the -backupTarget parameter is used.

    <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:,E: -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.

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Friday, April 27, 2012 12:32 AM
    Moderator