Star

Created With

link🗂 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!

.autorestic.yml
1linkversion: 2

2link

3linklocations:

4link my-location-name:

5link from: path/to/backup

6link # Or multiple

7link # from:

8link # - /a

9link # - /b

10link to:

11link - name-of-backend

12link - also-backup-to-this-backend

linkfrom

This is the source of the location. Can be an array for multiple sources.

linkHow 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.

linkto

This is either a single backend or an array of backends. The backends have to be configured in the same config file.

🗂 LocationsfromHow are paths resolved?to

Home Quick Start Installation Configuration Upgrade

Locationschevron_right

Overview Hooks

Optionschevron_right

Cron Docker Volumes

Backendchevron_right
CLIchevron_right
Migrationchevron_right

Examples Docker QA Community Contributors