Use s3 backend for restic backups
It's apparently more stable
This commit is contained in:
parent
6a7e8ffd0e
commit
df5b8f4c90
2 changed files with 4 additions and 3 deletions
|
@ -2,10 +2,10 @@
|
||||||
|
|
||||||
set -e
|
set -e
|
||||||
|
|
||||||
export B2_ACCOUNT_ID="{{ restic_b2_account_id }}"
|
export AWS_ACCESS_KEY_ID="{{ restic_b2_account_id }}"
|
||||||
export B2_ACCOUNT_KEY="{{ restic_b2_account_key }}"
|
export AWS_SECRET_ACCESS_KEY="{{ restic_b2_account_key }}"
|
||||||
export RESTIC_PASSWORD="{{ restic_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
|
export GOGC=20 # HACK: Work around for restic's high memory usage https://github.com/restic/restic/issues/1988
|
||||||
|
|
||||||
set -x
|
set -x
|
||||||
|
|
|
@ -24,6 +24,7 @@ restic_key: !vault |
|
||||||
61303164333662353732656265386430383566343462633435626334373331316663363563616662
|
61303164333662353732656265386430383566343462633435626334373331316663363563616662
|
||||||
66643135336539333738623231346331623464636637373639666435663961383936
|
66643135336539333738623231346331623464636637373639666435663961383936
|
||||||
restic_b2_bucket: 0rng-restic
|
restic_b2_bucket: 0rng-restic
|
||||||
|
restic_b2_endpoint: s3.eu-central-003.backblazeb2.com
|
||||||
healthchecks_host: https://hc-ping.com
|
healthchecks_host: https://hc-ping.com
|
||||||
|
|
||||||
restic_homeassistant_mounts:
|
restic_homeassistant_mounts:
|
||||||
|
|
Loading…
Reference in a new issue