lsepoch and chepoch method

If the sites do not have an IP connection, you can fix syncreplica –export problems using lsepoch and chepoch commands.

1. At buenosaires (destination replica), run lsepoch to determine the actual state of buenosaires:

   multitool lsepoch buenosaires@/vobs/tests
   For VOB replica "/vobs/tests":
   Oplog IDs for row "buenosaires" (@ mardelplata):
   oid:ac93e6cf.14a311d5.bbcc.00:01:80:c0:4b:e7=4000     (buenosaires)
   oid:c6b8c9b0.038d11d1.b083.00:60:97:98:42:69=5927     (sydney)
   

2. Send the lsepoch command output back to the sending site, where the administrator of sydney uses this data in a chepoch command to inform sydney about the actual state of buenosaires.

   cd /vobs/dev
   multitool chepoch buenosaires
   Enter specifications for epochs to change in row "buenosaires" (one per line)
   oid:ac93e6cf.14a311d5.bbcc.00:01:80:c0:4b:e7=4000
   oid:c6b8c9b0.038d11d1.b083.00:60:97:98:42:69=5927
   .
   Change oplog IDs in row "buenosaires" [no] yes
   Epoch row successfully set.
   

3. At sydney, enter the original syncreplica –export command.
   • If the command fails, buenosaires is in jeopardy. Have other replicas in the family perform this process, taking the role of sydney to exchange update packets with buenosaires. The hope is that some other replica has not yet scrubbed its copies of the missing oplog entries. If no other replica has the missing oplog entries, you must create a new replica. See Replacing an existing replica.
   • If the command succeeds and the packet is imported successfully at buenosaires, buenosaires is up to date.

   Note: Have all administrators review their oplog scrubbing procedures. See Scrubbing parameters for replicas.