How to failover API Connect from the active to the warm-standby data center
How to complete service failover in a 2DCDR deployment on Kubernetes, OpenShift, and Cloud Pak for Integration.
Before you begin
Ensure that you have read and understand the 2DCDR concepts and reviewed the failure scenarios that are described in Key concepts of 2DCDR and failure scenarios. Do not proceed with the failover until you confirm that it is the correct course of action for your situation.
About this task
- The first step in the process is to set the active data center to warm-standby. When the active data center is set to warm-standby, all data is deleted from the active data center's management database, to be replaced by data copied from the warm-standby when it becomes active. Do not proceed with failover if you suspect there is also a problem on the warm-standby data center and you are unsure it has the most recent management data. See Verifying replication between data centers, and consider restoring your active site from backup instead of attempting a failover: Backup and restore requirements for a two data center deployment.
- If the warm-standby data center is offline for more than 24 hours, there can be issues with the disk space on the active data center. In this case, you should revert your deployment to a single data center topology. For more information, see Removing a two data center deployment.
- Avoid both data centers being set to active at the same time while the network links between data centers are enabled. This causes split-brain.
- If the active data center failure prevents you from updating the active data center API Connect custom resources (CRs), then you should disable the network links used by API Connect between the data centers.
Note: For OpenShift users: The steps that are detailed in this topic use the
Kubernetes
kubectl
command. On OpenShift, use the equivalent oc
command in its place. If you are using a top-level CR you must edit the multiSiteHA section for the
subsystem in the top-level CR, instead of directly in the subsystem CRs. If the subsystem section is
not included in the top-level CR, copy and paste the section from the subsystem CR to the top-level
CR.