link🎛 Config File

linkPath

By default autorestic searches for a .autorestic.yml file in the current directory and your home folder.

• ./.autorestic.yml
• ~/.autorestic.yml

You can also specify a custom file with the -c path/to/some/config.yml

⚠️ WARNING ⚠️

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 or config file somewhere in case your server dies. Otherwise DATA IS LOST!

linkExample configuration

.autorestic.yml
1linklocations:

2link  home:

3link    from: /home/me

4link    to: remote

5link

6link  important:

7link    from: /path/to/important/stuff

8link    to:

9link      - remote

10link      - hdd

11link

12linkbackends:

13link  remote:

14link    type: b2

15link    path: 'myBucket:backup/home'

16link    env:

17link      B2_ACCOUNT_ID: account_id

18link      B2_ACCOUNT_KEY: account_key

19link

20link  hdd:

21link    type: local

22link    path: /mnt/my_external_storage

linkAliases

A handy tool for more advanced configurations is to use yaml aliases. These must be specified under the global extras key in the .autorestic.yml config file. Aliases allow to reuse snippets of config throughout the same file.

The following example shows how the locations a and b share the same hooks and forget policies.

.autorestic.yml
1linkextras:

2link  hooks: &foo

3link    before:

4link      - echo "Hello"

5link    after:

6link      - echo "kthxbye"

7link  policies: &bar

8link    keep-daily: 14

9link    keep-weekly: 52

10link

11linkbackends:

12link  # ...

13linklocations:

14link  a:

15link    from: /data/a

16link    to: some

17link    hooks:

18link      <<: *foo

19link    options:

20link      forget:

21link        <<: *bar

22link  b:

23link    from: data/b

24link    to: some

25link    hooks:

26link      <<: *foo

27link    options:

28link      forget:

29link        <<: *bar