autorestic/docs/pages/location/index.md

34 lines
939 B
Markdown
Raw Normal View History

2020-05-17 14:52:30 +02:00
# 🗂 Locations
Locations can be seen as the input to the backup process. Generally this is simply a folder.
The paths can be relative from the config file. A location can have multiple backends, so that the data is secured across multiple servers.
Note: names of locations MUST be lower case!
2020-05-17 14:52:30 +02:00
```yaml | .autorestic.yml
2021-11-21 21:06:25 +01:00
version: 2
2020-05-17 14:52:30 +02:00
locations:
my-location-name:
from: path/to/backup
2021-11-21 21:06:25 +01:00
# Or multiple
# from:
# - /a
# - /b
2020-05-17 14:52:30 +02:00
to:
- name-of-backend
- also-backup-to-this-backend
```
## `from`
2021-11-21 21:06:25 +01:00
This is the source of the location. Can be an `array` for multiple sources.
2020-05-17 14:52:30 +02:00
#### How are paths resolved?
Paths can be absolute or relative. If relative they are resolved relative to the location of the config file. Tilde `~` paths are also supported for home folder resolution.
## `to`
2021-04-21 09:34:01 +02:00
This is either a single backend or an array of backends. The backends have to be configured in the same config file.