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
Converting client backup to VM
You can convert BMR-enabled backups to virtual machine using Virtual Machine Conversion wizard.
To initiate operations related to conversion of client backups to virtual machines, perform following actions:
- Navigate to VM Conversion Clients panel on NetBackup console.
- Right-click on intended client configuration to get a pop-up menu with conversion operation options.
Optionally, you can create a custom client configuration or PIT (Point-In-Time) configuration for VM creation. In such case, use New Client Configuration option to either create a PIT configuration or copy the existing client configuration. For details on how to change client configuration, See Creating custom configurations.
- On conversion operations pop-up menu, click Convert to Virtual Machine to start conversion process wizard.
This wizard prompts you the details about destination Hypervisor server parameters and conversion options.
VMWare based VM Conversion Wizard Flow
The wizard first page prompts user for information about VMWare server parameters, VIC host details etc.
Table: Conversion to Virtual Machine
| Parameter | Parameter Details |
NetBackup recovery host: | This is NetBackup client host-name which to be used as VIC (Virtual Instance Converter). or recovery host. This host prepares VM on intended VMWare server. Note: VIC OS has a rule that if client that is being converted to VM has Windows-based family, then you Must set Windows-based VIC . VIC can be set on physical or virtual machine if this OS rule is satisfied. However, it is not recommended to set up VIC on NetBackup master or media server as Virtual Machine creation process consumes resources and it can slow down NetBackup server Performance. |
VMWare Tools ISO files: | Enter the absolute path where the VMWare .iso file is located on VIC host that is entered earlier in this dialog box. For details See Pre-requisites to create VM creation from backup . |
vCenter server: | Select vCenter server name if applicable. |
ESX Server: | Select or Enter ESX server name. |
VMWare Folder: | The folder where the destination virtual machine to be created. |
Display Name: | Enter a display name for the virtual machine to be created. |
Resource Pool: | Select the intended resource pool name from the drop-down menu. |
Datastore/Datastore Cluster: | These are storages connected to ESX server. If you select option Use the same datastore/datastore cluster for all VMDKs then all V-disks belonging to the VM will be created on the same datastore or datastore cluster. If this option is not selected, then later screen of this wizard will provide option to map individual V-disk to the datastore. |
Refer following sample dialog snapshot showing earlier described parameters populated. Refer following screenshot for more details.