Search <book_title>...

Veritas NetBackup™ Bare Metal Restore™ Administrator's Guide

Last Published: 2019-02-18

Product(s): NetBackup (8.3.0.1, 8.3, 8.2, 8.1.2)

BMR client recovery to other NetBackup Domain using Auto Image Replication

This appendix explains how BMR and Auto-Image-Replication (AIR) can be leveraged together to do bare metal recovery of primary domain clients onto other clients or disaster recovery domain.

NetBackup AIR feature helps duplicating clients backup image onto defined destination or DR domain NetBackup setup. The feature performs fast backup import automatically providing primary data recovery readiness at DR site.

Refer to the NetBackup Administrator's Guide to learn more about AIR and how to enable it.

For this dual-domain dual-site protection requirement, you need to enable Bare Metal Restore option in Auto Image Replication enabled backup policy. When Auto Image Replication and BMR enabled backup image gets imported at DR domain; NetBackup server checks if the image being imported is BMR enabled. If NetBackup server finds the image is BMR enabled then it automatically imports client BMR configuration as well. You can see client's bare metal restore configuration node appears under UI menu NetBackup Administration Console > Bare Metal Restore Management > Hosts > Bare Metal Restore Clients.

During BMR configuration import at DR site, BMR master server automatically tunes client configuration for DR site entities like NetBackup master and media server host names and their IP-addresses. It updates older domain entries with new server details so that BMR recovery environment can approach to DR domain NetBackup servers while recovering client's data. Optionally, you can add or update required host entries manually by copying or editing client's imported BMR configuration. To manually edit client configuration, refer to the Managing clients and configurations chapter.

Note:

While you restore BMR configurations in a BMR AIR setup, you may come across the following error: Add an appropriate host entry or host mapping for Name of the host and retry the operation.

To resolve the issue, you need to add a host in the host database of the DR domain.

See Adding a host in the host database of the DR domain.

Without any manual backup import or configuration change, client can be completely recovered at DR domain using BMR network or media based recovery procedure. You can also create client VM onto DR domain Virtual Environment Server using the Direct VM creation from backup feature.

Refer to the Creating virtual machine from client backup chapter.

Note:

It is recommended to list client short names in NetBackup backup policy at primary domain. If FQDN of DR domain is different than primary domain then client data recovery at DR domain may fail due to mismatch in client domain name. Primary domain Primary domain > backup selection must enlist minimum OS file systems where NetBackup client is installed. In case of Windows, system state should be listed as well. If these points are not listed, then BMR configuration import at DR site may fail. Refer chapter Protecting Clients for more details about defining BMR backup policy.

Note:

Make sure BMR master server on DR domain is enabled; otherwise BMR configuration import at DR site fails.