During this talk, we'll navigate through a customer's journey as they migrate an existing MongoDB deployment to MongoDB Atlas. While the migration itself tends to be only a few clicks, the prep/post effort requires due diligence to ensure a smooth transfer. We'll cover these steps in detail and provide best practices. Whenever you're ready to migrate, you'll be equipped with the confidence, advice, and resources to assist you during every single step along the way.
6. Why Atlas?
Atlas
MongoDB as a Service
Cloud Agnostic
GCP
AWS
Azure
Secure By Default
IP Whitelisting
LDAP
Encrypted Backups
TLS
Values
Self Service Database Access
Best Practices From Day 1
Drives Focus To Development
https://www.mongodb.com/cloud/atlas
8. Prep Items
> db.getReplicationInfo()
Gather details about existing cluster
Launch new Atlas Cluster
Working set in RAM
Resize OpLog❗
Check version compatibility, including your drivers❗
9. Prep Items
use admin
db.createUser({
user: "migrationSourceUser",
pwd: "pass",
roles: [ "clusterMonitor", "readAnyDatabase" ]
})
Create Users
IP Whitelist your apps
Verify apps can talk to Atlas❗
12. Comparing Options
Live Migrate ✅✅✅ mongomirror mongodump|mongorestore
RS or Sharded RS only All deployments
Great for most customers Can avoid network hop Downtime proportional to data size
Short cutover window
Built-in Atlas UI
User-controlled cut-over Sharded -> RS
13. Behind The Scenes
1. initial sync, copying documents and
building indexes that already exist on
the source deployment.
2. oplog sync, tailing and applying
entries from the oplog.
20. Post Steps
Monitor the deployment
Re-size oplog or instance size accordingly (72 hours recommended)❗
Update IP Whitelisting, if applicable
Set up backups, alerts, and other security settings
21. Key Takeaways
Do most of the "post work" upfront
Identify most suitable migration route
Have a generous maintenance window
Engage with Professional Services
> https://www.mongodb.com/contact/consulting/mongodb-atlas-foundation-migration-planning
Measure Twice, Cut Once!