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
Pre-requisites to create VM creation from backup
Following are the prerequisites to create virtual machine from backups.
Configured BMR Master Server
First, you need to enable the BMR server on your NetBackup master server. For details on how to enable BMR server, See Configuring BMR Master Server.
Client's BMR enabled backup
Configure NetBackup policy for BMR. Enable check box for BMR for the Collect disaster recovery information option in backup policy attributes. For details, See Configuring policies to back up BMR clients.
BMR backup policy requires at least OS volumes added as part of backup selection. In case of Windows, Boot, System Volume, System State needs to be added under backup selection list.
Note:
For user convenience, in the backup selection, ALL_LOCAL_DRIVES option is made available by default that considers all the client volumes during backup.
After enabling BMR in backup policy, take an initial FULL backup.
Hypervisor-specific tools ISO file
VM creation process requires hypervisor-specific tools ISO file so that during VM creation it configures required device drivers into VM system. Usually Hypervisor vendor provides their tools ISO file on their website and hypervisor server. For example, in case of VMWare ESX server 5.0, the associated tools ISO can be located on your ESX server as well as can be downloaded from VMWare website. See following examples given.
Tools ISO path on ESX server: /vmimages/tools-isoimages/windows.iso
Website location:
http://packages.vmware.com/tools/esx/5.0latest/windows/x86_64/index.html
It is MUST to have this tools ISO file on VIC host. Virtual machine creation wizard prompts for full directory path of this ISO available on VIC.
Hypervisor server name registration in NetBackup
You need to register your Hypervisor server with NetBackup where VM needs to be created. This registration requires Hypervisor server admin credentials. Refer following sample GUI of VMWare vCenter server registration.
VIC (NetBackup recovery host) name registration in NetBackup
For VMWare type Hypervisor, Virtual Image Converter host name needs to be registered in NetBackup master server property named "VMWare Access Host". Refer following sample GUI of VMWare Access Host registration.
