[DOCS-6230] Add note regarding storage.bson to Cloud Manager backup/restore considerations for directoryPerDB Created: 17/Sep/15 Updated: 27/Jul/16 Resolved: 07/Apr/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager, Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Roger McCoy (Inactive) | Assignee: | Anthony Sansone (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Days since reply: | 8 years, 21 weeks, 6 days ago | ||||||||||||
| Epic Link: | C/OM Backup | ||||||||||||
| Description |
|
Cloud Manager doc section: Starting with 3.0, backup files include a "storage.bson" file. If using directoryPerDB and manually moving files to subdirectories, the metadata in storage.bson will prevent the mongod from starting. Suggest to first restore to a mongod without directoryPerDB, then sync or dump/restore to a mongod with directoryPerDB. |