Mongodb version 3+ filestructure is different to previous versions

From: LynnyK <lyn.duong@xxxxxxxxx>
To: mongodb-user <mongodb-user@xxxxxxxxxxxxxxxx>
Date: Mon, 18 Apr 2016 20:58:22 -0700 (PDT)
Why ads?
Hi,

I have Mongodb 2.6 version installed on server and the physical file for 
each database consists of
databasename.0
databasename.1
databasename.2 ...
and 1 .ns file
databasename.ns

I've now got another database server with 3.2 installed and noticed the 
filestructure is completely different.
The files i can see are a bunch of collection-nn-nnnnnnnnnnnnnnnn.wt and 
index-nn-nnnnnnnnnnnnnnnnnnnnnn.wt files.

In the earlier versions, if I wanted to copy the a database from one server 
to the other, I can just copy the files named with the same name, not so 
with version 3.

Is there a configuration or parameter to set so that the filestructure 
contained by database??

Does anyone understand the underlying file structure who can help me?


Thanks
Lyn

-- 
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: https://docs.mongodb.org/manual/support/
--- 
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+unsubscribe@xxxxxxxxxxxxxxxx.
To post to this group, send email to mongodb-user@xxxxxxxxxxxxxxxx.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/cf70b4c3-42b2-4f70-bbde-10b33189acb7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Why ads?