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
- 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
- Generic BMR Restore
- Generic Discovery of Hardware
- 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
- 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
- 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 for NetBackup 8.0 and earlier clients
- PTR or PTD failure because of boot server version mismatch after upgrade
- Error messages for prepare to restore, prepare to discover, and the bmrprep command with reference to secure communication in BMR
- 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 Conversion Clients
- Converting client backup to VM
- Virtual Machine Options
- Virtual machine conversion storage destination
- Network connection selections
- Virtual machine conversion summary
- Direct Virtual Machine (VM) conversion (physical to virtual) tasks performed after the restore is complete
- Virtual Machine Conversion Tasks
- Restore Task Properties
- Creating custom configurations
- 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
- Secure communication compatibility matrices for BMR for NetBackup 8.1.1 and later releases
Preparing a client for restore
Review the secure communication compatibility matrix for BMR for NetBackup 8.1.1 and later releases before you proceed with the prepare to restore operation.
See Secure communication compatibility matrices for BMR for NetBackup 8.1.1 and later releases.
Before you restore a client, you must prepare to restore (PTR) the client.
During a prepare-to-restore operation, the NetBackup master server does the following:
Retrieves the client configuration from the master server database.
Creates the restore script and the configuration files that are used to restore the client.
Allocates the boot server resources for the selected client recovery.
When you prepare to restore a client, you select the configuration to use for the restore, as follows:
For a standard restore (also known as a self restore, which is a restore to the same system), select the current configuration.
For other types of restores, select the configuration that you created for the restore.
To ensure that the restore includes the most recent data, Veritas recommends that you prepare to restore immediately before you restore a system.
To prepare a client for restore using the bmrprep command
- Login as an administrator.
- Run the bpnbat command.
For more information regarding bpnbat command, refer to the NetBackup Command Reference Guide
- Run the bmrprep command to initiate a prepare to restore operation.
For more information regarding bmrprep command, refer to the NetBackup Command Reference Guide
https://www.veritas.com/support/en_US/article.DOC5332
Starting with Netbackup 8.1.1 release, when you execute the bmrprep command, validation checks are performed pertaining to the different parameters such as SRT version, configuration version, and so on.
If the validation checks for prepare to restore are successful, then the client is marked for automatic recovery. This automatic recovery is by default valid for 48 hours. Master server authenticity is validated automatically and a host-ID based certificate is automatically issued to this client during the automatic recovery process.
Use the nbhostmgmt command to verify whether the client is marked for automatic recovery.
For more information about the nbhostmgmt command, refer to the NetBackup Command Reference Guide
https://www.veritas.com/support/en_US/article.DOC5332
For more information about the automatic recovery and the host-ID based certificate, refer to the NetBackup Security and Encryption Guide
If the validation checks fail, appropriate error messages are displayed. Follow the instructions that are provided in the message.
For more information, See Error messages for prepare to restore, prepare to discover, and the bmrprep command with reference to secure communication in BMR.
The client is ready for restore.
To prepare a client for restore using the NetBackup Administration console
- In the NetBackup Administration Console, expand Bare Metal Restore Management > Hosts > Bare Metal Restore Clients.
- Select a client or a client configuration.
- Select Actions > Prepare to Restore.
- In the Prepare to Restore Client dialog box, select the appropriate values for the restore.
Some fields may be completed depending on whether you selected a client or a client configuration.
If some other PTR options are selected, See BMR disk recovery behavior.
- Click OK.
Bare Metal Restore runs all the processes to prepare for a restore.
Starting with Netbackup 8.1.1 release, when you click Prepare to Restore, validation checks are performed pertaining to the different parameters such as SRT version, configuration version, and so on.
If the validation checks for prepare to restore are successful, then the client is marked for automatic recovery. This automatic recovery is by default valid for 48 hours. Master server authenticity is validated automatically and a host-ID based certificate is automatically issued to this client during the automatic recovery process.
Use the nbhostmgmt command to verify whether the client is marked for automatic recovery.
For more information about nbhostmgmt command, refer to the NetBackup Command Reference Guide
https://www.veritas.com/support/en_US/article.DOC5332
For more information about the automatic recovery and the host-ID based certificate, refer to the NetBackup Security and Encryption Guide
https://www.veritas.com/support/en_US/article.DOC5332
https://www.veritas.com/support/en_US/article.DOC5332
If the validation checks fail, appropriate error messages are displayed. Follow the instructions that are provided in the message.
For more information, See Error messages for prepare to restore, prepare to discover, and the bmrprep command with reference to secure communication in BMR.
- After the processes finish, in the dialog box that appears, click OK.
The client is listed in the Bare Metal Restore Tasks in Queued state. The Prepare-To-Restore step may take few minutes to complete.
To clean up the restore configuration
- In the NetBackup Administration Console, click Bare Metal Restore Management > Bare Metal Restore Tasks.
- In the details pane, right-click the client for which you want to clean up the restore configuration.
- Select Clean Up from the shortcut menu.
The resources that the task uses are unallocated, the State is set to Done, and Status is set to 150, terminated by user.