Adding a standby master server to a cluster
In IBM Guardium Key Lifecycle Manager, high-availability solution is implemented by using Multi-Master cluster configuration. IBM Guardium Key Lifecycle Manager Multi-Master cluster must contain a primary master server and a standby master server. Add a standby master server to the cluster for setting up a Multi-Master environment.
Before you begin
About this task
To provide continuous data availability to all the IBM Guardium Key Lifecycle Manager instances in a Multi-Master cluster, Db2 high-availability disaster recovery (HADR) configuration is used. Db2 HADR is a database replication feature that provides a high-availability solution. HADR protects against data loss by replicating data changes from a source database, called primary, to a target database, called the standby. Db2 HADR supports up to three standby databases in your Multi-Master setup.
The server from where you add the first standby master server to a cluster is configured as the primary master server. After the cluster is created with a minimum of one primary and one standby master server, you can add master servers from any of the master servers in the cluster. Your role must have the permission to add standby master servers to the Multi-Master cluster.
To add a standby master server to a cluster when another master server in the cluster is out of network or unreachable, you can use the REST interface only. For more information about the REST API, see REST service for adding a master when other master in the cluster is not reachable.