-
Type: New Feature
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: mongorestore
Is there a smart way to do this?
Can we force the config database to be restored first and then force a metadata update before loading the rest of the dump?
- depends on
-
SERVER-4087 Add setting to disable auto-splitting and auto-migrations
- Closed
-
TOOLS-127 Add option to mongorestore to exclude the given database (or databases)
- Closed
- is depended on by
-
SERVER-4992 Disable dropDatabase command on "config" if sharded collections exist with data
- Closed
- is duplicated by
-
SERVER-5734 mongodump shouldn't export config database by default
- Closed
- is related to
-
TOOLS-116 Ability to mongorestore to shards with different names
- Closed