How to sync two separate 2 node clusters

Products

• CA API Gateway

Issue/Introduction

There are two separate environments with 2 node clusters. Currently, objects are manually modified in each cluster.  There is a difference in the certificates of the ID Provider resulting in failures to one cluster only.

What's the best approach to sync these two environments?

 

 

Environment

API Gateway 10.0

Cause

Manual changes are prone to errors .

Resolution

Best approach is to dump the SSG DB from the good cluster then import into the problematic cluster.

The steps are similar to clone and the KB for re-init replication

NOTE: Check with the team regarding cluster passphrase between the two different cluster 

 First dump the SSG DB from the node in the good cluster

 #  mysqldump ssg --routines > /home/ssgconfig/01-ssg.sql

Copy the backup-ssg.sql to the problematic each node in the cluster

 

On the problematic cluster 

STOP SSG services on both gateways 

# service ssg stop

 

Stop slave replication on both nodes: 

# mysqladmin stop-replica 

 

Reset the master configuration on both nodes: 

# mysql -e "reset master"

# mysql -e "reset slave; reset slave all;"

 

Backup current SSG DB on problematic gateway as a precaution 

mysqldump ssg --routines > /home/ssgconfig/03-ssg.sql

 

Drop the SSG from the BOTH gateways and import the SSG DB from the good cluster to both

# mysql

# drop database ssg;

# create database ssg;

# mysql -u root -p ssg < 01-ssg.sql

 

Clear cluster_info table on BOTH Gateways

# mysql

mysql> use ssg;app*A

mysql> truncate table cluster_info;

 

SETUP replication Secondary gateway and restart replication on the primary node

1. Execute the create_slave.sh script on the SECONDARY node: /opt/SecureSpan/Appliance/bin/create_slave.sh
• Follow the prompts of the script, keeping the following in mind:
• Provide the FQDN of the primary node
• Enter NO to the prompt "Do you want to clone a database from $Master (yes or no)?"
2. Execute the create_slave.sh script on the PRIMARY node: /opt/SecureSpan/Appliance/bin/restart_repplication.sh
• Follow the prompts of the script, keeping the following in mind:
• Provide the FQDN of the secondary node
3. Query the status of the replication on both nodes: mysql -e "show slave status\G"
4. Verify both nodes return the following lines:

Slave_IO_Running: Yes
Slave_SQL_Running: Yes
Seconds_Behind_Master: 0

1. Start the Gateway 'ssg' service on both nodes: service ssg start