mongorestore error: Don't know what to do with

Question

Closed. This question needs debugging details. It is not currently accepting answers.

---

Want to improve this question? Update the question so it's on-topic for Stack Overflow.

Closed 3 years ago.

I have mongo DB installed in the following path c:\mongodb\bin. I have configured my environment variable PATH in advanced settings.I also have mongod running .When I run the following command mongorestore dump from the following path c:\hw1-1\dump (This contains the BSON files) I'm getting this error:

Don't know what to do with the dump file

I have referred to this thread to check my path.

Answer 1

in mongodb 3.0 or above, we should specify the database name to restore

mongorestore -d [your_db_name] [your_dump_dir]

Answer 2

I got this error when I had a collection matching the name of the one I was trying to restore present in Mongo ended up going into Mongo and deleting it using db.m101.drop();

Answer 3

If you're using mongoexport to create the dump, be sure to use mongoimport rather than mongorestore to load it.

Answer 4

You probably saw this error:

ERROR: don't know what to do with file [dump]

Which means in this case, that there is no file or directory called dump in your current working directory. So, Try this first cd c:/hw1-1/ (or whatever the correct syntax is on Windows, I can't test it.) Alternatively you can specify the full path to the dump directory:

mongorestore c:/hw1-1/dump

Answer 5

I'm on version 3.2 windows and my mongorestore seems to have a bug:

If I specify /db:database_name or /d database_name I get the error:

don't know what to do with subdirectory "dump\database_name", skipping...

Instead if I let it run on the whole dump directory it seems to work. The command I used is:

mongorestore /host:remote_host dump

My current directory structure is:

.
..
dump
dump\database_name

Answer 6

This error message "don't know what to do with file" can also occur if you have a BSON file that does not have a .bson file extension.

Generally this isn't a problem since mongodump generates the files with .bson extensions, but in my case I had a BSON file that was not generated by mongodump and had a different file extension.