I am migrating Authentication Manager on both my primary (8.0) and replica instance (8.0). I upgraded my primary instance as follows: 8.0->8.1->8.1 SP1->8.2. My replica instance seemed to be replicating correctly all the way through the 8.1 SP1 install. After upgrading 8.1 SP1->8.2, I received the "internal replication error" on the primary (as to be expected as described in other discussions here). The replica is still at 8.0 and I started to upgrade using a similar path (8.0 -> 8.1 -> 8.1 SP1 -> 8.2); however, it seems like I cannot update my replica due to a fatal error that replication isn't running. Upon viewing my logs, I get the error "incompatible replica error". So I'm at a catch22 that I can't replicate because the replica isn't 8.2, but I can't upgrade to 8.2 because it isn't replicating.
Is there an upgrade path moving forward for the replica? Or should I just abandon the current replica, and redeploy an 8.2 replica?
Also, would the proper steps have been to upgrade the primary, then replica, to the next version (upgrade both from 8.0->8.1, then upgrade both from 8.1 -> 8.1 SP1), slowly making my way from 8.0 to 8.2?
Thanks,
Gary
Hi Gary,
when upgrading RSA Authentication Manager from 8.0 up to 8.2, you should perform each step on each appliance in turn:
step 1) Primary 8.0 -> 8.1
step 2) Replica 8.0 -> 8.1
step 3) Primary 8.1 -> 8.1 sp1
step 4) Replica 8.1 -> 8.1 sp1
step 5) Primary 8.1 sp1 -> 8.2
step 6) Replica 8.1 sp1 -> 8.2
step 7) Primary 8.2 -> 8.2 patch 2
step 8) Replica 8.2 -> 8.2 patch 2
A version 8.0 will not replicate with a version 8.2.
I'm assuming your using the Virtual appliance, so unfortunately your best and quickest option now, is to remove the replica from the deployment, deleting the entry in the Primary Appliance Operations Console, Instances section. Then deploy a new RSA Authentication Manager 8.2 virtual appliance and configure as a new replica.
Best regards,
Darren Gaunt
RSA Professional Services EMEA