Veritas NetBackup™ Bare Metal Restore™ Administrator's Guide
- Introducing Bare Metal Restore
- Configuring BMR
- Protecting clients
- Setting up restore environments
- Shared resource trees
- About 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
- Enabling or disabling SRT exclusive use
- Repairing a damaged shared resource tree
- Breaking a stale shared resource tree lock
- Managing boot media
- Restoring clients
- Disclaimer
- BMR restore process
- Preparing a client for restore
- 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 dissimilar system restore
- About discovering the configuration of the new system
- Creating an editable DSR configuration
- About adding NIC and MSD drivers
- About changing network interfaces
- About mapping disks in the restore configuration
- About creating boot media
- About restoring the client
- Logging on for the first time after system restore
- About restoring NetBackup media servers
- About restoring BMR boot servers
- About external procedures
- External procedure points and names
- About managing external procedures
- Specifying external procedures
- About external procedure data transfer
- About interaction with external procedures
- External procedure logging examples
- External procedure operational states
- About external procedure exit codes
- About external procedure error handling
- About external procedure environment variables
- About SAN (storage area network) support
- About multiple network interface support
- Port usage during restores
- Managing Windows drivers packages
- Managing clients and configurations
- About clients and configurations
- Copying a configuration
- Discovering a configuration
- Modifying a configuration
- Deleting a configuration
- Deleting a client
- Client configuration properties
- Managing BMR boot servers
- Troubleshooting
- Problems booting from CD or DVD
- Long restore times
- Solaris media boot network parameters issue
- How to recover client when BMR configuration is deleted accidentally
- First boot after BMR restore fails on UNIX platforms
- Client network based boot issue
- Verify backup failure while recovering Windows client
- The VM takes long time for booting after BMR Physical backup conversion to virtual machine is performed on 32-bit architecture Windows OS
- BMR-enabled physical backup to Virtual Machine conversion job fails on Windows platform
- Troubleshooting issues regarding creation of virtual machine from client backup
- If the boot server has a base installation of Solaris 10 update 11, the creation of SRTs can fail
- Many services on Solaris 11 and newer print warning messages during a system boot and during BMR first boot
- Solaris Zone recovery on Solaris 11 and newer takes time to reconfigure after a BMR restore during first boot
- A Solaris BMR restore operation fails if the text-installer package is not present in the customized AI ISO
- The /boot partition must be on a separate partition for a multiple device-based OS configuration
- Multiple error messages might be displayed during the first boot after the restoration of a client with ZFS storage pools
- BMR may not format or clear the ZFS metadata
- Specifying the short name of the client to protect with Auto Image Replication and BMR
- A restore task may remain in a finalized state in the disaster recovery domain even after the client restores successfully
- IPv6 support for BMR
- Automatic boot may fail for HP-UX after a restore
- Prepare to Restore may not work for a Solaris client
- Use of Virtual Instance Converter (VIC) hosts on Windows (x64) having NetBackup 8.1 is not supported in NetBackup 8.1 release for NetBackup 8.0 and earlier clients
- Creating virtual machine from client backup
- About creating virtual machine from backup
- BMR physical to virtual machine creation benefits and use cases
- Deployment diagram for virtual machine creation
- Client-VM conversion process flow
- Pre-requisites to create VM creation from backup
- Virtual machine creation from backup
- Virtual Machine Creation CLIs
- Monitoring Bare Metal Restore Activity
- Appendix A. NetBackup BMR related appendices
- Network services configurations on BMR boot Server
- About the support for Linux native multipath in BMR
- BMR support for multi-pathing environment
- BMR multipath matrix
- BMR support for virtual environment
- BMR Direct VM conversion support matrix
- About ZFS storage pool support
- Solaris zone recovery support
- BMR client recovery to other NetBackup Domain using Auto Image Replication
Discovering a configuration
You can discover the configuration of a new system; the system does not have to be a NetBackup client. A discovered configuration contains the hardware and the software information of a host.
Hardware discovery is mainly required when you are recovering a client onto different target machine than the original. In this case, as target machine differs in hardware details like NIC (network interface card), disk details than original, BMR needs to understand those details before restore begins. Therefore user needs to perform hardware discovery of target hardware using BMR prepare-to-discover operation and map original client configuration with the discovered configuration.
When you discover a configuration, BMR adds it to the discovered configurations pool. The elements of the configuration (such as disk layout) can then be used when you perform operations such as dissimilar disk restore.
When the discovery operation ends, the following changes appear on the client, and the configuration appears in the Discovered Configurations view:
AIX clients display B55 on the LED display.
HP-UX, Linux, and Solaris clients display the following message:
The Bare Metal Restore hardware discovery boot has concluded.
Windows clients display a pop-up box stating that the discovery is finished and that you can click to reboot the system.
To discover a configuration
- In the Bare Metal Restore Management node, click Actions > Prepare to Discover.
- In the Prepare to Discover dialog box, complete the fields and enter data as necessary.
If you select a client in the Hosts > Bare Metal Restore Clients view, the values for that client are included in the dialog box.
Note:
If a client is the target of a dissimilar disk restore (DDR) and VxVM manages the protected client's disks, specify an SRT with VxVM installed.
- Click OK.
- Boot the client to start the hardware discovery operation.
If you use media boot, when BMR prompts for the client name, enter it as it appears in the Tasks view from the prepare-to-discover operation.
Target machine discovery is done automatically and you receive a notification upon discovery completion. Upon successful discovery operation, you can see the discovered configuration with the given name under Bare Metal Restore Management > Resources > Discovered Configurations menu.
