About site-based disaster recovery in NetBackup Flex Scale
The NetBackup Flex Scale provides a disaster recovery solution by linking two NetBackup Flex Scale clusters from separate remote sites. The NetBackup catalog is replicated using Veritas Volume Replicator (VVR). NetBackup optimized duplication is used to replicate the backup images.
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.
Both the NetBackup Flex Scale clusters are configured to be part of single NetBackup domain. The NetBackup domain of the primary site is used once the disaster recovery is configured.
The NetBackup service is active on only one site at a time and can failover between sites, if required.
Clients on the primary site backup to the primary site and then the backup images are duplicated to the secondary site.
You can configure disaster recovery on an active NetBackup Flex Scale Appliance (which has existing backup data and acts as the primary site).
The NetBackup Flex Scale cluster to be configured as the secondary must be a freshly installed and configured cluster. It should not have any user data. It should not have lockdown mode configured. It should not have any additional data networks configured. It should not have node names or cluster name conflicting with the NetBackup Flex Scale cluster on the primary site. It should have the same number of nodes as the NetBackup Flex Scale cluster on the primary site.
The NetBackup primary service can be configured to use either the same virtual IP or a different virtual IP when failing over the service between two sites. When using a configuration with a different virtual IP, DNS server(s) must be updated to correctly resolve the NetBackup primary service virtual IP depending on the target site to which the service fails over.
You can choose to automatically update the NetBackup primary service host name mapping on the DNS servers that are configured with valid credentials. If you have not configured the DNS servers to be updated automatically then ensure that you have updated the DNS entries of the NetBackup primary service FQDNs to resolve to the secondary site.
Primary site can have the secondary data network configured before disaster recovery configuration.
While configuring disaster recovery, ensure that you configure ECA on the site that is going to act as the primary site.
If ECA is deployed on the primary site before adding the secondary site, then you must redeploy ECA from the primary site after disaster recovery configuration is complete.
After disaster recovery is configured between two sites, disaster recovery configuration cannot be removed.
Note:
Disaster recovery can also be configured if one or both the clusters are in non-DNS configurations.
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.
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 at both sites.
Note:
If a cloud LSU is present before the entire cluster on which the NetBackup Flex Scale software resides is destroyed, refer to the About the disaster recovery for cloud LSU section in the Veritas NetBackup Deduplication Guide.
Note:
Disaster recovery can be configured between a cluster with HPE model 5551 and a cluster with HPE model 5561.