[DOCS-5918] Sharded cluster backup procedure Created: 28/Jul/15  Updated: 30/Oct/23  Resolved: 01/Nov/22

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Bug Priority: Major - P3
Reporter: Ricardo Lorenzo Assignee: Kay Kim (Inactive)
Resolution: Won't Fix Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 1 year, 14 weeks, 1 day ago
Epic Link: DOCSP-1769

 Description   

In relation to the backup procedure described in the online documentation (https://docs.mongodb.org/manual/tutorial/backup-sharded-cluster-with-filesystem-snapshots/), I have the following concerns:

  • You could lock a shard indefinitely because of SERVER-14396
  • After stopping the balancer, chunk moves still can occur if auto-split option is enabled.
  • The data on each shard backup could reflect different points in time. However, there is a warning on the document pointing that.
  • The balancer will write the chunk migrations using w:2 write concern. If you have more than one secondary or a hidden member that could be problematic.


 Comments   
Comment by Education Bot [ 01/Nov/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!

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