Details
-
Improvement
-
Resolution: Done
-
Major - P3
-
None
-
None
-
None
-
*Location*: http://docs.mongodb.org/manual/administration/backups/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1364.172 Safari/537.22
*Referrer*: http://docs.mongodb.org/manual/contents/
*Screen Resolution*: 1920 x 1080
*repo*: docs
*source*: administration/backups
*Location*: http://docs.mongodb.org/manual/administration/backups/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1364.172 Safari/537.22 *Referrer*: http://docs.mongodb.org/manual/contents/ *Screen Resolution*: 1920 x 1080 *repo*: docs *source*: administration/backups
Description
binary database dumps are comparatively small, because they don’t include index content or pre-allocated free space, and record padding. However, it’s impossible to capture a copy of a running system that reflects a single moment in time using a binary dump.
Point-in-time snapshots are possible using mongodump --oplog (since 1.7.4) if the instance is running as part of a replica set.
Both methodologies have advantages and disadvantages
Even if my assertion above is shown to be incorrect, only a single disadvantage is listed for each strategy.