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
- 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
- Media restore of Solaris x86 11.2 or later clients may prompt for maintenance mode user name and password
- Discovery task may remain in Finalizing state after client PTD task completes successfully
- BMR restore task may remain in Finalizing state after the client is restored successfully
- Shared Resource Tree (SRT) creation fails with an error after BMR restore if a backup operation was initiated on the boot server and client while the SRT creation was in progress
- Error in receiving BMR information during backup
- BMR backup and restore job details does not display on the NetBackup web UI's activity monitor
- 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 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
- Management of iSCSI disks in Windows environment
- Index
Boot server requirements
More information is available about the SRT requirements that are related to boot servers.
See About boot servers.
Table: Boot server requirements
Type of server | Requirements |
|---|---|
General boot server | You must have a boot server for each type of client that you want to protect. For example, a Solaris client requires a Solaris boot server, a Windows client requires a Windows boot server, and so on. For UNIX, Linux, and legacy Windows restores, a boot server at a particular operating system version can only host SRTs of the same operating system version or lower. For example, a Solaris 9 boot server can host Solaris 8 and Solaris 9 SRTs, but not Solaris 10 SRTs. For UNIX, Linux, and legacy Windows restores, a client at a particular operating system version requires an SRT of the same operating system version. Refer appendix Network services configurations on BMR Boot Server to know details about network-based recovery pre-requisite setup for different platforms. |
AIX boot server | AIX boot servers do not have any special requirements. An AIX boot server can reside on the same subnet as the subnet of the client, or on a different subnet. However, AIX boot servers at a specific operating system version can only host SRTs of the same or earlier operating system version. For example, a 5.3.0.10 boot server can only host 5.1.x.x, 5.2.x.x, 5.3.0.0, and 5.3.0.10 SRTs, but not 5.3.0.20 SRTs. Likewise, a 5.2.x.x boot server cannot host 5.3.x.x SRTs. Also, to recover 5.3.0.10 client, you need to create 5.3.0.10 SRT. You cannot use 5.3.0.11 or 6.1.0.1 SRT to recover this client. |
HP-UX boot server | Each network segment with HP-UX clients must have an HP-UX boot server that can support the clients. On an HP-UX boot server, the Ignite version of an SRT must match the Ignite version that is installed on the boot server. |
Linux boot server | Each network segment that has Linux clients must have a Linux boot server. Though in case of VLAN (Virtual Local Area Network) setup case, you can configure your switch settings to route network boot requests packets to the server located at other VLAN than where client exists. This way a single Linux boot server can recover Linux clients belonging to different VLANs. |
Solaris boot server | Each network segment with Solaris clients must have a Solaris BMR boot server that can support the clients. However, you can use the following to minimize the effect of this requirement:
If you want to use bmrsrtadm Media Creation to generate BMR-ISO SRTs, you must install the SUNWmkcd package on the boot server. |
Windows boot server | Windows boot server requirements are as follows:
|