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
- 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
- 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
Creating a Linux SRT
The first time you create an SRT on a Linux boot server, you are guided through installing the following software:
The operating system software.
BMR third-party products, the open source products that may not be included in the vendor Linux distribution. Veritas has updated the third party components in 3PPCD to their respective recent releases. Veritas recommends using Version 2.0 of 3PPCD for NetBackup version 8.0 or later. To download a CD image at no charge, see the following:
NetBackup client software.
During this process, the bmrsrtadm command copies files from BMR third-party installation program to the following directory:
/usr/openv/netbackup/baremetal/server/data/media
Each time thereafter that you create an SRT on that boot server, bmrsrtadm uses those installation files. You do not have to enter the path to the third-party product image again. If you want to be prompted for the installation program or image location again, remove the media directory before running bmrsrtadm.
The BMR third-party products CD is distributed as an ISO file system image. You can download the image and use it as the source image or write it to CD media.
To create a Linux SRT
- On the boot server where you want to create the SRT, change to the following directory:
/usr/openv/netbackup/bin
- Enter the following command:
./bmrsrtadm
- When you are prompted, select the option to create a new SRT.
- Complete the command prompts as indicated in following table.
Enter the name of the SRT to create
The name of the SRT also is used for the directory that contains it.
Only alphanumeric characters and the underscore (_) character are allowed.
Enter the description of the new SRT
A description of the SRT.
Enter the directory in which to place the new SRT
The path to the directory in which to create the SRT. The root of the SRT (called the SRT path) is the pathname to the SRT location, which includes the SRT name.
The default is either /export/srt or the directory where an SRT was last created successfully.
The directory must exist.
The following media is required:
Linux distribution - disk x of x
Please load the media now.
Load media from:
The Linux distribution (Red Hat or SUSE) and the required disk.
The bmrsrtadm command prompts you for several of the Linux installation discs.
Some systems try to mount the media that is loaded in the CD drive automatically (such as the Red Hat magicdev process). When you are prompted for media on those systems, do the following: load the media into the drive, close the drive tray, and wait for the drive light to stop flashing before pressing Enter.
The following media is required:
BMR third-party products CD (3PPCD)
Please load the media now.
Load media from:
Enter the name of the device in which the BMR third-party products CD is inserted or enter the path to the installation image.
This CD contains open source the components that BMR uses on Linux systems.
The following media is required:
NetBackup x.x Client
Please load the media now.
Load media from:
Enter the name of the device in which the NetBackup client software installation media is inserted or enter the path to the installation image.
After you enter the device name or path, the NetBackup client installation procedure installs the client software into the SRT.
Do you want to continue? [y,n] (y) y
Enter y.
Do you want to install the NetBackup client software for this client? [y,n] (y)
Enter y.
Enter the name of the NetBackup server:
Enter any nonblank value. The server name is replaced at restore time with the correct values for the BMR client being restored.
Would you like to use servername as the configured name of the NetBackup client? [y,n] (y)
Accept the default or enter any nonblank value. The client name is replaced at restore time with the correct values for the BMR client being restored.
After you install the Linux and NetBackup software, the bmrsrtadm command provides options to install other software in the SRT. You can either add other software now or quit (you can always add software later).
More information is available about how to add other software.