docs: rename documentation files
Co-authored-by: Zachary Klosko <zklosko@users.noreply.github.com>
This commit is contained in:
parent
8d8e55f236
commit
c4cdb94fab
34 changed files with 0 additions and 1341 deletions
65
docs/server-config/backing-up-the-server.md
Normal file
65
docs/server-config/backing-up-the-server.md
Normal file
|
@ -0,0 +1,65 @@
|
|||
---
|
||||
layout: article
|
||||
title: Backing Up Libretime
|
||||
category: admin
|
||||
---
|
||||
|
||||
> At the moment, there is not a way to automatically restore a Libretime backup.
|
||||
> To restore a failed Libretime instance, install a fresh copy, go through the
|
||||
> standard setup process, and reupload the backed-up media files. A _Watched Folders_
|
||||
> feature is [currently in development](https://github.com/LibreTime/libretime/issues/70).
|
||||
|
||||
A backup script is supplied for your convenience in the _utils/_ folder of the Libretime repo.
|
||||
Run it using:
|
||||
|
||||
```
|
||||
sudo bash libretime-backup.sh # backs up to user's home folder
|
||||
# or
|
||||
sudo bash libretime-backup.sh /backupdir/
|
||||
```
|
||||
|
||||
The backup process can be automated with Cron. Simply add the following to the root user's
|
||||
crontab with `sudo crontab -e`:
|
||||
|
||||
```
|
||||
0 0 1 * * /locationoflibretimerepo/libretime/backup.sh
|
||||
```
|
||||
|
||||
> For more information on how Cron works, check out [this Redhat guide](https://www.redhat.com/sysadmin/automate-linux-tasks-cron).
|
||||
|
||||
If you wish to deploy your own backup solution, the following files and folders need to
|
||||
be backed up.
|
||||
|
||||
```
|
||||
/srv
|
||||
/airtime
|
||||
/stor
|
||||
/imported - Successfully imported media
|
||||
/organize - A temporary holding place for uploaded media as the importer works
|
||||
/etc
|
||||
/airtime
|
||||
airtime.conf - The main Libretime configuration
|
||||
icecast_pass - Holds the password for the Icecast server
|
||||
liquidsoap.cfg - The main configuration file for Liquidsoap
|
||||
```
|
||||
|
||||
In addition, you should keep a copy of the database current to the backup. The below code
|
||||
can be used to export the Libretime database to a file.
|
||||
|
||||
```
|
||||
sudo -u postgres pg_dumpall filename
|
||||
# or to a zipped archive
|
||||
sudo -u postgres pg_dumpall | gzip -c > archivename.gz
|
||||
```
|
||||
|
||||
It is recommended to use an incremental backup technique to synchronize
|
||||
the your LibreTime track library with a backup server regularly. (If
|
||||
the backup server also contains an LibreTime installation, it should be possible
|
||||
to switch playout to this second machine relatively quickly, in case of a
|
||||
hardware failure or other emergency on the production server.)
|
||||
|
||||
Two notible backup tools are [rsync](http://rsync.samba.org/) (without version control) and
|
||||
[rdiff-backup](http://www.nongnu.org/rdiff-backup/) (with version control). _rsync_ comes
|
||||
preinstalled with Ubuntu Server.
|
||||
|
||||
> **Note:** Standard _rsync_ backups, which are used by the backup script, cannot restore files deleted in the backup itself
|
Loading…
Add table
Add a link
Reference in a new issue