From 380acd343da55d81f2555397efe7854668f93fb5 Mon Sep 17 00:00:00 2001 From: Khrys42 Date: Wed, 11 Aug 2021 18:37:21 +0200 Subject: [PATCH] Test --- .../07.specific_use_cases/05.backups/01.evaluate/evaluate.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/01.administrate/07.specific_use_cases/05.backups/01.evaluate/evaluate.md b/pages/01.administrate/07.specific_use_cases/05.backups/01.evaluate/evaluate.md index 5a865cfd..0ccfb652 100644 --- a/pages/01.administrate/07.specific_use_cases/05.backups/01.evaluate/evaluate.md +++ b/pages/01.administrate/07.specific_use_cases/05.backups/01.evaluate/evaluate.md @@ -13,7 +13,7 @@ page-toc: In the context of self-hosting, backups are an important element to compensate for unexpected events (fire, database corruption, loss of access to the server, compromised server...). The backup policy to implement depends on the importance of the services and data you manage. For example, backing up a test server will be of little interest, while you will want to be very careful if you are managing critical data for an association or a company - and in such cases, you will want to store the backups *in a different location or locations*. -## What is a good backup? +## What is a good backup ? A good backup consists of at least **3 copies of the data** (including the original data), on at least **2 separate storages**, in at least **2 separate locations** (far enough apart) and ideally with 2 separate methods. If your backups are encrypted **these rules also apply to the decryption phrase/key**. A good backup is also in many cases, a recent backup, so it takes either a lot of rigor or **automate** the process.