Resiliency - Common Procedures - Database Node Swap

This procedure describes how to swap the master-slave (i.e., primary-secondary) roles of the two MOVEit DMZ database nodes. This procedure is typically performed during scheduled downtime after the failure of a master node and/or before upgrading to a new version of MOVEit DMZ software.

NOTE: A quick and simple way to swap resilient nodes is to shut down the primary/master server. This will force the secondary/slave server to take over as primary/master, at which point the server can be brought back up again. When the server finds out it is no longer master, it will begin operating as the slave. Be aware that this will cause your resiliency setup to be unable to respond to requests between the time that the master is brought down and the time the slave switches itself to master. This can take anywhere from 30 seconds to 2 minutes, depending on your Resiliency Timings configuration.

  1. From the Advanced Resiliency tab in the MOVEit DMZ Config program, shut down all services EXCEPT MySQL on all resilient nodes. (Start with the SLAVE node, then shut down services on the MASTER node, then shut down services on any other resilient nodes.)
  2. On the MASTER, press the "Record Replication" button. Wait for a "complete" or "OK" message.
  3. On the slave press the "Copy Database" button. Wait for a "complete" or "OK" message. (This procedure may take several minutes; open the "debug" window using the "Show Debug" button if you would like to see a running progress report.)
  4. Because this procedure swaps the MASTER and SLAVE roles of the two servers, the current MASTER will be referred to as OLD MASTER and the current slave will be referred to as NEW MASTER in the remainder of this procedure.
  5. Press the "Record Replication" button on the NEW MASTER. Wait for the pop-up prompt to announce that this step is complete.
  6. Press the "Make Me Master" button on the NEW MASTER. Wait for the pop-up prompt to announce that this step is complete.
  7. Press the "Use Replication Info" button on the OLD MASTER. Wait for the pop-up prompt to announce that this step is complete.
  8. Press the "Make Me DB Slave" button on the OLD MASTER. Wait for the pop-up prompt to announce that this step is complete.
  9. At this point your two database nodes have successfully swapped roles; the old master is the current slave and the new master is the current master.
  10. Start resiliency services (Web Resil and DB Resil) on all resilient nodes. (Start with the MASTER node, then the SLAVE node, then any other resilient nodes.)