Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
None
-
None
-
*Location*: https://docs.opsmanager.mongodb.com/v1.6/core/backup-preparations/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.152 Safari/537.36
*Referrer*: https://docs.opsmanager.mongodb.com/current/search/?query=for%20a%20cluster%20or%20replica%20set%20that%20runs%20on%20MongoDB%203.0
*Screen Resolution*: 1440 x 900
*repo*: REPONAME
*source*: core/backup-preparations
*Location*: https://docs.opsmanager.mongodb.com/v1.6/core/backup-preparations/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.152 Safari/537.36 *Referrer*: https://docs.opsmanager.mongodb.com/current/search/?query=for%20a%20cluster%20or%20replica%20set%20that%20runs%20on%20MongoDB%203.0 *Screen Resolution*: 1440 x 900 *repo*: REPONAME *source*: core/backup-preparations
Description
We should add a call-out box under https://docs.opsmanager.mongodb.com/v1.6/core/backup-preparations/#storage-engine that explains:
"The storage engine format chosen for a Backup is independent from the storage engine the Backup database uses. (Foe example, if the Backup Database <link to Backup Database docs> uses the MMAPv1 storage engine, it can store backup snaphots for WiredTiger backup jobs in its blockstore.)"