Often it is usefull to trigger backups autmatically. For this we can specify a `cron` attribute to each location.
Often it is usefully to trigger backups automatically. For this we can specify a `cron` attribute to each location.
```yaml | .autorestic.yml
```yaml | .autorestic.yml
locations:
locations:
@ -14,11 +14,11 @@ Here is a awesome website with [some examples](https://crontab.guru/examples.htm
## Installing the cron
## Installing the cron
**This has to be done only once, regadless of now many cros you have in your config file.**
**This has to be done only once, regardless of now many cron jobs you have in your config file.**
To actually enable cron jobs you need something to call `autorestic cron` on a timed shedule.
To actually enable cron jobs you need something to call `autorestic cron` on a timed schedule.
Note that the shedule has nothing to do with the `cron` attribute in each location.
Note that the schedule 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.
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 schedule it once a day.
If you want to exclude certain files or folders it done easily by specifiyng the right flags in the location you desire to filter.
If you want to exclude certain files or folders it done easily by specifying the right flags in the location you desire to filter.
The flags are taken straight from the [restic cli exclude rules](https://restic.readthedocs.io/en/latest/040_backup.html#excluding-files) so you can use any flag used there.
The flags are taken straight from the [restic cli exclude rules](https://restic.readthedocs.io/en/latest/040_backup.html#excluding-files) so you can use any flag used there.