Configuring disaster recovery
The user has to invoke RESTful API calls to configure disaster recovery between the clusters. The NetBackup Flex Scale cluster that is to be used as the primary may already have backup data. Before you run the API, ensure that the NetBackup Flex Scale cluster is in healthy state. The NetBackup Flex Scale cluster that is used as secondary must be a freshly configured cluster. Any changes made after the initial configuration is lost, including any backup images.
For the list of ports that should be open, see Firewall and network port requirements section in the Veritas NetBackup™ Flex Scale Best Practices and Troubleshooting Guide on SORT.
To configure disaster recovery:
Four virtual IP addresses are required, two on each cluster in the data network. One set of IP addresses are used for VVR replication and another set of IP addresses are used for heartbeat between clusters.
The API call to set up disaster recovery is asynchronous. Once the primary site receives the call, it creates a task and returns a task ID. You can find the status of the replication setup by querying the task with the task ID using the following API:
GET /api/appliance/v1.0/tasks/{taskId}Run the API to configure disaster recovery by specifying the primary and secondary site parameters. This API should be executed on the primary site.
POST /api/appliance/v1.0/disaster-recovery
This API can be retried if you encounter any network or timeout failures during disaster recovery configuration. But, do not attempt to retry it if disaster recovery is already configured.
For more information, see the Veritas NetBackup Flex Scale APIs on SORT.
The API sets up replication of the NetBackup catalog using VVR. For replicating the NetBackup policies, use NetBackup optimized duplication (SLP).
See Configuring a Storage Lifecycle Policy for optimized duplication.