How Do I Take a Backup of Asset Data

This use case explains how to perform backup and restore operation of asset data alone in cold standby mode. Assets data backup and restore reduces your RTO.

For example, assume that you have two data centers DC 1 and DC 2 in the following landscape:

Data Center Name	Host Name	Region
DC 1	uk.myhost.com	United Kingdom
DC 2	us.myhost.com	United States

Here, the DC 1 is in active mode and DC 2 is passive. You want to bring up DC 2, when DC 1 goes down. Assume that DC 2 is in cold standby mode, then there would be no data in DC 2.

Pre-requisites

You must install API Gateway in DC2 and ensure that the fix upgrades of DC1 is applied to DC2 too.

You must run the following backup script periodically to take a snapshot of assets data from DC1 and store the snapshots in a suitable externalized storage system based on the RPO.

apigatewayUtil.sh create backup -include assets

This command takes a backup of asset data only. Ensure to take a backup of configurations and migrate it to the secondary data center. For more information about back up and restore, see Data backup.

Failover and Failback process

1. During the failover process:

Start API Data Store in DC2.

Run the following command in DC 2 to restore the backed up data in API Data Store:

apigatewayUtil.sh restore -include assets

Note:
In cold standby mode, the data is restored only once.

Start API Gateway in DC 2.

Reconfigure the load balancer by exposing DC 2 to the client.

2. During the failback process:

Run the following command in DC 2 to back up the data:

apigatewayUtil.sh create backup -name backup_file_name

Run the following command in DC 1 to restore the backed up data:

apigatewayUtil.sh restore backup -name backup_file_name

Start API Gateway in DC 1.

Reconfigure the load balancer by exposing DC 1 to the client.