Hi Brian, could you give me more information about it. I had a replication issue
„Internal Replication error“
when the primary was already upgraded to 8.2. and the replica was running 8.1 SP1 Patch8.
When you upgrade Primary to 8.2 and replicas are not 8.2, replication will remain broken until
replica(s) are 8.2. Normal.
I moved this post to a new thread so it would not get lost in the earlier discussion.
Please take a look at the following articles about the internal replication error message: https://community.rsa.com/docs/DOC-49528 and https://community.rsa.com/docs/DOC-49697.
Same issue here. Updated my primary to 8.2 P1 and noticed the same replication issue with my secondary on 8.1 P15.
Yes, mine went to normal once primary and replica were on 8.2 P1.
I have the same issue. The document Upgrading to RSA AM 8.2 states the after upgrading Primary to 8.2 that you should wait for replication status to return to normal before upgrading the replica instances.
I'm in the same boat as Greg Griebel. The docs say that replication status must return to normal, which seems to contradict your advice above. Which is authoritative?
Pre-8.2 all docs and experience said to wait for replication to stabilize before upgrading the replicas, but 8.2 is different, in support we always see that replication remains broken after upgrading a Primary to 8.2, until the replica is upgraded to 8.2. If the docs say otherwise, that's an 8.2 doc bug, sounds like someone just copied over the old advice which did work in AM 8.1 SP1 all patches, and earlier
Jay, are there any plans to update the documentation? I've just got burnt by this issue as well, but thankfully found this article.
Nevertheless, I think that the Setup and Config Guide needs to be updated to reflect that all replicas must be upgraded immediately after upgrading the Primary. It would also be a good idea to state this advice prominently in a README file.
I will raise this with my company's account manager and my DSE, so hopefully other customers won't have to go through the pain of trying to work out what's gone wrong.
Update: Our Designated Support Engineer has confirmed that this has been escalated internally within RSA.
Retrieving data ...