[DOCS-10354] Comment on: "manual/tutorial/backup-sharded-cluster-with-filesystem-snapshots.txt" Created: 05/Jun/17 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Rodrigo Nascimento | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | collector-298ba4e7, docs-triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Location: https://docs.mongodb.com/manual/tutorial/backup-sharded-cluster-with-filesystem-snapshots/ |
||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 2 days ago |
| Epic Link: | DOCSP-1769 |
| Description |
|
The following topic should be added to this page. Lots of people have only stopped the balancer without checking if it still active. Bringing this topic to this page will make the process more accurate and complete: Disable Balancing During Backups If MongoDB migrates a chunk during a backup, you can end with an inconsistent snapshot of your sharded cluster. Never run a backup while the balancer is active. To ensure that the balancer is inactive during your backup operation: Set the balancing window so that the balancer is inactive during the backup. Ensure that the backup can complete while you have the balancer disabled. Before starting a backup operation, confirm that the balancer is not active. You can use the following command to determine if the balancer is active: !sh.getBalancerState() && !sh.isBalancerRunning() |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |