Error "Component 'maindb' could not be backed up" when running ssgbackup script on the secondary node of a cluster.

Products

• CA API Gateway

Issue/Introduction

When running the ssgbackup.sh script to take a back up of the database on the secondary server of a two-node cluster, there may be an error

ssgbackup.sh -image my_backup -v -config -maindb Performing a selective backup Backing up component version Backing up component maindb Component 'maindb' could not be backed up: Cannot backup database as it is not local Backing up component config File '/opt/SecureSpan/Gateway/node/default/etc/conf/omp.dat' copied to '/tmp/ssg_backup_restore4290324402437759202tm p/config/omp.dat' File

/tmp/ss. Failed component: maindb 

Environment

All supported versions of the CA API Gateway

Resolution

The ssgbackup tool is (in general) used for planned and scheduled backups, if you're wanting to take backups for unplanned outages we suggest using mysqldump instead. The issue is caused because of the node.properties file on both Gateways points to the same Primary and then Secondary DB's for both, hence in normal conditions, the DB on the slave is actually on the master gateway and not local.