Use s3 backend for restic backups

It's apparently more stable
This commit is contained in:
Jake Howard 2024-12-01 19:17:54 +00:00
parent 6a7e8ffd0e
commit df5b8f4c90
Signed by: jake
GPG key ID: 57AFB45680EDD477
2 changed files with 4 additions and 3 deletions

View file

@ -2,10 +2,10 @@
set -e
export B2_ACCOUNT_ID="{{ restic_b2_account_id }}"
export B2_ACCOUNT_KEY="{{ restic_b2_account_key }}"
export AWS_ACCESS_KEY_ID="{{ restic_b2_account_id }}"
export AWS_SECRET_ACCESS_KEY="{{ restic_b2_account_key }}"
export RESTIC_PASSWORD="{{ restic_key }}"
export RESTIC_REPOSITORY="b2:{{ restic_b2_bucket }}"
export RESTIC_REPOSITORY="s3:{{ restic_b2_endpoint }}/{{ restic_b2_bucket }}"
export GOGC=20 # HACK: Work around for restic's high memory usage https://github.com/restic/restic/issues/1988
set -x

View file

@ -24,6 +24,7 @@ restic_key: !vault |
61303164333662353732656265386430383566343462633435626334373331316663363563616662
66643135336539333738623231346331623464636637373639666435663961383936
restic_b2_bucket: 0rng-restic
restic_b2_endpoint: s3.eu-central-003.backblazeb2.com
healthchecks_host: https://hc-ping.com
restic_homeassistant_mounts: