|Applies To||Windows Server 2003|
RSA Authentication Manager 7.1 Service Pack 2 (SP2), Service Pack 3 (SP3), and Service Pack 4 (SP4)
Windows Server 2008
|Issue||Collect log data that can be sent to RSA Customer Service for analysis|
Restore replication after a replication failure in RSA Authentication Manager 7.1.2 or later
Replication failed or Replication logs
How to collect log data and restore replication after a replication failure in RSA Authentication Manager 7.1.2 or later
When a replication failure occurs in RSA Authentication Manager, the replica can be deleted and reattached (assuming SP2 or higher has been installed). However, simply reattaching a replica does not address the root cause of a replication failure and does not prevent the same failure from recurring. Also, if the primary is not recoverable, a complete reinstallation of the environment may need to be done. For these reasons, it is important to gather data prior to taking action to restore replication.
After the data is collected, you should disable and enable replication. (This is different than pausing and resuming.) Consider that this measure may not restore replication depending on the cause of the replication failure. Also, if you successfully restore replication, this does not mean that the replication issue is resolved.
RSA recommends that you identify the cause of a replication failure before you reattach a replica. However, if you decide to reattach a replica without identifying the cause, follow the important instructions at the end of this solution.
Note: This procedure instructs you to run RSA utilities. These utilities require the master password for your deployment. You created the master password when you installed the primary.
Collecting log data
To collect log data that you can send to Customer Service for analysis:
Restarting replication stops and starts the replication processes. This restores replication in many cases, but does not address the cause of the replication failure.
Avoid pausing and resuming replication when a replication issue exists. This requires communication between the primary and replicas, and if replication processes are abnormal, then pausing and resuming might take a significant amount of time and often fails.
To restart replication (if it is imperative that the replica be restored immediately), run the following commands on the primary and then on each replica.
Reattaching the affected replica
You can reattach the affected replica using the RSA Operations Console. Before you proceed, read the information in the following note.
|Notes||Important information about reattaching replicas RSA recommends that you identify the cause of a replication failure before you reattach a replica. When you reattach a replica without knowing the cause of replication issues, consider the following aspects:|
If you decide to reattach a replica without identifying the cause, perform these steps first:
For information on cleaning up after failed replication, see solution a51068.
Note: Authentication Manager 7.1 before SP4 is no longer covered under Primary Support.
For a similar solution on Linux or Solaris, see A60894
|Legacy Article ID||a51085|