none
BMR wants to include D:\ drive RRS feed

  • Question

  • Hi folks,


    we have an issue with BMR backups that is related to Windows Server Backup / VSS writers.


    On remote sites, we would like to backup BMR; however, WSB thinks the D: drive should be included (which bloats the backup from 40G to about 1TB!). If this wasn't bad enough, WSB complains it couldn't back up the volume anyway because volumes greater than than 2088958 Mb cannot be protected.

    The issue (after researching and reading this ) is that the SCCM PXE dstribution point wants the folder d:\sms_dp$\sms\bin included in the backup because it contains the lousy 20Mb of boot files.

    We have tried to exclude the path with the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\System Writer\ExcludedBinaryPaths REG_MULTI_SZ set to "d:\sms_dp$\sms\bin"

    However, this didn't work.

    Setting to the service binary "d:\sms_dp$\sms\bin\sccmpxe.exe" also had no effect.


    Any suggestions?


    Thursday, November 15, 2018 9:09 AM

Answers

All replies

  • Ok, it appears as though setting the key to the binary is important. In addition, the system needs a reboot for this to work!
    • Marked as answer by namezero111111 Thursday, November 15, 2018 9:49 AM
    Thursday, November 15, 2018 9:49 AM
  • Hi,

    Yes you always need to reboot when performing a registry modification in Windows.

    Another way to do this is to edit the BmrBackup.cmd file which can be found on the protected computer's C:\Program Files\Microsoft Data Protection Manager\DPM\bin folder.

    You can see exactly what DPM will call when performing a BMR backup, you can modify this and add an
    -Exclude switch there to exclude the drives you do not want to backup.

    Example

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

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, November 15, 2018 9:52 AM
  • Thank you, Leon.

    I was under the impression exclude didn't work without a specific include first?

    Thursday, November 15, 2018 9:55 AM
  • By default the BMR will protect the "critical system data", and according to the Microsoft critical data is System State, the C drive and all other drivers that contain system data directories (for example: Program files).

    So this is what the -allcritical switch does.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, November 15, 2018 9:58 AM
  • I'll try the -allCritical with exclude:D: , but I'm fairly certain this came up before we discovered the registry key and didn't work.
    Thursday, November 15, 2018 1:26 PM