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
SUSE Linux Network configuration
The following system prerequisites apply only to SUSE Linux systems:
Install the following RPM packages (unless they are installed already):
nfs-utils
dhcp-base
dhcp-server
inetd
tftp
Enable the tftp service by doing the following:
Edit the
/etc/inetd.conf
file and uncomment the tftp line.Start the service by running the following command:
/etc/init.d/inetd restart
Modify the /etc/dhcpd.conf file to define the networks it serves. You do not have to define host information; hosts are added and removed as needed by the Bare Metal Restore software. The following is an example configuration:
log-facility local7; ddns-update-style none; ignore unknown-clients; subnet 10.10.5.0 netmask 255.255.255.0 { default-lease-time 600; max-lease-time 7200; option domain-name "example.com"; option broadcast-address 10.10.5.255; option domain-name-servers 10.10.1.4,10.88.24.5; option routers 10.10.5.1; }
To verify the /etc/dhcpd.conffile syntax, restart the daemon and ensure that it starts successfully by running:
/etc/init.d/dhcpd restart
Note:
DHCP server needs to be configured on Linux BMR boot server. Any existing DHCP server in the network cannot be used for Linux BMR network-based boot recovery. It is recommended to shut down any other DHCP server while Linux client is network booting over BMR boot server. If the client DHCP boot request goes to the other DHCP server, then network boot recovery fails. This is not a BMR limitation and instead the way this boot protocol works.