From c68577757613f03f5514e070ee41abccb9f538f9 Mon Sep 17 00:00:00 2001 From: sleto-it <31849787+sleto-it@users.noreply.github.com> Date: Tue, 5 Feb 2019 10:49:25 +0100 Subject: [PATCH] Doc - More downgrade options (solving challenging situations) (#7988) (#8107) --- .../Books/Manual/Downgrading/README.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/Documentation/Books/Manual/Downgrading/README.md b/Documentation/Books/Manual/Downgrading/README.md index 2fff6ce5a2..b51b7390ca 100644 --- a/Documentation/Books/Manual/Downgrading/README.md +++ b/Documentation/Books/Manual/Downgrading/README.md @@ -62,3 +62,20 @@ or Cluster setups (because in this case you do not have a copy of the data direc 5. Start ArangoDB on the data directory that you have backup-ed up (at filesystem level) before the upgrade. As an extra precaution, please first take a new copy of this directory and move it to a safe place. + +### Other possibilities + +If you have upgraded by mistake, and: + +- your data directory has been upgraded already +- it is not possible for you to follow any of the + [Supported Downgrade Procedures](#supported-downgrade-procedures) because: + - you do not have a _dump_ backup taken using the old ArangoDB version + - you do not have a copy of your data directory taken after stopping the old ArangoDB + process and before the upgrade + +...one possible option to downgrade could be to export the data from the new ArangoDB version +using the tool _arangoexport_ and reimport it using the tool _arangoimport_ in the old +version (after having installed and started it on a clean data directory). This method will +require some manual work to recreate the structure of your collections and your indices - but +it might still help you solving an otherwise challenging situation.