In theory all the restic backends 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.
1linkbackends:
2link name-of-backend:
3link type: local
4link path: /data/my/backups
1linkbackends:
2link name-of-backend:
3link type: b2
4link path: 'bucket_name'
5link # Or With a path
6link # path: 'bucket_name:/some/path'
7link env:
8link B2_ACCOUNT_ID: 'backblaze_keyID'
9link B2_ACCOUNT_KEY: 'backblaze_applicationKey'
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'
).
1linkbackends:
2link name-of-backend:
3link type: s3
4link path: s3.amazonaws.com/bucket_name
5link # Minio
6link # path: http://localhost:9000/bucket_name
7link env:
8link AWS_ACCESS_KEY_ID: my_key
9link AWS_SECRET_ACCESS_KEY: my_secret
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 on the matter.
1linkbackends:
2link name-of-backend:
3link type: sftp
4link path: my-host:/remote/path/on/the/server
See here for how to install a rest server backend and here for further documentation.
1linkbackends:
2link name-of-backend:
3link type: rest
4link path: http://localhost:8000/repo_name
5link # Or authenticated
6link path: https://user:pass@host:6969/path
Optionally you can set user and password separately
1linkbackends:
2link rest:
3link type: rest
4link path: http://localhost:6969/path
5link key: ...
6link rest:
7link user: user
8link password: pass
Home Quick Start Installation Configuration Upgrade