Veritas NetBackup™ Flex Scale Administrator's Guide

• Protect NetBackup catalog and backup data against a site failure.

• Support for dual site and single NetBackup domain configuration.

• Mechanism to takeover and migrate the primary service from one site to another.

• Configuration, management, failover, and migration using RESTful APIs and GUI.

• Asynchronous continuous replication for NetBackup catalog and backup data.

• The NetBackup Flex Scale primary site and the secondary site should be in the same NetBackup domain.

• At any given time, the NetBackup primary service is active on one site only. The media service is active on both the sites.

• Clients on the primary site backup to the primary site and then the backup images are duplicated to the secondary site.

• The node names of the clusters in the primary and secondary site should not be the same.

• You can configure disaster recovery on an active NetBackup Flex Scale Appliance (which has existing backup data and acts as the primary site).

• The secondary site that is added must be a freshly installed or configured NetBackup Flex Scale Appliance. Else, any data present on the secondary site is lost when you set up disaster recovery.

• As part of the initial configuration of the secondary site, only the primary data network should be configured on the secondary site. Secondary data network should not be configured on the secondary site before disaster recovery configuration.

• As part of the initial configuration on the secondary site (whether in the YAML file or in the GUI), users should be created on the secondary site in the same order as they are present in the primary site.

• As part of initial configuration pre-requisites, the secondary site must be in Normal lockdown mode only. The primary site can have any lockdown mode configured. After disaster recovery configuration, you can configure any lockdown mode on any of the clusters as per the lockdown mode guidelines.

• As part of disaster recovery migration and takeover, the FQDN and IP mapping for NetBackup primary service needs to be updated manually in the DNS. The NetBackup primary service FQDN should point to the virtual IP present on the new primary site.

• Primary site can have the secondary data network configured before disaster recovery configuration.

• After disaster recovery is configured between two sites, disaster recovery configuration cannot be removed.

If disaster recovery is configured:

• The cluster from which the disaster recovery configuration is initiated is called the primary site and other cluster is called the secondary site.

• Users have to be manually added on the secondary site in the same order as they are present in the primary site.

• If you want to add a node to the cluster, See Considerations for adding a node when disaster recovery is configured.

• If you want to configure VLAN, See Support for multiple VLAN when disaster recovery is configured.

• If disaster recovery is configured in a non-DNS environment, ensure that you add the NetBackup Client host entries in Settings > Network > Custom hosts at both sites.