Troubleshoot Live Migration

Before the live migration process begins, Atlas performs a validation check to ensure that all the necessary form fields and parameters are functional and correct. If any parameters are invalid, Atlas returns an error and live migration does not proceed.

This section describes common live migration validation errors and provides suggestions for what to check if you encounter them.

Common Live Migration Validation Errors

Error

Remediation

Could not reach specified source

Ensure that you added the correct subnet ranges to the IP access list on the source cluster. You can find the four required subnet ranges in the live migration modal window.

Confirm that the hostname that you specified resolves to a public IP address. At a command prompt, use one of the following commands:
```
nslookup <hostname>
ping <hostname>
```
Ensure that you are not using a VPC Peering Connection, which is not compatible with pull live migration.

Could not resolve hostname

No IP address was found for the given hostname. Confirm that the given hostname is correct and publicly accessible.

Invalid SSL options provided

If you are using SSL:

Confirm that your SSL certificate is complete and correctly copied to the live migration (pull) modal window.
Confirm that the Is encryption in transit enabled? toggle switch is in the Yes position.

If you aren't using SSL:

Check your connection string and confirm that the ssl query parameter is not present. If --ssl is part of your connection string, your cluster requires an SSL connection.
Confirm that the Is encryption in transit enabled? toggle switch is in the No position.

The username or password is not correct

Confirm your credentials in mongosh with the following commands:

use admin
db.getUser("<username>");

If the issue persists, update the MongoDB user's password.

User not authorized to execute command

To run the live migration (pull) process, the MongoDB user must have sufficient system privileges. To learn more, see Source Cluster Security.

Disk storage info unavailable

To run the live migration (pull) process, the MongoDB user must have permissions on the source cluster's MongoDB instance. To learn more, see Source Cluster Security.

Source appears to be a standalone

Your source deployment must be a MongoDB replica set. If your source deployment is currently a standalone node, convert it to a single-node replica set before running live migration (pull).

Unable to process the provided CA file

Confirm that your CA file is complete and correctly pasted into the live migration (pull) modal window.

Source cluster contains a time series collection, which is unsupported

Ensure that the source cluster doesn't contain time series collections, which aren't supported. To filter your databases on the source cluster and identify which collections with time series data have caused the error, use the listCollections command, as in the following example:

db.runCommand({ listCollections: 1, filter:{ type: "timeseries" }})`

Available disk space on the destination needs to be increased

To successfully migrate data between Atlas clusters, the destination cluster must have at least 25% more disk space than the source cluster. Ensure the destination cluster can handle all the data, and increase your destination cluster's disk size if necessary.