Veritas NetBackup™ Bare Metal Restore™ Administrator's Guide
- Introducing Bare Metal Restore
- Configuring BMR
- Protecting clients
- Setting up restore environments
- Shared resource trees
- Pre-requisites for Shared Resource Tree
- Creating a shared resource tree
- Managing shared resource trees
- Adding software to a shared resource tree
- Importing a shared resource tree
- Copying a shared resource tree
- Deleting a shared resource tree
- Managing boot media
- Restoring clients
- BMR disk recovery behavior
- About restoring BMR clients using network boot
- About restoring BMR clients using media boot
- About restoring to a specific point in time
- About restoring to dissimilar disks
- Restoring to a dissimilar system
- About restoring NetBackup media servers
- About external procedures
- About external procedure environment variables
- About SAN (storage area network) support
- About multiple network interface support
- Managing Windows drivers packages
- Managing clients and configurations
- Client configuration properties
- Managing BMR boot servers
- Troubleshooting
- Troubleshooting issues regarding creation of virtual machine from client backup
- A restore task may remain in a finalized state in the disaster recovery domain even after the client restores successfully
- Creating virtual machine from client backup
- Virtual machine creation from backup
- Monitoring Bare Metal Restore Activity
- Appendix A. NetBackup BMR related appendices
- Network services configurations on BMR boot Server
- BMR client recovery to other NetBackup Domain using Auto Image Replication
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.
Veritas 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 Windows client recovery, if BMR recovery process finds vendor partition on target machine disk where client operation system is going to be recovered, then BMR prompts the user giving option to save the found vendor partition.