Seed with mongorestore¶

Optional: Create a database user in the source replica set.¶

If the source deployment enforces authentication, you must provide a database user with privileges to read any database as part of this procedure. To learn more about database user privileges, see MongoDB Role-Based Access Control.

If no such user exists, create a user in your source MongoDB replica set with the backup role on the admin database.

use admin
db.createUser(
  {
     user: "<mySourceUser>",
     pwd: "<mySourcePassword>",
     roles: [ "backup" ]
  }
)

Assemble the mongodump command.¶

Based on the type of connection string you use, copy one of the following templates to into your preferred text editor:

mongodump --uri "mongodb://username:password@mongodb0.example.com:<Port>,mongodb1.example.com:<Port1>,mongodb2.example.com:<Port2>/?replicaSet=<ReplicaSetName>&authSource=admin" \
          --archive

Do not run this command yet. Proceed to the next step once you have modified the template.

Set up database user in the target Atlas cluster.¶

To run mongorestore against an Atlas cluster, you must specify a database user in the Atlas cluster that has the Atlas admin role.

If no such user exists, create the user:

1. If it is not already displayed, select your desired organization from the Organizations menu in the navigation bar.
2. Click Access Manager in the sidebar, or click Access Manager in the navigation bar, then click your organization.
3. Click Add New Database User.
4. Add an Atlas admin user.

To learn more about user management, see Configure Database Users.

Navigate to the Clusters page for your project.¶

1. If it is not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
2. If it is not already displayed, select your desired project from the Projects menu in the navigation bar.
3. If the Clusters page is not already displayed, click Clusters in the sidebar.

Choose Command Line Tools for your desired cluster.¶

From the menu for the cluster, click Command Line Tools.

Retrieve and modify the mongorestore connection template.¶

The Binary Import and Export Tools section of the Command Line Tools tab displays a copyable template with the minimum required options for connecting mongorestore to your Atlas cluster.

The template includes placeholder values for certain options. Copy and paste the template into your preferred text editor and make the following modifications:

• password: replace this with the password for the user specified in username. The template includes a database user for the project as the username. If you want to authenticate as a different user, replace the value of username and specify the password for that user in password.
• Add --nsExclude and set its value to "admin.system.*".
• Add --archive.

Based on the type of connection string you use, your template should resemble one of the following commands:

mongorestore --uri "mongodb://username:password@00.foo.mongodb.net:27017,01.foo.mongodb.net:27017,02.foo.mongodb.net:27017/?replicaSet=myRepl&authSource=admin" \
             --archive \
             --ssl \
             --nsExclude "admin.system.*"

Run mongodump and mongorestore.¶

In your preferred text editor, use the pipe | operator to separate the mongodump and mongorestore commands. Based on the type of connection string you use, the final command should resemble one of the following:

mongodump --uri "mongodb://username:password@mongodb0.example.com:27017,mongodb1.example.com:27017,mongodb2.example.com:27017/?replicaSet=sourceRS&authSource=admin" \
          --archive \
| \
mongorestore --uri "mongodb://username:password@00.foo.mongodb.net:27017,01.foo.mongodb.net:27017,02.foo.mongodb.net:27017/?replicaSet=myAtlasRS&authSource=admin" \
             --archive \
             --ssl \
             --nsExclude "admin.system.*"

Run the completed command from a terminal or shell connected to a host machine on your source cluster.

Upon successful completion of the procedure, connect to your Atlas cluster using the mongo shell and verify the result of the procedure. To learn how, see Connect via mongo Shell.

You must update your applications to point to the Atlas cluster before resuming write operations. To learn how to connect applications to Atlas, see Connect via Driver.