We had to change IP addresses on both the Primary and Replica instances and now I have an internal error on the Replica, and now they will not sync.
If you change the IP address on either a replica or primary in the Operations console, there is usually some amount of time needed for that change to reach the other AM server, but if you changed both primary and replica IP addresses at about the same time, you could be in trouble. Either the Primary or Replica may not know the other AM servers new address, because it did not learn it while changing its own.
You probably should open a support case, but you may end up needing to redeploy the replica. If the [Sync] button is available you can try to Synchronize, and it if fails the log details might show the old IP address of either the primary or the replica. You might be able to salvage the realm if you return either the primary or the replica to it's original IP, but you'd have to either guess or try changing one at a time. This could be time consuming and ultimately a waste of time, and your only recourse would be to redeploy the replica.
Look at the logs and seems replica can't communication to primary to get database update. Does the replica package need to be updated.
I did the IP change one at a time, Replica first then Primary, and I looked at the server logs, and it seems it doesn't know where the primary is.
Thanks and will most likely redeploy the replica.
That's probably your quickest fix, by a mile.
and that's what I did, all back to normal
Retrieving data ...