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
- 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
Restoring a Solaris client with network boot
Note:
If NetBackup access control management is used in your environment, you must provide the appropriate credentials when prompted so that NetBackup can restore the client files.
To network boot Solaris clients, BMR requires the following:
PXE (In case of Solaris-x64 platform based client recovery)
DHCP
TFTP
NFS
To know more on the required network services configuration,
See Network services configurations on BMR boot Server.
Solaris system restore requires the name of the network device that directs the client to the correct BMR boot server.
After you perform the network boot procedure, the remainder of the restore process is automatic and requires no manual intervention. After the restore finishes and the client reboots itself, it is completely restored.
To restore a Solaris client with network boot
- Prepare to restore the client.
- Ensure that no other DHCP service except the one running on BMR Solaris Boot server is running in the same subnet. Otherwise the client DHCP boot request goes to un-intended DHCP server and network boot may fail.
Note:
This is a limitation with DHCP, PXE boot protocols themselves where first DHCP reply failure stops network boot process. Hence recommendation is to keep only Solaris DHCP service on the boot server running.
- Boot the client to restore.
- Terminate the boot process by using the #.command to return to the sc> prompt and send break command from sc>prompt to get OK prompt.
- Start the network boot by entering the following command
(net[id] is the device that points to the BMR boot server): boot net[id] where [id] is 1,2,3 interface cards.
- Start the network boot by entering the following command (net[id] is the device that points to the BMR boot server):boot net[id] where id is 1,2,3 interface cards.
More Information