Forum Discussion

Lotfi_BOUCHERIT's avatar
11 years ago

About BMR server restore

Hello, I have couple of policies with ALL_LOCAL_DRIVES as backup content and the backup clients are servers containing more than one disk partition (SYSTEM C: + Data partition D:). When I want ...
  • Jaime_Vazquez's avatar
    11 years ago

    Based on the restore log, BMR on the client only could find/see one disk on the system. The restore configuration has two disk entries in it.  I presume harddisk0 is for the C:\ and harddisk1 is for the D:\. The log shows:

    4 DEBUG mergeconfigs.cpp:LocalMatchDisks() SCSI match, disk id=12135 to 5
    4 DEBUG mergeconfigs.cpp:LocalMatchDisks() Size match (LDM BPC), disk id=12134 to 4
    2 DEBUG mergeconfigs.cpp:LocalMatchDisks() Could not find a match for disk, id=12133
    3 DEBUG mergeconfigs.cpp:MatchDisks() Could not match disks, rc=1007

    disk id 12134 and 12135 are the harddisk0 and the CD ROM drives. Disk id 12133 has no viable match on the hardware.It is either totally missing or of a size smaller that what the restore configuration is holding. For this reason it dropped into the runtime DDR process wizard.

    2 DEBUG ddr_detect.cpp:IsDissimilarDiskRestore() Errors while matching disks, assuming DDR, rc=1001
    4 DEBUG CWinPeRestoreStrategy.cpp:step() Current step=Dissimilar Disk Mapping

    This wizard will allow you to make changes to the partition allocation map for recovery purposes. If you just hit "OK", only the system partition will be recovered.  In the panel, choose the selection "empty disks". In that panel choose the 'disk view' selection. It is more intuitive to use.  If there are no entries shown, then there was no other disk seen on the hardware. This could be a hardware problem or a logical drive configuration issue on a RAID adapter. BMR does not perform RAID configuration.  That is a user action at boot time.

    If a disk is visible in the panel, right click on the drive and choose 'remove restriction'. If the 'empty disks' option is not visible, there were no other disks to be seen. Anyway, from there go to the "Volumes -> Windows disk management -> Disks" selection.On the right side, choose 'disk view'.

    The panel will have two sections. The top section is "Original volume layout". The bottom is 'New volume layout'. The 'Original' layout came from the restore configuration being used.  The 'New' is what BMR will create for the recovery.  At this time, no disk writes or allocations have been performed. The 'Original' should be showing two disk drives, with their captured sizes. It will also show all of the original partitions, their drive letters, some major properties (if present) and their sizes. Right click on a partition and choose to 'map' the partition. The mapping wizard will then fire off and you can use it to do the partition mapping.  This is identical to the activity if run on the Master Server when making changes to a configuration. From the disks available section, choose a drive and do an 'Add'. The panel has an entry where the partition size is preloaded. The panel also shows 'Available space' on the drive. You can change the allocation size to any value, as long as the size is large enough to hold the recovered backup image.  BMR notes this in there as well. If there is sufficient space available on the hard disk0 entry, you can map to it, i.e. map both partitions to the single disk.  

    You can also resize the C:\ drive as well during this process. If you choose it you will not get a 'map' option, but an option to change the size. It can be shrunk  to make free space on the disk, but only to a size large enough to hold the backup image. It can even be enlarged to a bigger size if the disk has room.It cannot be unmapped and moved to another disk drive. If you do this first and free up enough space on the first disk, you can then map the second partition to it. When mapping is completed, use the "OK' button and BMR will continue on using the new layout for the disks. It will only manipulate those disk and partitions that were mapped. It will only recover those drive letters in the layout when doing the 'bprestore'.The restore selection is also noted in the log:

    4 DEBUG CWindowsRestoreStrategy.cpp:setFileSystemsToRestore() Adding C: to restore list.

    BTW, the log also shows a restore time failure:

     DEBUG nbutils.cpp:NBURestore() Restore command failed! Tried (bprestore -w   -L C:\BMR\nbulog.txt  -T   -f "X:\listfile.txt" )--rc(150).
    1 DEBUG nbutils.cpp:NBURestore() content of listFile ( 27 C:\WINDOWS\system32\config\ 1404386607 1404807258
     )

    That is a status code 150 return code when attempting the restore of "C:\WINDOWS\system32\config\". You need to look at the Admin console for this.