Skip to main content

Database migrations

If oneyou orwant moreto Replicamigrate nodesan areexisting unhealthydatabase orto desynchronized,your cluster, you can resynchronizedo themso with the Primary nodeeasily by following these steps:

  1. Go to the Overview tab of your cluster.
  2. Click on the ResyncMigrate ClusterDatabase button.

A confirmation popup will appear to ensure you want to resync your cluster.

001.png

ResynchronizationMigration Process

  1. Health Check ofStart the PrimaryMigration:

    • BeforeA thepopup resynchronizationwill begins,appear.
    • a health check is performed
    • Click on the PrimaryGet nodeStarted button.
    • 001.png
    • A second page will appear where you’ll need to ensureenter the processcredentials canof proceedyour successfully.source database.
    • IfOnce entered, click the PrimaryRun isCheck unhealthy,button ato warningvalidate popupthe will appear,credentials and the process will stop.connection.
    • If the Primary is healthy, the resynchronization process will continue.002.png
  2. ReplicaBegin Reconfigurationthe Migration:

    • AllIf the check is successful, a third page will appear.
    • Click the Start Migration button to begin the migration process.
    • 003.png
  3. Primary and Replica nodesSynchronization:

    • The migration will be performed on the Primary Node.
    • Once completed, all Replicas will be reconfigured as follows:
      • Replicas will be reset from scratch.
      • OnceAfter cleared,being eachcleared Replica will beand reconfigured to point to the Primary.
      • Primary,
      • Aeach Replica will be restored with a backup directly from the Primary node will then be restored to each Replica to ensure full synchronization.synchronization

During the resynchronizationmigration process, your cluster will be temporarily unavailable.

Once the process is complete, you will receive an email notifying you that your cluster is active and operational again.