How do I perform an auxiliary database switchover?
Purpose
|
CAUTION Data Loss |
Performing an auxiliary database switchover may result in an data-collection interruption of up to 30 minutes.
Ensure that you perform the switchover directly after the completion of the most recent copy-cluster operation, as described in the procedure.
Perform this procedure to switch the active and standby roles of a geo-redundant auxiliary database.
Steps
1 |
Log in to a station that has access to the NSP system. |
2 |
Open a console window. |
3 |
Issue the following REST API call: Note: In order to issue a REST API call, you require a REST token; see the My First NSP API Client tutorial on the Network Developer Portal for information. GET https://address:8545/restconf/data/auxdb:/auxdb-agent where address is the NSP advertised address The auxiliary database cluster status is displayed; the copy-cluster operation is complete only when the status reads SUCCESS. |
4 |
If the cluster status reads RUNNING, return to Step 3. |
5 |
A copy-cluster operation is invoked every 30 minutes to replicate the recent data from the primary to the standby auxiliary database cluster. Review the status information to identify the copy-cluster completion time. |
6 |
To minimize data loss during the switchover, plan the switchover for 31 minutes after the copy-cluster completion time. |
7 |
At the time planned in Step 6, issue the following REST API call: POST https://address:8545/restconf/data/auxdb:/clusters/cluster=cluster_ID/activate where address is the NSP advertised address cluster_ID is the target-cluster value in the Step 3 command output The roles reverse; the former standby cluster assumes the primary role. |
8 |
Close the console window. End of steps |