Veritas NetBackup™ Flex Scale Administrator's Guide
- Product overview
- Viewing information about the NetBackup Flex Scale cluster environment
- NetBackup Flex Scale infrastructure management
- User management
- About Universal Shares
- Node and disk management
- Adding a node to the cluster using the NetBackup Flex Scale web interface
- License management
- Managing the Fibre Channel ports
- Requirements
- Managing hardware vendor packages
- User management
- NetBackup Flex Scale network management
- Bonding operations
- Data network configurations
- Network configuration on plain device (eth5)
- Network configuration on bonded interfaces (bond0 on eth5 and eth7)
- NetBackup Flex Scale infrastructure monitoring
- Resiliency in NetBackup Flex Scale
- EMS server configuration
- Site-based disaster recovery in NetBackup Flex Scale
- Performing disaster recovery using RESTful APIs
- NetBackup Flex Scale security
- STIG overview for NetBackup Flex Scale
- FIPS overview for NetBackup Flex Scale
- Support for immutability in NetBackup Flex Scale
- Deploying external certificates on NetBackup Flex Scale
- Configuring multifactor authentication
- Single Sign-On (SSO)
- Appendix A. Maintenance procedures for HPE servers
- Appendix B. Configuring NetBackup optimized duplication
- Appendix C. Disaster recovery terminologies
- Appendix D. Configuring Auto Image Replication
About site-based disaster recovery in NetBackup Flex Scale
The NetBackup Flex Scale provides a disaster recovery solution. 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.
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.
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.
The node names and the cluster names in the primary and secondary sites should not be the same.
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 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.
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.