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 Volumes properties
Use the Volumes property sheet of the Change Configuration dialog box to map the volume configuration from the protected client to the new disks of the restore configuration.
You can perform the following operations for mapping volumes and for changing configurations:
Change the disks that make up a disk group.
Control the file systems that are restored.
Control the logical volumes that are created.
Change the attributes of either a file system, a logical volume, or a disk.
Restrict a disk to prevent it from being used as a target for mapping.
Make a discovered disk available for mapping (remove restriction).
Given enough space on the target disk, you can map all the logical volumes and their file systems. Or you can map specific logical volumes and file systems. You do not have to restore all your logical volumes and file systems.
Primary partitions and simple volumes require only one disk. Striped, mirror, and RAID-5 volumes require multiple disks.