Troubleshooting guide

5: Replica Server Migration 81
RSA Authentication Manager 6.1 to 8.1 Migration Guide
5 Replica Server Migration
Migrating a Replica Server
After you have migrated the primary server and shut down the version 6.1 primary
server, the replica servers cannot send database changes (delta records) to the primary
instance until you migrate the replica servers. The only important data that needs to be
migrated from the replica database are the changes, or delta records, that accumulate
as a result of authentications that occur on the replica server while it is not
communicating with the primary server. For example, delta records include PIN
changes, any tokens that were disabled, or other important information about tokens
and authentication agents.
Before You Begin
Deploy the version 8.1 replica instance. See the Deploying a Replica Appliance
chapter of the RSA Authentication Manager 8.1 Setup and Configuration Guide.
Procedure
1. Dump the Replica Server Database on page 81.
2. Migrate Replica Delta Records to the 8.1 Primary Instance
on page 83.
3. If your deployment has a new hostname and IP address, you must rebalance the
contact lists. For instructions, see Rebalance Contact Lists
on page 85.
Dump the Replica Server Database
Dumping the replica database creates a database dump file that you use to migrate the
data from the version 6.1 replica database to the version 8.1 database. Version 6.1
provides a GUI-based utility for dumping the database on Windows and a command
line utility for dumping the database on Windows, Linux, or Solaris.
Before You Begin
Do one of the following:
• Stop RSA Authentication Manager 6.1 Services on a Non-Appliance Server
• Stop RSA Authentication Manager 6.1 Services on RSA SecurID Appliance 2.0
or Later