Back up MongoDB Atlas, and prove it restores
Restore-tested backups of your MongoDB Atlas cluster, written to storage you control. Add one IP to the access list, use a read-only user, and every backup can prove it restores.
- Spin up a throwaway database
- Restore the backup
- Check the data came back 48 of 48 tables
- Delete the throwaway database
A second copy, outside Atlas
An off-site backup is the one you can still reach when something goes wrong with the platform or the account. Norcube keeps it outside Atlas, in storage you control, and proves it restores.
Off-site, in storage you control
Norcube runs a full mongodump on your schedule and writes the encrypted archive to Norcube-managed storage in Frankfurt or to your own S3-compatible bucket.
Proven to restore
Every backup can be restore-tested: Norcube restores it into a throwaway database and confirms your collections and documents come back.
Yours, in a standard format
Download any backup and restore it with standard MongoDB tools, independent of Norcube. No proprietary format, no lock-in.
Connect Atlas, step by step
The Atlas-specific settings, from the connection string to network access. Everything after that is the standard Protect form: schedule, retention and restore testing.
Copy the SRV connection string
In the Atlas UI, go to Database, click Connect on your cluster and choose Drivers. Copy the
mongodb+srv://string and replace<password>with the user's password, URL-encoding reserved characters (@becomes%40).Add Norcube to the IP Access List
Atlas denies all inbound connections by default. Under Network Access → IP Access List, add
18.196.207.101/32and wait for the entry to show Active. Don't use0.0.0.0/0.Create a read-only database user
Under Database Access, add a user with Password authentication and the built-in Only read any database role (
readAnyDatabase), orreadon just the database you back up.Paste it into Norcube
Choose Protect a database, pick MongoDB and paste the URI. The SRV scheme implies TLS, which Atlas always requires, so there's nothing else to set.
What Norcube adds
Restore testing
Prove each backup restores, not just that the dump ran. A Passed badge per backup and a restore-health score per database show recoverability at a glance.
Failure and missed-backup alerts
Get notified when a backup fails, a restore test can't confirm your data, or a schedule silently stops. By email, Slack or a signed webhook, on every plan.
Your own bucket
Keep backups in Norcube-managed storage in Frankfurt, or in your own Amazon S3, Cloudflare R2, Backblaze B2, Wasabi or MinIO bucket.
Standard archives
Every backup is a standard mongodump archive, gzip-compressed by default. Download it any time.
Atlas backups, answered
The questions that come up when backing up MongoDB Atlas. The full guide is in the docs.
Why can't Norcube connect to my Atlas cluster?
18.196.207.101/32 and wait until the entry is Active.What permissions does the database user need?
readAnyDatabase covers a full-cluster dump, or grant read on a single database. Don't grant write or admin roles.Does Norcube use --oplog?
--oplog needs privileges Atlas doesn't grant a standard user, so Norcube takes a regular mongodump, which is exactly what gets restore-tested.How do restore tests work for MongoDB?
Your Atlas data, backed up and tested
Start on the Free plan. No credit card required. Connect Atlas, pick a schedule and let the first restore test prove it.
- Free plan
- No credit card
- Standard formats
- Restore-tested