Then we check if everything is correct by running the `check` command. We will pass the `-a` (or `--all`) to tell autorestic to check all the locations.
Then we check if everything is correct by running the `check` command. We will pass the `-a` (or `--all`) to tell autorestic to check all the locations.
Lets see a more realistic example (from the config above)
If we would check only one location we could run the following: `autorestic check -l home`. Otherwise simpply check all locations with `autorestic check -a`
```
##### Note
autorestic check -l important
```
If we would check only one location we could run the following: `autorestic -l home check`.
Note that the data is automatically encrypted on the server. The key will be generated and added to your config file. Every backend will have a separate key. You should keep a copy of the keys somewhere in case your server dies. Otherwise DATA IS LOST!
### Backup
### Backup
@ -76,6 +74,7 @@ autorestic restore -a --to /path/where/to/restore
This will restore all the locations to the selected target. If for one location there are more than one backends specified autorestic will take the first one.
This will restore all the locations to the selected target. If for one location there are more than one backends specified autorestic will take the first one.
Lets see a more realistic example (from the config above)
```
```
autorestic restore -l home --from hdd --to /path/where/to/restore
autorestic restore -l home --from hdd --to /path/where/to/restore
```
```
@ -132,7 +131,7 @@ backends:
B2_ACCOUNT_KEY: backblaze_account_key
B2_ACCOUNT_KEY: backblaze_account_key
```
```
## Pruning and snapshot policies
### Pruning and snapshot policies
Autorestic supports declaring snapshot policies for location to avoid keeping old snapshot around if you don't need them.
Autorestic supports declaring snapshot policies for location to avoid keeping old snapshot around if you don't need them.
@ -143,24 +142,20 @@ locations:
etc:
etc:
from: /etc
from: /etc
to: local
to: local
keep:
options:
# options matches the --keep-* options used in the restic forget CLI
keep-within: "2w" # keep snapshots from the last 2 weeks
within: "2w" # keep snapshots from the last 2 weeks
```
```
Pruning can be triggered using `autorestic forget -a`, for all locations, or selectively with `autorestic forget -l <location>`. **please note that contrary to the restic CLI, `restic forget` will call `restic prune` internally.**
Pruning can be triggered using `autorestic forget -a`, for all locations, or selectively with `autorestic forget -l <location>`. **please note that contrary to the restic CLI, `restic forget` will call `restic prune` internally.**
Run with the `--dry-run` flag to only print information about the process without actually pruning the snapshots. This is especially useful for debugging or testing policies:
Run with the `--dry-run` flag to only print information about the process without actually pruning the snapshots. This is especially useful for debugging or testing policies:
Note that the data is automatically encrypted on the server. The key will be generated and added to your config file. Every backend will have a separate key. You should keep a copy of the keys somewhere in case your server dies. Otherwise DATA IS LOST!
If you want to exclude certain files or folders it done easily by specifiyng 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).
cupcakearmy
5 years ago