Details
-
Task
-
Resolution: Duplicate
-
Major - P3
-
None
-
None
-
None
Description
The backup sharded cluster with database dumps has a number of issues:
1) In addition to stopping the balancer, it should be noted that the current balancer round also needs to complete before continuing.
2) It uses the word lock when actually it means shutdown. The word lock is associated with the fsyncLock command and is confusing in this case. It would be simpler to just say shutdown.
3) The mongodump command suggests dumping the dbpath directly. This is no longer possible in MongoDB 3 and above. The --dbpath command was removed to simplify pluggable storage engine support:
$ mongodump --journal --dbpath ./data/db --out /tmp/backup
|
2015-03-23T13:05:49.847+0000 error parsing command line options: --dbpath and related flags are not supported in 3.0 tools.
|
See http://dochub.mongodb.org/core/tools-dbpath-deprecated for more information
|
2015-03-23T13:05:49.848+0000 try 'mongodump --help' for more information
|
To perform this mongodump procedure for 3.0 and above:
- the mongod process would need to be restarted on a different port and without the replset option.
-OR- - dump a running instance with mongodump --oplog. For large replica sets, this option would be discouraged as it can cause performance problems when scanning all the database / collections / documents.
4) If the end user can simply shutdown the server, wouldn't a straight cp / tar / rsync of the dbpath be quicker?
Attachments
Issue Links
- duplicates
-
DOCS-4680 Update Backup/Restore sharded cluster docs for new mongodump tool
-
- Closed
-