Call support to troubleshoot the failure.
The Primary would not go down until the majority of the data was Rsync'd over to the Redundant - then the services on the Primary would go down while that last bit of information was syncd.
There are log files that you can pull that will give you good indication of root cause, however, at this point, I would suggest to call support and let them troubleshoot.
Basic premise when you setup Primary / Redundant:
The Primary will not copy data for any partitions currently being written to, it will create some sort of marker to let it know where to start once the background copy is done.
Rsync will then copy over all the rest of the partitions (that were not being actively written to), you will then get prompted in the UI to "Finalize" (there is a finite time frame which this is available - then it goes and starts another Rsync and you have to wait for another "Finalize" prompt).
Once you acknowledge the "Finalize" prompt, that is when the services on your Primary will go down, to allow the remaining partitions to be copied over without any new data being added to the database while the new Rsync is running.
Once all of the data is done copying, the Primary becomes available again.
2 of 2 people found this helpful
My primary ESM was not even reaching the stage to clieck "finalize", had to reach tech support. The below mentioned helped and it got resolved.
- Removed the secondary esm from primary
- Moved the sync file from /usr/local/ess/tmp to /temp
- Configured the primary with secondary ESM IP
- Sync started and completed without any issues