MongoDB Backups Overview
summary
Six concrete options: mongodump (logical, simple, OK for small DBs but slow due to read‑amplification), stopping a secondary and copying DB files (physical, consistent at shutdown), LVM snapshot (fast for very large datasets if extra disk exists), WiredTiger snapshot (Percona/enterprise), Percona Backup for MongoDB and MongoDB Ops Manager/Atlas (agents, S3 support, and the only built‑in systems offering point‑in‑time restore and proper multi‑shard/transaction handling). Oplog capture is required for consistency; oplog volume can exceed the dataset.
AI-written summary · about
chapters (27)
- 0:00Intro
- 0:53Agenda
- 1:15Terminology: Logical vs. Physical Backup
- 2:43Terminology: Consistent Backup
- 3:54Terminology: Hot Backup
- 5:05Terminology: Snapshot
- 5:51Terminology: Point-in-time Restore
- 7:05MongoDB Oplog for Replication
- 9:30MongoDB Oplog - Extra Use in Backups
- 12:31MongoDB Transactions
- 16:47Backup & Restore Solution List
- 19:09Why so many options?
- 20:15Stop secondary: Copy files
- 22:41i Filesystem snapshot
- 24:42Wired Tiger Snapshot ('Hot backup')
- 26:02Percona Backup for MongoDB
- 27:05Hot Backups (no downtime)
- 28:07Cluster-consistent Backups
- 29:55Admin / Installation
- 30:34Supported Backup Storage types
- 31:16Source Licence Type
- 31:3710 Speed - How much have you got?
- 32:42Logical vs. Physical Backup Speed
- 34:36Logical vs. Physical Restore Speed
- 35:35Medium-Small to Medium-Large
- 37:08Point-in-time Restore consideration
- 38:36Large (Many TBs per server)
related talks
26mCurrent state of MongoDB Backup options
39mPhysical Backups with Percona Backup for MongoDB
26mConsistent Backups for Multi-Shard MongoDB
52mPBM - The Backup Open Source Tool for MongoDB
07mPBM -The backup OpenSource tool for MongoDB
50mDeploying #MongoDB on public clouds: Architecture and options
09mOpen Software for MongoDB Where Percona Fits
49mCreating Backups for Various Transactional DBMSs Under Load