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
Error messages for prepare to restore, prepare to discover, and the bmrprep command with reference to secure communication in BMR
This section provides information that helps you with troubleshooting the errors that you may encounter while you perform prepare to restore (PTR) or prepare to discover (PTD) operations and while you use the bmrprep command.
Table: Error messages with respect to secure communication in BMR
Error message | Description |
|---|---|
Add an appropriate host entry or host mapping for <Name of the host> and retry the operation. | To restore BMR configurations of NetBackup 8.1.1 and later, a valid host ID to host name mapping for the selected host name must be present. Use the nbhostmgmt command for adding a host entry in the host database or for host ID to host name mappings. For more information about the nbhostmgmt command refer NetBackup Command Reference Guide https://www.veritas.com/support/en_US/article.DOC5332 Scenario 1: The host that you intend to restore may have multiple host names associated with it or it may be referred by short name or FQDN in different contexts. If any of those host names have an entry in the host ID to host name mappings database, you need to add a mapping for it with the host name that you intend to restore using the nbhostmgmt -add command to add a new mapping to an existing host entry. such as short name, FQDN and so on Scenario 2: If none of the host names associated with the host that you intend to restore have entries in the host ID to host name mappings database, you need to add the required host entry in the host database. This may occur in a BMR AIR setup. |
Shared Resource Tree version <Version> is incompatible with client configuration version <Version>. . | To restore BMR configurations of NetBackup 8.0 or earlier, you must use Shared Resource Tree (SRT) with NetBackup client version of 8.0 or earlier installed in the SRT. Shared Resource Tree (SRTs) with NetBackup 8.1.1 or later installed in them are not supported for restoring BMR configurations of NetBackup 8.0 or earlier. Similarly, to restore BMR configurations of NetBackup 8.1.1 or later, you must use Shared Resource Tree (SRT) with NetBackup client version of 8.1.1 or later installed in the SRT. The usual conditions that the SRT version is greater than or equal to the BMR configuration version apply. |
Reset the host attributes for <Name of the host> and retry the operation. | To restore BMR configurations of NetBackup 8.0 or earlier for a host that is known to the master as communicating securely (For Example: NetBackup 8.1 and above hosts), you must reset the host for a successful communication. For more information about resetting host attributes, refer NetBackup Security and Encryption Guide |
Reset host attributes for all hosts with the mapping name <Mapping Name> and retry the operation. | A host name may be associated with multiple host IDs. For example: In a clustered environment. Some or all of those hosts may be known to the master as communicating securely (For Example: NetBackup 8.1 and above hosts). For restoring BMR configurations of NetBackup 8.0 or earlier for such hosts, you must reset all of those hosts for successful communication. For more information about resetting host attributes, refer NetBackup Security and Encryption Guide |
Configuration version of the specified host is 8.1, which is not supported by BMR. | Restoring BMR configurations of NetBackup 8.1 version is not supported. |
Set the 'autoreissue' parameter for one of the host IDs of <Name of the host> and retry the operation. | A host name may be associated with multiple host IDs. For example: In a clustered environment. In such scenarios, you must set the parameter for only one of the host IDs which you intend to restore. For more information about the host mapping, refer to the nbhostmgmt command in the NetBackup Command Reference Guide https://www.veritas.com/support/en_US/article.DOC5332 For more information about the autoreissue parameter, refer NetBackup Security and Encryption Guide. |
Authorization failed. A web login is required. Run the <Command Name> command to log in. | For a successful execution of bmrprep command, a web login is required. Perform a web login using the bpnbat command before you execute bmrprep command For more information about the bpnbat command, refer to the bpnbat command in the NetBackup Command Reference Guide |
BMR client <Name of the client> is ready to be restored. This operation is valid for a limited period of time. The default is 48 hours. Boot the client to proceed. | To restore BMR configurations of NetBackup 8.1.1 and later, you are provided with a limited period of time. The default is 48 hours. You can edit or update the default validity of 48 hours to the desired value using For more information about the autoreissue validity configuration setting, refer to the NetBackup Security and Encryption Guide. https://www.veritas.com/support/en_US/article.DOC5332 Note: This is not a requirement to restore BMR configurations of NetBackup 8.0 and earlier versions. |
BMR client <Name of the client> is ready to be discovered. This operation is valid for a limited period of time. The default is 48 hours. Boot the client to proceed. | To discover BMR configurations of NetBackup 8.1.1 and later, you are provided with a limited period of time. The default is 48 hours. You can edit or update the default validity of 48 hours to the desired value using For more information about the autoreissue validity configuration setting, refer to the NetBackup Security and Encryption Guide. https://www.veritas.com/support/en_US/article.DOC5332 Note: This is not a requirement to restore BMR configurations of NetBackup 8.0 and earlier versions. |
The specified IP address <IP address> is not associated with the host name <Name of the host>. Specify an appropriate IP address for successful Prepare To Discover operation. | If the IP address that you have specified during Prepare to Discover (PTD) operation for a particular BMR client is not associated with that client, the PTD operation fails. You must ensure that you have entered the appropriate IP address. |
The Prepare To Discover operation is not successful, because the specified IP address cannot be resolved. | If the IP address that you have specified during Prepare to Discover (PTD) operation cannot be resolved, the PTD operation fails. You must ensure that you have entered the appropriate IP address. |