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 master service from one site to another.

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

• Asynchronous continuous replication for NetBackup catalog and backup data.

• The NetBackup Flex Scale primary cluster and the secondary cluster will be in the same NetBackup domain.

• At any given time, the NetBackup master service is active on one cluster only. The media service are active on both the clusters.

• Clients on the primary site backup to the cluster at the primary site and then the backup images are duplicated to the cluster at the secondary site. The data is always backed up to the primary cluster.

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

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

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

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

• As part of disaster recovery migration and takeover, the FQDN and IP mapping for NetBackup master service needs to be updated manually in the DNS. The NetBackup master 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:

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

• 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.

• Deploy the secondary cluster like a regular NetBackup Flex Scale cluster. The secondary cluster configuration should be equivalent to the primary cluster in terms of number of nodes, hardware and software revision.

• Create trust between the two clusters through the exchange of Appliance web server and its CA certificates. Establish an authentication mechanism between the two clusters.

  See Establishing trust and setting up authentication.

• Configure the primary and secondary cluster for disaster recovery.

  See Configuring disaster recovery.

• Configure NetBackup optimized duplication SLPs.

  See Configuring a Storage Lifecycle Policy for optimized duplication.