Veritas NetBackup™ Bare Metal Restore™ Administrator's Guide
- Introducing Bare Metal Restore
- Configuring BMR
- Protecting clients
- Setting up restore environments
- 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
- Managing boot media
- Restoring clients
- BMR disk recovery behavior
- About restoring BMR clients using network boot
- About restoring BMR clients using media boot
- About restoring to a specific point in time
- About restoring to dissimilar disks
- Restoring to a dissimilar system
- About restoring NetBackup media servers
- About external procedures
- About external procedure environment variables
- About SAN (storage area network) support
- About multiple network interface support
- Managing Windows drivers packages
- Managing clients and configurations
- Client configuration properties
- Managing BMR boot servers
- Troubleshooting
- Troubleshooting issues regarding creation of virtual machine from client backup
- A restore task may remain in a finalized state in the disaster recovery domain even after the client restores successfully
- Creating virtual machine from client backup
- Virtual machine creation from backup
- Monitoring Bare Metal Restore Activity
- Appendix A. NetBackup BMR related appendices
- Network services configurations on BMR boot Server
- BMR client recovery to other NetBackup Domain using Auto Image Replication
Failure during submitting the job of virtual machine creation
To find the reason for failure of job of virtual machine creation, follow these steps:
On UI wizard window, if the intended NetBackup Recovery Host (Virtual Instance Convertor) is not visible under Recovery Host drop-down list, make sure that the Virtual Instance Convertor (VIC) is registered with the NetBackup master server.
On UI wizard window, if you are not able to view the intended Hypervisor (vCenter or ESX) Server, follow these steps:
If your intended server is vCenter server or a standalone ESX server, make sure that it is registered with the master server.
If Hypervisor is already registered, validate its connectivity with VIC as follows:
Open the target Hypervisor entry under the node Media and Device Management > Credentials > Virtual Machine Servers.
Select the intended recovery host under the tab For Backup Host.
Click OK.
Completing the process will validate the connectivity of Hypervisor server through the selected NetBackup recovery host.
If you are not able to view the datastores or resource pool/vApp or folder of hypervisor, check the connectivity of the Hypervisor as mentioned earlier in this section. If connectivity exists, but you are still not able to get the entries, refer the bpVMutil and bpVMreq logs with verbose level 6. Refer Table: for logs location.