From e8a8d5276e408fc9c5c172bb7948efee4c90ddab Mon Sep 17 00:00:00 2001 From: sleto-it <31849787+sleto-it@users.noreply.github.com> Date: Tue, 2 Oct 2018 21:02:34 +0200 Subject: [PATCH] Doc - Backup Improvement (#6697) --- .../Books/Manual/BackupRestore/README.md | 17 +++++++++++++++++ Documentation/Books/Manual/SUMMARY.md | 2 ++ 2 files changed, 19 insertions(+) create mode 100644 Documentation/Books/Manual/BackupRestore/README.md diff --git a/Documentation/Books/Manual/BackupRestore/README.md b/Documentation/Books/Manual/BackupRestore/README.md new file mode 100644 index 0000000000..b7035e364e --- /dev/null +++ b/Documentation/Books/Manual/BackupRestore/README.md @@ -0,0 +1,17 @@ +Backup and Restore +================== + +Backup and restore can be done via the tools [_arangodump_](../Administration/Arangodump.md) +and [_arangorestore_](../Administration/Arangorestore.md). + +Performing frequent backups is important and a recommended best practices that can allow you to recover your data in case unexpected problems occur. Hardware failures, system crashes, or users mistakenly deleting data can always happen. Furthermore, while a big effort is put into the development and testing of ArangoDB (in all its deployment modes), ArangoDB, as any other software product, might include bugs or errors. It is therefore important to regularly backup your data to be able to recover and get up an running again in case of serious problems. + +Backup-ing up your data before an ArangoDB upgrade is also a best practice. + +**Note:** making use of a high availability deployment mode of ArangoDB, like Active Failover, Cluster or data-center to data-center replication, does not remove the need of taking frequent backups, which are recommended also when using such deployment modes. + + + + + + diff --git a/Documentation/Books/Manual/SUMMARY.md b/Documentation/Books/Manual/SUMMARY.md index fbb8b80542..844afd0ddf 100644 --- a/Documentation/Books/Manual/SUMMARY.md +++ b/Documentation/Books/Manual/SUMMARY.md @@ -144,6 +144,8 @@ * [TLS](Deployment/Kubernetes/Tls.md) * [Troubleshooting](Deployment/Kubernetes/Troubleshooting.md) # +* [Backup & Restore](BackupRestore/README.md) +# * [Administration](Administration/README.md) * [Web Interface](Administration/WebInterface/README.md) * [Dashboard](Administration/WebInterface/Dashboard.md)