3ec85d7821
* docs: rework files structure * rewrite documentation entrypoint * update category files and use yml * add manuals entry page * update admin-manual titles and page order * create releases sections * move ssl configuration to reverse proxy * docs: update website vars and links * update release note codeblock syntax key * resurect troubleshooting guide * Update freeipa custom auth documentation * add notice about the state of the documentation * update the backup documentation * tmp: allow to deploy the website for preview * Don't use require.resolve for plugins * Update the main page link dest * update development environment title * rewrite the install/upgrade/migrate as guides * update website docs sections links * Fix urls * move release note to documentation * move home links to vars files * tmp: update deploy url * add react to tsconfig to handle jsx linting * fix: replace absolute url to relative path to files * tmp: allow CI Website dpeloy on working branch * Update release note title * use default syntax highlighting theme * update the troubleshooting guide * Wording * use CodeBlock components * Better prose * remove api_client config section * fix prose errors * update import prefix for vars file * reroder docs manuals links * use sentence capitalization for page titles * Wording * missing word * Update note about syslog log file * wording
56 lines
1.3 KiB
Markdown
56 lines
1.3 KiB
Markdown
---
|
|
title: Backup
|
|
sidebar_position: 10
|
|
---
|
|
|
|
## Create a backup
|
|
|
|
This guide walk you though the steps required to create a full backup of your installation.
|
|
|
|
:::info
|
|
|
|
Remember to **automate** and **test** the backup process and to have it run regularly. Having an **automated** and **tested** restoring process is also recommended.
|
|
|
|
:::
|
|
|
|
:::caution
|
|
|
|
Feel free to pick the backup software of your choice, but know that rsync and similar tools are not backup tools. You could use [restic](https://restic.net/) or [borg](https://borgbackup.readthedocs.io/).
|
|
|
|
:::
|
|
|
|
### Backup the configuration
|
|
|
|
On common setups, you need to backup the entire `/etc/airtime` folder.
|
|
|
|
### Backup the database
|
|
|
|
You need to backup the PostgreSQL database, which holds the entire data of your installation.
|
|
|
|
Here is an example to dump your PostgreSQL database:
|
|
|
|
```bash
|
|
sudo -u postgres pg_dump --file=libretime.sql libretime
|
|
```
|
|
|
|
Please read the `pg_dump` usage for additional details.
|
|
|
|
### Backup the storage
|
|
|
|
You need to backup the entire file storage, which holds all the files of your installation.
|
|
|
|
The path to your storage was defined during the installation process.
|
|
|
|
## Restore a backup
|
|
|
|
### Restore the configuration
|
|
|
|
Copy the backed configuration files back to the configuration folder.
|
|
|
|
### Restore the database
|
|
|
|
:construction:
|
|
|
|
### Restore the storage
|
|
|
|
:construction:
|