[DOCS-5861] Comment on: "mms/core/backup-preparations.txt" Created: 16/Jul/15  Updated: 24/Feb/16  Resolved: 16/Jul/15

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Andrew Davidson Assignee: Allison Reinheimer Moore
Resolution: Done Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

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


Issue Links:
Related
Participants:
Days since reply: 8 years, 30 weeks, 6 days ago

 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.)"


Generated at Thu Feb 08 07:51:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.