1. An existing slave node is configured as a Secondary Master Node.

2. During regular operation the Secondary Master is used as a slave node.

3. On failover, the Secondary Master is removed from the list of slaves and set as the Master Node.

4. The instance is then started on the Secondary Master with the original Master Node removed from the configuration.

5. After the failed Master Node is back online, you can reverse this process by "failing over" again back to the original Master Node. This process reverts all nodes to their original states.