marco/backup.sh
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Added crontab documentation

Browse Source
This commit is contained in:
Marco Cetica 2023-03-13 17:21:05 +01:00
parent 8d0ddfee09
commit 0d01a9bbf3
No known key found for this signature in database
GPG Key ID: 0EE8E2CF315D6F8E
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
README.md
View File

@ -91,6 +91,17 @@ Elapsed time: 10 seconds.
After that, you will find the final backup archive in `/home/john/backup-<HOSTNAME>-<YYYMMDD>.tar.gz.enc`. After that, you will find the final backup archive in `/home/john/backup-<HOSTNAME>-<YYYMMDD>.tar.gz.enc`.
You can also use `backup.sh` from a crontab rule:
```sh
$> sudo crontab -e
30 03 * * 6 EKEY=$(cat /home/john/.ekey) /usr/local/bin/backup.sh -b /usr/local/etc/sources.bk john $EKEY
```
This will automatically run `backup.sh` every Saturday morning at 03:30 AM. In the example above, the encryption
key is stored in a local file(with fixed permissions) to avoid password leaking in crontab logs. You can also
adopt this practice while using the `--extract` option to avoid password leaking in shell history.
### Archive extraction ### Archive extraction
`backup.sh` can also extract the encrypted backup archive using the following syntax: `backup.sh` can also extract the encrypted backup archive using the following syntax: