如何将MongoDB Cloud生产数据同步至免费版Staging项目（覆盖原有数据）

Got it, I totally get your situation—you want to sync your Production MongoDB Atlas cluster (higher tier) to your free-tier Staging cluster, but mongomirror won't play nice because it requires matching cluster tiers. No worries, there are reliable workarounds that let you keep Staging on the free tier while getting the latest Production data. Here are the best methods to pull this off:

This is the go-to approach for offline data sync between clusters of different tiers. It’s flexible and works for most data sizes (as long as you stay under the free tier’s 512MB limit).

• Step 1: Export data from your Production cluster
  Open your terminal and run the mongodump command with your Production cluster’s connection string. This will export all databases to a local directory:

  mongodump --uri "mongodb+srv://<your-username>:<your-password>@production-cluster.mongodb.net/" --out ./production-backup
  

  Replace the placeholder values with your actual Atlas credentials and cluster URL.

• Step 2: Clear existing data from Staging
  You can either let the import process auto-drop data, or manually clean up first. For manual cleanup:

  1. Connect to your Staging cluster with mongosh:

     mongosh "mongodb+srv://<your-username>:<your-password>@staging-cluster.mongodb.net/"
     

  2. Run this script to delete all non-system databases (keep admin, local, and config intact):

     show dbs;
     db.adminCommand({ listDatabases: 1 }).databases.forEach(db => {
       if (db.name !== 'admin' && db.name !== 'local' && db.name !== 'config') {
         db.getSiblingDB(db.name).dropDatabase();
       }
     });
     

• Step 3: Import the backup to Staging
  Use mongorestore to push the exported data to your free-tier cluster. The --drop flag ensures existing collections are overwritten:

  mongorestore --uri "mongodb+srv://<your-username>:<your-password>@staging-cluster.mongodb.net/" --drop ./production-backup
  

If you prefer a visual tool, Compass makes export/import straightforward:

• Step 1: Export Production data

  1. Open MongoDB Compass and connect to your Production cluster.
  2. Right-click on "Databases" in the left sidebar, then select "Export All Databases".
  3. Choose BSON as the export format (it’s more efficient for MongoDB data) and pick a save location for the backup files. Click "Export".

• Step 2: Clear Staging data

  1. Connect to your Staging cluster in Compass.
  2. Right-click each non-system database (e.g., your app’s main database) and select "Drop Database". Confirm the deletion when prompted.

• Step 3: Import to Staging

  1. In the Staging cluster’s Compass interface, right-click "Databases" and select "Import Database".
  2. Navigate to the folder where you saved the Production backup, select the files, and click "Import".

• Free tier storage limit: MongoDB Atlas’s M0 free tier only allows 512MB of storage. Before syncing, check the size of your Production backup (use du -sh ./production-backup on Linux/macOS, or check folder properties on Windows) to make sure it fits.
• Permissions: Ensure your database user has read access on Production (for exporting) and readWrite access on Staging (for deleting and importing data).
• Data consistency: If Production has active writes during the export, those changes won’t be synced to Staging. For tighter consistency, run the sync during a low-traffic window, or temporarily pause writes if your business allows it.
• Index checks: Both methods will restore your collection indexes automatically, but double-check custom indexes or sharding keys after sync to make sure they’re working as expected.

内容的提问来源于stack exchange，提问作者stkvtflw