Search <book_title>...

Veritas NetBackup™ Flex Scale Administrator's Guide

Last Published: 2025-02-12

Product(s): Appliances (3.2)

Platform: NetBackup Flex Scale OS

Managing disaster recovery

You can manage disaster recovery using RESTful APIs.

Perform takeover:
Run the API to takeover a secondary site as primary. Set the value of operation field as takeover.
```
PATCH /api/appliance/v1.0/disaster-recovery
```
This API is run to give the primary role to the cluster on which this API is executed. Takeover is a user initiated operation and does not happen automatically. The API should be called on the secondary after the current primary site is down and not reachable. The primary site is completely down and the nodes of the primary site are not reachable.
Before you make this API call:
- 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.
- In case multiple data networks are configured, the FQDN and IP mapping of the NetBackup primary service for each data network needs to be updated manually in the DNS such that the NetBackup primary service FQDN for each data network points to the virtual IP present on the new primary site.
To clear the host cache on clients, See Clearing the host cache.
Current backup and restore jobs fail after you make this call and you have to restart the jobs after the takeover is complete. There is a time window before the NetBackup primary service is brought online on the secondary during which the backup and restore jobs fail.
Perform migration:
Run the API to migrate the primary role to the cluster on which the API is executed. Set the value of operation response field as migrate.
```
PATCH /api/appliance/v1.0/disaster-recovery
```
This API can be called only on the secondary gateway.
Before you make this API call:
- 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.
- In case multiple data networks are configured, the FQDN and IP mapping of the NetBackup primary service for each data network needs to be updated manually in the DNS such that the NetBackup primary service FQDN for each data network points to the virtual IP present on the new primary site.
- The secondary should be completely in sync with the primary.
To clear the host cache on clients, See Clearing the host cache.
Current backup and restore jobs fail after you make this call and you have to restart the jobs after the migration is complete. There is a time window before the NetBackup primary service is brought online on the secondary during which the backup and restore jobs fail.
To change the SLP of each of policies used in the new primary, See Updating the policy to reverse the replication direction.
Get the replication status:
You can get the state of the primary service catalog and the details of how the cluster lags with respect to the primary using the API:
```
GET /api/appliance/v1.0/disaster-recovery
```
For details on the response fields, See About response fields in the GET disaster recovery API.
Pause replication:
Run the API to pause the NetBackup catalog replication between the primary and secondary sites. Set the value of the operation response field as pauseReplication.
```
PATCH /api/appliance/v1.0/disaster-recovery
```
Resume replication:
Run the API to resume the NetBackup catalog replication between the primary and secondary sites. Set the value of the operation response field as resumeReplication.
```
PATCH /api/appliance/v1.0/disaster-recovery
```

To restore the backup image from the disaster recovery cluster after a takeover or migrate operation, see the Promoting a copy to a primary copy section in the Managing backup images chapter in the Veritas NetBackup™ Administrator's Guide, Volume I on SORT.

For more information, see the Veritas NetBackup Flex Scale APIs on SORT.