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?
Add setting to disable auto-splitting and auto-migrations
Add option to mongorestore to exclude the given database (or databases)
Disable dropDatabase command on "config" if sharded collections exist with data
mongodump shouldn't export config database by default
Ability to mongorestore to shards with different names