[DOCS-6012] Backup Methods: shutdown secondary no longer useful for mongodump, only file copy Created: 11/Aug/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: Kevin Pulo Assignee: Kay Kim (Inactive)
Resolution: Won't Fix Votes: 0
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   

http://docs.mongodb.org/manual/core/backups/#backup-with-mongodump states

Alternatively, you can shut down a secondary and use mongodump with the data files directly. If you shut down a secondary to capture data with mongodump ensure that the operation can complete before its oplog becomes too stale to continue replicating.

This is no longer true with version 3.0, which has dropped support for the --dbpath option on mongodump.

However, stopping a secondary is a useful approach when backing up by copying the files. Therefore, the above quote should be removed from the "Backup with mongodump" section, and added (with necessary tweaks) to the "Backup by Copying Underlying Data Files" section, probably in or after the paragraph starting "If your storage system does not support snapshots..."



 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:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.