Hi,
If the -allcritical switch causes the backup to fail or if it includes too many drives, you can protect the system drive using the below steps which will allow you to restore it the same as BMR.
You need to ADD the system partition by using mountvol.exe to get the volume guid, and add it to the include.
C:\Windows\system32>mountvol
Creates, deletes, or lists a volume mount point.
MOUNTVOL [drive:]path VolumeName
MOUNTVOL [drive:]path /D
MOUNTVOL [drive:]path /L
MOUNTVOL [drive:]path /P
MOUNTVOL /R
MOUNTVOL /N
MOUNTVOL /E
path Specifies the existing NTFS directory where the mount
point will reside.
VolumeName Specifies the volume name that is the target of the mount
point.
/D Removes the volume mount point from the specified directory.
/L Lists the mounted volume name for the specified directory.
/P Removes the volume mount point from the specified directory,
dismounts the volume, and makes the volume not mountable.
You can make the volume mountable again by creating a volume
mount point.
/R Removes volume mount point directories and registry settings
for volumes that are no longer in the system.
/N Disables automatic mounting of new volumes.
/E Re-enables automatic mounting of new volumes.
Possible values for VolumeName along with current mount points are:
\\?\Volume{05abb0d4-759d-11e0-a684-806e6f6e6963}\
*** NO MOUNT POINTS ***
\\?\Volume{c8d8cd04-c8b6-11de-8261-806e6f6e6963}\
C:\
Based on the above, Modify the BmrBackup.cmd to use the following commands.
start /WAIT %SystemRoot%\system32\wbadmin.exe start backup -systemstate -include:c:,\\?\Volume{05abb0d4-759d-11e0-a684-806e6f6e6963}\ -quiet -backuptarget:%1
You can include more local drives if you want.