High Availability (HA) considerations

You can set up high availability (HA) for your IBM Concert Operate deployment by selecting a production (large) sizing profile.

IBM Concert Operate

HA configures your deployment with extra replication of its services, and affinity rules to provide redundancy. A HA configuration allows your deployment to tolerate upgrades and service interruptions to a portion of the infrastructure. Failures in the following domains are minimized:

  • individual pod failure: Red Hat OpenShift recovers individual failed pods.
  • cluster node failure (master or worker): Red Hat OpenShift recovers non-stateful deployments.

If a service has to be moved from a failed node to a new node, this can take up to six minutes.

For a high availability deployment, you must set a value of large in your IBM Concert Operate Installation custom resource when you create your IBM Concert Operate instance. Sizing is configured in your IBM Concert Operate installation custom resource with the parameter Capacity (Red Hat OpenShift Container Platform UI) or spec.size (Red Hat OpenShift CLI), and can be set to small for starter deployments or large for production deployments.

Multi-zone HA

You can deploy IBM Concert Operate on a multi-zone architecture. For more information, see Installing IBM Concert Operate on a multi-zone architecture (multi-zone HA).

Multi-region cold standby disaster recovery

A multi-region cold standby disaster recovery solution for IBM Concert Operate is also available. For more information, see Multi-region cold standby disaster recovery.

Geo-redundant multi-cluster support

A multi-cluster geo-redundant hot standby disaster recovery solution for IBM Concert Operate is also available. For more information, see Geo-redundant multi-cluster support.