ArangoDB v3.6 reached End of Life (EOL) and is no longer supported.

This documentation is outdated. Please see the most recent version here: Latest Docs

Switching the storage engine

In order to use a different storage engine with an existing data directory, it is required to first create a logical backup of the data using the tool arangodump.

After that, the arangod server process should be restarted with the desired storage engine selected (this can be done by setting the option, or by editing the configuration file of the server) and using a non-existing data directory. If you have deployed using the Starter, instead of arangod you will need to run arangodb, and pass to it the option and the option to set a new data directory.

When the server is up and running with the desired storage engine, the data can be re-imported using the tool arangorestore.

For a list of available storage engines, and more information on their differences, please refer to the Storage Engines page under the Architecture chapter.

The MMFiles storage engine is deprecated starting with version 3.6.0 and it will be removed in a future release. We recommend to switch to RocksDB even before the removal of MMFiles.