Physical Backups with Percona Backup for MongoDB
summary
Percona Backup for MongoDB adds PSMDB based physical backups using backupCursor and backupCursorExtend to capture file lists, oplog end timestamps, and required journals, then uploads WiredTiger files to S3‑style storage. Backups take similar time to logical dumps but restores scale flat: 400 GB restores drop from ~156 to ~36 minutes and 600 GB from ~325 to ~57 minutes, achieved by shutting the cluster, restoring files simultaneously to all replica set nodes, and coordinating PBM agents via storage.
AI-written summary · about
chapters (13)
- 0:00Start
- 1:27Generic information
- 9:02Logical
- 11:39Test setup
- 16:19What do you need for physical backup
- 17:10Get the files with
- 20:53Ensure consistency
- 22:08Get the files again
- 24:38Glueing it all together
- 27:00Restoration problems
- 29:19Data beyond timestamp
- 30:06Communication with the database
- 33:38User to bring up the cluster after the restore
related talks
52mPBM - The Backup Open Source Tool for MongoDB
40mMongoDB Backups Overview
07mPBM -The backup OpenSource tool for MongoDB
26mCurrent state of MongoDB Backup options
09mOpen Software for MongoDB Where Percona Fits
25mPercona Server for MongoDB: Features Overview
26mConsistent Backups for Multi-Shard MongoDB
24mMariabackup: too rarely used