Hawkin
/
arangodb
mirror of https://gitee.com/bigwinds/arangodb
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Doc - More downgrade options (solving challenging situations) (#7988) (#8107)

This commit is contained in:
sleto-it 2019-02-05 10:49:25 +01:00 committed by GitHub
parent 38c8b992bd
commit c685777576
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
Documentation/Books/Manual/Downgrading/README.md
View File

@ -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.