About mapping disks in the restore configuration
A dissimilar system restore may also be a dissimilar disk restore. If the target system has different disks than the protected client, you must map the volume configuration from the original system to the new disks. (You map as in a dissimilar disk restore.) You can also shrink or extend the size of the system partition or volume. You do not have to map the vendor partition (if one exists) from the protected client to the target system's disks.
For the changes to work properly, you must back up the target system in compliance with the procedures that are part of discovering a configuration.
See Discovering a configuration.
If you installed the client on the target system and backed it up in compliance with the procedures above, you can do the following:
Import the disk layouts from that configuration.
Map disks before the restore.
Cohesity recommends that you map disks before the restore, especially when the protected client's system partition cannot fit on the target system's system disk.
If you did not save the target system's configuration, you must do the DDR mapping during the restore.
More information is available about dissimilar disk restore.
See About restoring to dissimilar disks.
During the recovery of a Windows client, if the BMR recovery process detects a vendor partition on the disk of the target system where the client operating system is being recovered, BMR prompts the user with an option to preserve the detected vendor partition.