Troubleshooting guide

B: Reverting RSA Authentication Manager 8.1 to Version 6.1 105
RSA Authentication Manager 6.1 to 8.1 Migration Guide
B Reverting RSA Authentication Manager 8.1
to Version 6.1
Reverting Migration
After migration to version 8.1, all of the required version 6.1 data and application files
still exist on the original Authentication Manager hardware. However, reverting to
version 6.1 is not just simply stopping version 8.1 and restarting version 6.1. Consider
these important issues before reverting:
• Data loss
All data concerning any version 8.1 administration or authentication activity is
lost and cannot be recovered for use in version 6.1. Your version 6.1 servers will
be in the same state they were in at the time of migration.
• Authentication downtime and updating authentication agents
The amount of administration downtime is minimal, since in all cases, reverting
involves stopping version 8.1 and restarting version 6.1. However, the ability to
authenticate is affected by the time it takes to update all the authentication agents.
• Authentication agents
To enable authentication agents to communicate with the reverted version 6.1
servers, you must either generate new configuration files for all agents, or delete
the sdstatus.12 file from all authentication agents, depending on the type of
migration.
• Replication traffic
The reverted version 6.1 replica databases still contain delta records that will be
replicated to the primary server when the replica server is started. Therefore, you
may see a lot of activity occurring between the primary server and any replica
servers on your network.