Community to Enterprise Upgrade Procedure
While migrating from the Community to the Enterprise Edition is supported,installing directly the Enterprise package over the Community package is notsupported. Please see below for the correct migration procedure.
Migrating from Enterprise to Community Edition is, in general, not supported. Thisis because the Community Edition does not include some features, such asSmartGraphs that, if used while the databasewas running under the Enterprise Edition, do not make easily possible theconversion of some database structures.
Upgrading from the Community to the Enterprise Edition requires unistallation ofthe Community package (can be done in a way that the database data are preserved)and installation of the Enterprise package. The upgrade can be done in alogical or in-place way. Please refer to theUpgrade Methods section for a generaldescription of the two methods. Refer to the sections below for a detailedprocedure.
Procedure for a Logical Upgrade
- Use the tool arangodump to take a backupof your data stored by your Community Edition installation
- Uninstall the ArangoDB Community Edition package
- Install the ArangoDB Enterprise Edition package(and start your Single Instance, Active Failover or Cluster)
- Restore the backup using the tool arangorestore.
Procedure for an In-Place Upgrade
- Shutdown ArangoDB and make a copy of your data directory (e.g., in Linux, byusing the cp command). If you are using a setup that involves several arangod processes(e.g. Active Failover or Cluster) please make sure all arangod processesare stopped and all the data directories in use are copied in a safe location
- Uninstall the ArangoDB Community Edition package (make sure this is done in a way thatyour database is kept on your disk, e.g. on Debian systems do not use thepurge option of dpkg or, on Windows, do not check the “Delete databases withunistallation?” option)
- Install the ArangoDB Enterprise Edition package
- If you are moving from version A to version B, where B > A, start arangod onyour data directory with the option
—database.auto-upgrade
(in addition toany other options you are currently using). The server will stop after a while(check the log file of arangod as it should contain relevant information aboutthe upgrade). If you are using a setup that involves several arangod processes(e.g. Active Failover or Cluster) this step has to be repeated for all _arangod_processes - Start ArangoDB Enterprise Edition(in the same way you were starting ArangoDB Community Edition)