|
1 | 1 | Backup and Restore |
2 | 2 | ================== |
3 | 3 |
|
4 | | -Backup and restore can be done via the tools [_arangodump_](../Administration/Arangodump.md) |
5 | | -and [_arangorestore_](../Administration/Arangorestore.md). |
| 4 | +Backup and restore can be done via the tools |
| 5 | +[_arangodump_](../Administration/Arangodump.md) and |
| 6 | +[_arangorestore_](../Administration/Arangorestore.md). |
6 | 7 |
|
7 | | -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. |
| 8 | +Performing frequent backups is important and a recommended best practices that |
| 9 | +can allow you to recover your data in case unexpected problems occur. |
| 10 | +Hardware failures, system crashes, or users mistakenly deleting data can always |
| 11 | +happen. Furthermore, while a big effort is put into the development and testing |
| 12 | +of ArangoDB (in all its deployment modes), ArangoDB, as any other software |
| 13 | +product, might include bugs or errors and data loss could occur. |
| 14 | +It is therefore important to regularly backup your data to be able to recover |
| 15 | +and get up an running again in case of serious problems. |
8 | 16 |
|
9 | | -Backup-ing up your data before an ArangoDB upgrade is also a best practice. |
| 17 | +Creating backups of your data before an ArangoDB upgrade is also a best practice. |
10 | 18 |
|
11 | | -**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. |
| 19 | +{% hint 'warning' %} |
| 20 | +Making use of a high availability deployment mode of ArangoDB, like Active Failover, |
| 21 | +Cluster or data-center to data-center replication, does not remove the need of |
| 22 | +taking frequent backups, which are recommended also when using such deployment modes. |
| 23 | +{% endhint %} |
12 | 24 |
|
13 | 25 | <!-- Offline dumps --> |
14 | 26 |
|
|
0 commit comments