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 storageengine selected (this can be done by setting the option —server.storage-engine,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 —server.storage-engine and the option —starter.data-dir to set a newdata directory.
When the server is up and running with the desired storage engine, the datacan be re-imported using the toolarangorestore.
For a list of available storage engines, and more information on theirdifferences, please refer to the Storage Enginespage under the Architecture chapter.
The MMFiles storage engine is deprecated starting with version3.6.0 and it will be removed in a future release.We recommend to switch to RocksDB even before the removal of MMFiles.