2020-06-19 22:15:00 +02:00
# Restic for YunoHost
2020-02-23 12:02:10 +01:00
2021-02-15 22:20:47 +01:00
[](https://github.com/YunoHost-Apps/restic_ynh/releases)
2020-02-23 12:02:10 +01:00
[](https://github.com/YunoHost-Apps/restic_ynh/milestones)
[](https://dash.yunohost.org/appci/app/restic)
[](https://raw.githubusercontent.com/YunoHost-Apps/restic_ynh/master/LICENSE)
2020-11-12 08:23:18 +01:00
[](https://github.com/YunoHost-Apps/restic_ynh/issues)
2020-02-23 12:02:10 +01:00
[](https://install-app.yunohost.org/?app=restic)
2020-11-12 08:23:18 +01:00
> *This package allows you to install Restic quickly and simply on a YunoHost server.
2020-06-19 22:15:00 +02:00
If you don't have YunoHost, please consult [the guide ](https://yunohost.org/#/install ) to learn how to install it.*
## Overview
A [Restic ](https://restic.net/ ) package for YunoHost (heavily inspired by [the Borg package ](https://github.com/YunoHost-Apps/borg_ynh/ )).
2020-03-03 19:46:44 +01:00
Restic is a backup tool that can make local and remote backups.
This package uses restic to make backups to a sftp server.
2021-02-28 16:38:35 +01:00
The package does not handle local backups yet but you can work around that by using the local sftp server as target server (see my comment [here ](https://forum.yunohost.org/t/sauvegarde-yunohost-avec-restic/10275/33 )).
2020-02-23 12:02:10 +01:00
## Usage
If you want to backup your server A onto the server B.
2020-06-19 22:15:00 +02:00
## Setup Restic app on Server A
2020-02-23 12:02:10 +01:00
Firstly set up this app on the server A you want to backup:
```
$ yunohost app install https://github.com/YunoHost-Apps/restic_ynh
2020-02-23 12:38:09 +01:00
Indicate the server where you want put your backups: serverb.domain.tld
sftp port of your server (default: 22): 2222
2020-03-02 22:30:12 +01:00
The directory where you want your backup repositories to be created in (default: ./): ./servera.domain.tld
2020-02-23 12:02:10 +01:00
Indicate the ssh user to use to connect on this server: servera
2020-02-23 12:38:09 +01:00
You are now about to define a new user password. The password should be at least 8 characters - though it is good practice to use longer password (i.e. a passphrase) and/or to use various kind of characters (uppercase, lowercase, digits and special characters).
Indicate a strong passphrase, that you will keep preciously if you want to be able to use your backups:
Would you like to backup your YunoHost configuration ? [yes | no] (default: yes):
Would you like to backup mails and user home directory ? [yes | no] (default: yes):
Which apps would you backup (list separated by comma or 'all') ? (default: all): gitlab,blogotext,sogo
Allow backup method to temporarily use more space? [yes | no] (default: yes):
2020-04-12 17:13:54 +02:00
Indicate the backup frequency (see systemd OnCalendar format) (default: *-* -* 0:15:00): *-* -* 0:05
Indicate the backup check frequency (see systemd OnCalendar format) (default: Sat *-* -8..31 3:15:00):
Indicate the complete backup check frequency (see systemd OnCalendar format) (default: Sun *-* -1..7 3:15:00):
2020-02-23 12:02:10 +01:00
```
You can schedule your backup by choosing an other frequency. Some example:
Monthly :
Weekly :
Daily : Daily at midnight
Hourly : Hourly o Clock
Sat *-* -1..7 18:00:00 : The first saturday of every month at 18:00
4:00 : Every day at 4 AM
5,17:00 : Every day at 5 AM and at 5 PM
2020-03-02 22:30:12 +01:00
See here for more info : https://wiki.archlinux.org/index.php/Systemd/Timers#Realtime_timer
2020-02-25 13:35:23 +01:00
After each invocation an e-mail will be sent to root@yourdomain.tld with the execution log.
2020-03-02 22:30:12 +01:00
Restic can check backups consistency and verify the actual backed up data has not been modified.
If you use the default values for the backup checks frequencies, a full check will be made on the first day of each month and a simple check will be made on each one of the three remaining weeks of the month.
2020-02-23 12:02:10 +01:00
At the end of the installation, the app displays the public_key and the user to give to the person who has access to the server B.
You should now authorize the public key for user `servera` on server B by logging into server B with user `servera` and running:
```
2020-02-23 12:38:09 +01:00
mkdir ~/.ssh -p 2>/dev/null
touch ~/.ssh/authorized_keys
2020-02-23 12:02:10 +01:00
chmod u=rw,go= ~/.ssh/authorized_keys
cat < < EOPKEY > > ~/.ssh/authorized_keys
< paste here the privakey displayed at the end of installation >
EOPKEY
```
2020-03-02 22:30:12 +01:00
If you don't find the mail and you don't see the message in the log bar you can find the public_key with this command:
2020-02-23 12:02:10 +01:00
```
cat /root/.ssh/id_restic_ed25519.pub
```
2020-02-23 12:38:09 +01:00
## (Optional) set sftp jail on server B
2020-02-23 12:02:10 +01:00
To improve security, make sure user `servera` can only do sftp and can only access his home directory on server B.
2020-02-23 12:38:09 +01:00
This is how you would do it on Debian/Ubuntu, otherwise refer to your distribution manual (don't forget to replace `servera` with the real username)
2020-02-23 12:02:10 +01:00
```
cat < < EOCONFIG > > /etc/ssh/sshd_config
Match User servera
ChrootDirectory %h
ForceCommand internal-sftp
AllowTcpForwarding no
X11Forwarding no
EOCONFIG
service ssh restart
```
## Test
At this step your backup should schedule.
If you want to be sure, you can test it by running on server A:
```
2020-03-02 22:30:12 +01:00
systemctl start restic.service
2020-02-23 12:02:10 +01:00
```
2020-03-02 22:30:12 +01:00
Next you can verify the backup contents by running on server A
2020-02-23 12:02:10 +01:00
```
2020-02-23 19:24:50 +01:00
restic -r sftp:serverb.domain.tld:servera.domain.tld/auto_conf snapshots
2020-02-23 12:02:10 +01:00
```
2020-02-23 12:38:09 +01:00
Replace `auto_conf` with `auto_<app>` if you did not choose to backup configuration but only applications.
2020-03-02 22:30:12 +01:00
If you want to check the backups consistency:
```
systemctl start restic_check.service
```
2020-06-19 22:15:00 +02:00
If you want to make a complete check of the backups - keep in mind that this reads all the backed up data, it can take some time depending on your target server upload speed (more on this topic in [the Restic documentation ](https://restic.readthedocs.io/en/latest/045_working_with_repos.html#checking-integrity-and-consistency ):
2020-03-02 22:30:12 +01:00
```
systemctl start restic_check_read_data.service
```
2020-02-23 12:02:10 +01:00
## Edit the apps list to backup
```
yunohost app setting restic apps -v "nextcloud,wordpress"
```
## Backup on different server, and apply distinct schedule for apps
2020-06-19 22:15:00 +02:00
You can setup the Restic app several times on the same server so you can backup on several server or manage your frequency backup differently for specific part of your server.
#### Supported architectures
* x86-64 - [](https://ci-apps.yunohost.org/ci/apps/restic/)
* ARMv8-A - [](https://ci-apps-arm.yunohost.org/ci/apps/restic/)
## Links
* Report a bug: https://github.com/YunoHost-Apps/restic_ynh/issues
* App website: https://restic.net/
* Upstream app repository: https://github.com/restic/restic
* YunoHost website: https://yunohost.org/
---
Developer info
----------------
Please send your pull request to the [testing branch ](https://github.com/YunoHost-Apps/restic_ynh/tree/testing ).
To try the testing branch, please proceed like that.
```
sudo yunohost app install https://github.com/YunoHost-Apps/restic_ynh/tree/testing --debug
or
sudo yunohost app upgrade restic -u https://github.com/YunoHost-Apps/restic_ynh/tree/testing --debug
```
