[DOCS-5712] Online backup of OpsManager and fsyncLock Created: 24/Jun/15 Updated: 11/Jan/17 Resolved: 30/Oct/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager, manual |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ronan Bohan | Assignee: | Bob Grabar |
| 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, 34 weeks ago | ||||||||
| Description |
|
The documentation page for backup up OpsManager in the online manual, specifically the section 'Online Backup' instructs the user to use 'fsyncLock' before starting the backup. This recommendation however applies only to MMAPv1. If the OpsManager databases are using WiredTiger as the storage engine the fsyncLock command cannot guarantee that the storage layer is quiesced. See this link for details. As such 'Online Backup' should have a disclaimer, stating that it is only appropriate if the databases are using MMAPv1. |