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
Windows Network configuration
Windows BMR Boot server registration enables the following services:
BMRBD (BMR BOOT server) service
BMR TFTP Service
BMR PXE Service
BMR TFTP and PXE services are used in case of network-based boot recovery. Apart from these services, DHCP service is also required.
DHCP service requirements: DHCP server can exist on the same Boot Server host or somewhere on the network.
BMR PXE and TFTP service requirement and configuration:
Make sure that there is no other PXE server running in the same subnet while BMR NW boot is happening.
This restriction is more due to the way this network protocol works. In case client NW boot request goes to un-intended PXE server then client NW boot fails. It does not re-direct the request to other valid PXE server in the network. Hence recommendation is to keep only valid BMR PXE service running while NW booting your client for BMR recovery.
Post BMR boot server registration, navigate to BMR PXE Configuration Wizard available on Windows boot server.
This wizard can be located in Start > Programs > NetBackup. This wizard prompts user for DHCP server location. Depending upon your DHCP server location (either same boot server computer or any other computer in the network), the wizard prompts to run netsh command-lines on your DHCP server.
Finish the wizard for successful PXE, TFTP, and DHCP server configuration.
If the Windows boot server is to be installed on an Active Directory Server, let the legacy restore method to share SRTs with restoring clients. Set the following security settings:
Microsoft network server
Digitally signed communications (always) - Disabled
Microsoft network server
Digitally signed communications (if client agrees) -- Enabled