In theory all the restic backends are supported.
Those tested are the following:
ℹ️ You can also specify the
envvariables in a config file to separate them from the config file.
1backends:2 name-of-backend:3 type: local4 path: /data/my/backups
1backends:2 name-of-backend:3 type: b24 path: 'bucket_name'5 # Or With a path6 # path: 'bucket_name:/some/path'7 env:8 B2_ACCOUNT_ID: 'backblaze_keyID'9 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.
1backends:2 name-of-backend:3 type: s34 path: s3.amazonaws.com/bucket_name5 # Minio6 # path: http://localhost:9000/bucket_name7 env:8 AWS_ACCESS_KEY_ID: my_key9 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.
1backends:2 name-of-backend:3 type: sftp4 path: my-host:/remote/path/on/the/server
1backends:2 name-of-backend:3 type: rest4 path: http://localhost:8000/repo_name5 # Or authenticated6 path: https://user:pass@host:6969/path
Optionally you can set user and password separately
1backends:2 rest:3 type: rest4 path: http://localhost:6969/path5 key: ...6 rest:7 user: user8 password: pass