Available Backends

In theory all the restic backends (opens in a new tab) are supported.

Those tested are the following:

ℹ️ You can also specify the env variables in a config file to separate them from the config file.

Local

backends:
  name-of-backend:
    type: local
    path: /data/my/backups

Backblaze

backends:
  name-of-backend:
    type: b2
    path: 'bucket_name'
    # Or With a path
    # path: 'bucket_name:/some/path'
    env:
      B2_ACCOUNT_ID: 'backblaze_keyID'
      B2_ACCOUNT_KEY: 'backblaze_applicationKey'

API Keys gotcha

If you use a File name prefix when making the application key, do not include a leading slash. Make sure to include this prefix in the path (e.g. path: 'bucket_name:my/path').

S3 / Minio

backends:
  name-of-backend:
    type: s3
    path: s3.amazonaws.com/bucket_name
    # Minio
    # path: http://localhost:9000/bucket_name
    env:
      AWS_ACCESS_KEY_ID: my_key
      AWS_SECRET_ACCESS_KEY: my_secret

SFTP

For SFTP to work you need to use configure your host inside of ~/.ssh/config as password prompt is not supported. For more information on this topic please see the official docs (opens in a new tab) on the matter.

backends:
  name-of-backend:
    type: sftp
    path: my-host:/remote/path/on/the/server

Rest Server

See here (opens in a new tab) for how to install a rest server backend and here (opens in a new tab) for further documentation.

backends:
  name-of-backend:
    type: rest
    path: http://localhost:8000/repo_name
    # Or authenticated
    path: https://user:pass@host:6969/path

Optionally you can set user and password separately

backends:
  rest:
    type: rest
    path: http://localhost:6969/path
    key: ...
    rest:
      user: user
      password: pass

Overview Options