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
Network boot service configuration for Solaris version 10
No specific DHCP configuration is required on Solaris-10 SPARC architecture as BMR internally handles the required network configurations on boot server while preparing the client for restore.
Solaris 10 x64 architecture requires DHCP and TFTP services configuration to be done on the boot server manually.
To configure DHCP services, perform following steps:
Run dhcpconfig command to initialize dhcp:
dhcpconfig -D -r SUNWfiles -p /var/dhcp
Add network table entry.
pntadm -C <Network-IP> E.g. : pntadm - C 10.209.4.0
Configure subnet/route details.
dhtadm -A -m <Network-IP> -d < ':option=value:option=value:option=value:'>
Example:
dhtadm -A -m 10.209.4.0 -d ':Subnet=255.255.252.0'':Router=10.209.4.1'':DNSdmain="<yourdomainname>.com"'':DNSserv=10.216.16.101 10.217.160.131:'
Enable DHCP server using following command.
svcadm -v enable dhcp-server.
To configure TFTP services, perform following steps:
Create TFTP base directory.
mkdir /tftpboot
If the TFTP entry is not present in file /etc/inetd.conf file, add the following line.
tftp dgram udp6 wait root /usr/sbin/in.tftpd in.tftpd -s /tftpboot
Import the configuration changes.
/usr/sbin/inetconv
Restart TFTP.
svcs network/tftp/udp6 svcadm restart network/tftp/udp6
Note:
For Solaris, BMR does not support Solaris WAN-based boot protocol. Though in case of cross subnet network-based boot recovery is intended then Relay Boot server can be used.