docs: create backups
This commit is contained in:
parent
c17c4ee30f
commit
7dc684f8e0
32
en/backups.md
Normal file
32
en/backups.md
Normal file
@ -0,0 +1,32 @@
|
|||||||
|
---
|
||||||
|
title: Backups
|
||||||
|
description:
|
||||||
|
published: true
|
||||||
|
date: 2023-12-21T09:51:57.726Z
|
||||||
|
tags:
|
||||||
|
editor: markdown
|
||||||
|
dateCreated: 2023-12-21T09:51:57.726Z
|
||||||
|
---
|
||||||
|
|
||||||
|
# Backups
|
||||||
|
|
||||||
|
The server data and configurations are backed up regularly. There is currently a backup server.
|
||||||
|
|
||||||
|
## Technology <a name="technic" id="technic"></a>
|
||||||
|
|
||||||
|
[borgbackup](https://www.borgbackup.org/) is used via ssh with a passphrase for encryption. All backups are therefore completely encrypted on the target devices and cannot be read without a key + passphrase. In a worst-case scenario, restoring the entire server requires a number of manual steps and will certainly take some time. However, individual files and configurations can be read and restored quickly and easily. *borgbackup* works with compressed, incremental backups, which not only saves storage space, but also enables older versions to be restored. Currently, the status of the last two days, one week ago, one month ago and one year ago is stored.
|
||||||
|
|
||||||
|
## Backup server <a name="server" id="server"></a>
|
||||||
|
|
||||||
|
| # | interval | server data | location |
|
||||||
|
| :-: | :- | :-: | :-: |
|
||||||
|
| 1 | Daily at 04:00 | **all** | private home server |
|
||||||
|
| 2 | Daily at 04:00| **all**| private home server |
|
||||||
|
| 3 | Mondays and Thursdays at 02:00 | **all** | private home server |
|
||||||
|
|
||||||
|
> For members: [offer your own backup server](/en/internal/backup)
|
||||||
|
{.is-info}
|
||||||
|
|
||||||
|
## Manual backup
|
||||||
|
|
||||||
|
The backup of [Server #1](/en/backups#server) is also copied to an external hard disk ~1x a week.
|
Loading…
Reference in New Issue
Block a user