Hi,

You need to backup MongoDB by another way. X3 Folders, MongodB are 2 differents things.
To backup MGDB: Mongodump.exe --out <destination>
To restore: Mongodump.exe --out /data/bakup

Ludovic

Great answer Ludovic!

I would also add a couple things I remember from the mongodb training over at MongoDb University (university.mongodb.com/).

There are four ways to back up a mongo database:

1. As you stated, mongodump is technique number one. However, the training at MongoDB University was quick to point out that you should include the oplog switch. They state the following in their documentation as to why:

"Without --oplog, if there are write operations during the dump operation, the dump will not reflect a single moment in time. Changes made to the database during the update process can affect the output of the backup."

2. File system snapshot
- In order to do this, you must have journaling enabled for for MongoDb.
- You can read more about it here: docs.mongodb.org/.../
- If you are snapshotting the disks and not the entire raid then you can use something called db.fsynclock(). It will lock all the writes. You then use db.fsyncUnlock to unlock the database and allow writes to happen again.

3. MongoDB university then went on to talk about backing up from a sceondary. They stated you need to shut down, copy files then restart

4. Finally, they also stated you another hybrid situation where you want to backup a shard. First you need to shut off the balancer, then back up the config database, then backup each shard's replset, then turn the balancer back on.

Don't worry, I'm 100% confident no Sage X3 customer is sharding just yet. :)


In the end, mongodump is the easiest way, but oplog is recommended.

Hope this helps!
Bob