Introduction
If there is a major discrepancy between two servers (eg. Server1 is correct but Server2 is out), then sometimes the easiest way to restore the replication between them is to stop replication, delete the database of the one that is out of sync (in this example on Server2), take a snapshot of the correct database from Server1, then import it onto Server2 and restart the replication.
The easiest method, and best practice, is to stop the DualShield Server Service on both machines; however, this is not always an option, especially if access to services protected by MFA is required 24/7. Therefore there is another method where only one DualShield Server needs to be stopped, leaving at least the other DualShield online to continue authentication.
Most of our customers only have a two-node replication cluster (primary and secondary server) This Wiki is purely for the scenario that replication has stopped between two servers. If you have more than two DualShield Servers in an HA cluster then please contact support for assistance, as the fix for that is more complicated and will likely require a remote session with our team.
Scenario
The database that is out of sync is on Server-2, therefore, you are going to take a snapshot of the database from Server-1, then restore the snapshot onto Server-2 and restart the replication.
Stop Replication between both servers
Change to MySQL bin folder Login into MySQL console by entering When prompted, enter the password of the root mysql user.cd C:\Program Files\Deepnet DualShield\mysql\bin
mysql -u root -p