This article provides steps to manually sync a single replica in an Authentication Manager 8.1 deployment with multiple replicas.
Replication can fail between a primary and a replica for the following reasons:
Replication is broken between the primary and a replica instance.
Possible network issue between the primary and a replica instance.
From the Operations Console, navigate to Maintenance > Backup and Restore > Back Up Now to take a backup before continuing.
Using the rsaadmin account, logon to the Authentication Manager primary, with an either an SSH session or at the local console.
Navigate to /opt/rsa/am/utils.
Retrieve the password for the rsa_dba user using the command ./rsautil manage-secrets -a get com.rsa.db.dba.password -u <Operations Console administrator name> -p <Operations Console administrator password>.
Commands are documented below:
login as: rsaadmin
Using keyboard-interactive authentication.
Password: <enter OS user password>
Last login: Tue Dec 15 14:07:01 2015 from jumphost.vcloud.local
RSA Authentication Manager Installation Directory: /opt/rsa/am
rsaadmin@am81p:~> cd /opt/rsa/am/utils
rsaadmin@am81p:/opt/rsa/am/utils> ./rsautil manage-secrets -a get com.rsa.db.dba.password -u ocadmin -p support!
rsaadmin@am81p:/opt/rsa/am/utils> /opt/rsa/am/pgsql/bin/psql -h localhost -p 7050 -d db -U rsa_dba
Password for user rsa_dba: <enter the com.rsa.db.dba.password captured above>
SSL connection (cipher: DHE-RSA-AES256-SHA, bits: 256)
Type "help" for help.
Enter the following SQL statement to list the contents of the rsa_rep.IMS_INSTANCE_NODE table: