ERROR: Source and Destination servers are identical. Use --checkservers=false
to force replication.
One of our implementation guys ran into an issue where replication was complaining that the replication target is an identical system. Seems like the system ID is the same on both nodes ? Is this a realistic possibility ? Can he change a system ID on the replication target or should he re-kickstart the node ?
Thanks Rob. It is only checking the create time so the shortest path to resolution will probably be a re-kick of one node or the other.
Honestly, I'm impressed that somebody managed to initialize two systems that are replicating to one another in the exact same second. The odds against that have to be pretty astronomical!
This is likely to be an issue with the probe.xml file. If the GSAN doesn't have an up to date list of node IPs, it may incorrectly return the internal IP of one or more of the nodes and the grid will end up talking to itself without realizing it.
Please don't follow the advice about checkservers as this is likely to cause serious problems on the source grid.
Both nodes are single nodes in two different sites. I wasnt planning on using the checkservers switch, just needed to know if I needed to rekickstart the remote node or if I was able to modify the system ID
Could you please post 10 or 15 lines from the replicate.log leading up to the error? These two systems have the same create time (which is unusual) but I don't recall offhand if the replicator checks the full systemid or only the create time.
ionthegeek
2 Intern
•
2049 Posts
1041
0
Posted November 28th, 2012 11:00
Thanks Rob. It is only checking the create time so the shortest path to resolution will probably be a re-kick of one node or the other.
Honestly, I'm impressed that somebody managed to initialize two systems that are replicating to one another in the exact same second. The odds against that have to be pretty astronomical!