You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
40 lines
1.2 KiB
40 lines
1.2 KiB
# Cron
|
|
|
|
Often it is usefull to trigger backups autmatically. For this we can specify a `cron` attribute to each location.
|
|
|
|
> Available since version 0.18
|
|
|
|
```yaml | .autorestic.yml
|
|
locations:
|
|
my-location:
|
|
from: /data
|
|
to: my-backend
|
|
cron: '0 3 * * 0' # Every Sunday at 3:00
|
|
```
|
|
|
|
Here is a awesome website with [some examples](https://crontab.guru/examples.html) and an [explorer](https://crontab.guru/)
|
|
|
|
## Installing the cron
|
|
|
|
To actually enable cron jobs you need something to call `autorestic cron` on a timed shedule. Note that the shedule has nothing to do with the `cron` attribute in each location. My advise would be to trigger the command every 5min, but if you have a cronjob that runs only once a week, it's probably enough to shedule it once a day.
|
|
|
|
### Crontab
|
|
|
|
Here is an example using crontab, but systemd would do too.
|
|
|
|
First, open your crontab in edit mode
|
|
|
|
```bash
|
|
crontab -e
|
|
```
|
|
|
|
Then paste this at the bottom of the file and save it. Note that in this specific example the `.autorestic.yml` is located in `/srv/`. You need to modify that part of course to fit your config file.
|
|
|
|
```bash
|
|
0 * * * * /usr/local/bin/autorestic -c /srv/.autorestic.yml
|
|
```
|
|
|
|
Now you can add as many `cron` attributes as you wish ⏱
|
|
|
|
> :ToCPrevNext
|