Please enter search query.
Search <book_title>...
Veritas NetBackup™ Bare Metal Restore™ Administrator's Guide
Last Published:
2019-02-18
Product(s):
NetBackup (8.1.1)
Platform: Linux,UNIX,Windows
- 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
Prepare to Restore may not work for a Solaris client
A Bare Metal Restore (BMR) prepare-to-restore of a Solaris client computer may not work because the BMR boot server failed to resolve the IPv4 address of the client computer.
To work around this issue, perform the following:
Make sure the IPv4 address, client_host_name mapping entry exists first in /etc/hosts before the IPv6 mapping entry.
On the Solaris BMR boot server, if the /etc/hosts directory contains the IPv6 address client_host_name entry first, then the BMR boot server fails to identify client IPv4 address.
Run
again.