Removing a two data center deployment

You can remove your two data center disaster recovery deployment on VMware.

Before you begin

Ensure that you understand the concepts of a 2DCDR deployment in API Connect. For more information, see Two data center warm-standby deployment strategy on VMware.

About this task

If you decide to remove your two data center disaster recovery (DR) deployment, you go from two data centers to one. The active data center remains as the only working system. The warm-standby data center has its data deleted.

Warning: If the active data center is offline, do not disable 2DCDR in the warm-standby data center, as this action deletes all the data from the management and portal databases.

As part of the installation, you configured the multi-site-ha settings on each data center, as described in the following table:

Table 1. The `multi-site-ha` settings
Setting	Description
`multi-site-ha-enabled`	Indicates whether two data center DR deployment is enabled. Set to `true` to enable two data center DR. Set to `false` to disable two data center DR. The default value is `false`.
`multi-site-ha-mode`	The state of the data center in the context of the two data center deployment. Valid values are: `active` - indicates the primary data center `passive` - indicates the warm-standby data center
`management-replication`	Required only for the management subsystem. The external ingress name for the management subsystem in the current data center in the two data center deployment. The name is a unique fully qualified hostname that the other data center uses to communicate with the current data center.
`portal-replication`	Required only for the portal subsystem. The external ingress name for the portal subsystem in the current data center in the two data center deployment. The name is a unique fully qualified hostname that the other data center uses to communicate with the current data center.
`replication-peer-fqdn`	The ingress hostname for the other data center in the two data center deployment. This information is required so that the two data centers can communicate with each other.

If you want to revert to a single data center topology, or temporarily remove the warm-standby data center from DR, you must disable the multi-site-ha configuration on the active data center, and then remove the warm-standby data center. If the active data center is offline, you must first change the warm-standby data center to be active, and then disable the multi-site-ha configuration on the now active data center.

Procedure

Disable the multi-site-ha configuration on the active data center:
1. Disable the multi-site-ha configuration on the management subsystem of the active data center:
```
apicup subsys set mgmt multi-site-ha-enabled=false
apicup subsys install mgmt
```
2. Disable the multi-site-ha configuration on the portal subsystem of the active data center:
```
apicup subsys set ptl multi-site-ha-enabled=false
apicup subsys install ptl
```
Disable the multi-site-ha configuration on the warm-standby data center:

Note:
Disabling 2DCDR on the warm-standby results in deletion of all data on the warm-standby.
If you do not plan to keep the warm-standby installation, you can uninstall API Connect on the warm-standby, you do not need to convert it to a stand-alone before you uninstall.
1. Disable the multi-site-ha configuration on the management subsystem of the warm-standby data center:
```
apicup subsys set mgmt multi-site-ha-enabled=false
apicup subsys install mgmt --accept-dr-data-deletion
```
2. Disable the multi-site-ha configuration on the portal subsystem of the warm-standby data center:
```
apicup subsys set ptl multi-site-ha-enabled=false
apicup subsys install ptl
```