1
0
Fork 0

Doc - Backup Improvement (#6697)

This commit is contained in:
sleto-it 2018-10-02 21:02:34 +02:00 committed by GitHub
parent fd800f1642
commit e8a8d5276e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 19 additions and 0 deletions

View File

@ -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.
<!-- Offline dumps -->
<!-- Hot backups -->
<!-- Cluster -->

View File

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