# Rollover MongoDB Data

You can use the rollover operation to failover data from one MongoDB instance to another. This is useful when you need to deprovision a machine or place it in maintenance mode without disrupting services. During a standard rollover operation, the system backs up the data from the source MongoDB instance, copies the data to the destination instance, and then restores it.

Note

Failing over to a different MongoDB instance automatically restarts all web server services because web servers are the primary modules that connect to the MongoDB databases.

## Procedure

1. From the navigation pane of the Command Center, go to Manage > Infrastructure > MongoDB health.

2. Click the MongoDB node that is currently hosting databases.

   To verify which MongoDB node is hosting databases, on the MongoDB page, go to the Usage Dashboard tab.

3. In the Node health section, click Actions, and then select Rollover.

   The MongoDB data rollover dialog box appears.

4. From the MongoDB Server list, select the new MongoDB node.

5. (Optional) To switch to the new MongoDB node even if the data migration fails, select the Force failover check box.

   Warning

   Use the Force failover option only if the source MongoDB instance is unavailable or dead, or if immediate failover is required. This option forces the system to switch to the new MongoDB node even if data migration fails. Data will be reconstructed from scratch on the new instance, resulting in permanent loss of any data that was not backed up on the old MongoDB instance.

6. Click Rollover to start the rollover operation.

   You can monitor the status and execution phases of the rollover operation from the Jobs page, or view the final status in the Audit trail report.

×

Loading...