Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

340
Views
mongodump - The filename, directory name, or volume label syntax is incorrect

When trying to do a mongodump we get this error:

$mongodump --host <host> -db <db> -out C:/ --username username --password password

The output is:

Failed: error dumping metadata: error creating m
etadata file C:\590690e1231230279214b1319f2\_Join:users:_Role.metadata.json
: open C:\590690e1231230279214b1319f2\_Join:users:_Role.metadata.json: The
filename, directory name, or volume label syntax is incorrect.

Is there a work-around for this when using a Windows OS machine? This db is a database of a parse-server

over 4 years ago · Santiago Trujillo
2 answers
Answer question

0

Since mongoDB 3.2, the --archive option is introduced, which allows writing dump into a single file instead of a directory, e.g.:

$mongodump --host <host> --db <db> --archive <archive_file_name> --username <username> --password <password>

Note that the same option is used to specify the dump file to restore when using mongorestore.

over 4 years ago · Santiago Trujillo Report

0

good day.. as you can see in the error your command is trying to dump _Join:users:_Role Collection which is invalid filename to mongodb, first rename those collection and try to dump again, or else try to dump the collections one by one. make sure not to include those invalid filename unless you rename them

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!