fixed readme
This commit is contained in:
parent
41db36c7d5
commit
6ab2465cfb
@ -39,7 +39,7 @@ After that you can copy all files to the right directories with the Makefile in
|
||||
|
||||
```bash
|
||||
$ sudo make install
|
||||
````
|
||||
```
|
||||
|
||||
### 2. Initialize your Backup
|
||||
|
||||
@ -51,7 +51,7 @@ Now see if the backup itself works, by running
|
||||
```bash
|
||||
$ /usr/local/sbin/restic_backup.sh
|
||||
$ restic snapshots
|
||||
````
|
||||
```
|
||||
|
||||
### 4. Backup automatically; systemd service + timer
|
||||
Now we can do the modern version of a cron-job, a systemd service + timer, to run the backup every week!
|
||||
@ -60,7 +60,7 @@ Now simply enable the timer with:
|
||||
```bash
|
||||
$ systemctl start restic-backup.timer
|
||||
$ systemctl enable restic-backup.timer
|
||||
````
|
||||
```
|
||||
|
||||
You can see when your next backup is scheduled to run with
|
||||
```bash
|
||||
@ -83,7 +83,7 @@ You can follow the backup stdout output live as backup is running with:
|
||||
|
||||
```bash
|
||||
$ journalctl -f -u restic-backup.service
|
||||
````
|
||||
```
|
||||
|
||||
(skip `-f` to see all backups that has run)
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user