Connect to your ESX through ssh (ssh needs to be enable first via vcenter),

Go to your VM datastore,

Execute the following command on the disk: vmkfstools -i disk.vmdk Disk.vmdk,

Detach disk.vmdk via vcenter and attach Disk.vmdk

Backup and Restore Vulture's MongoDB Internal database

If mongod service is not terminated correctly (like when a hard shutdown occurs), it will fail to start on the next boot. This issue comes from MongoDB's storage engine, WiredTiger, which keeps its cache in memory.

To prevent Vulture from stopping to work. We wrote a cronjob that creates a mongo dump from Vulture database.

This job is ran every hour and only keeps the last two backups which are located at: /var/db/mongodb_dumps/.

WARNING: only vulture database is dumped. If you want a backup of the log database you need to run your own scripts.

Restore database

If your MongoDB server refuses to start, there are two scripts located at /home/vlt-sys/recover/ that will restore the vulture database.

You can run those scripts with root user on your vulture nodes depending on which status they have in the MongoDB Replicatset in the following order:

1) If you have a Vulture cluster, for each of your mongoDB secondary nodes, you need to run: