From fff85f029c7f1f7f5ce6768c91700dc2e1db81d8 Mon Sep 17 00:00:00 2001 From: Ian Wienand Date: Wed, 6 Oct 2021 10:34:13 +1100 Subject: [PATCH] borg-backup-server: wait for lock in verify We have seen a case where the weekly verification run conflicted with an in-progress backup run. Make the verification step wait for up to an hour for the lock to allow backups to complete. Change-Id: Id87dd090c7cd652695ab0c4aa73477cf0d72c28d --- playbooks/roles/borg-backup-server/files/verify-borg-backups.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/playbooks/roles/borg-backup-server/files/verify-borg-backups.sh b/playbooks/roles/borg-backup-server/files/verify-borg-backups.sh index 7ee1614bd1..579f5294eb 100644 --- a/playbooks/roles/borg-backup-server/files/verify-borg-backups.sh +++ b/playbooks/roles/borg-backup-server/files/verify-borg-backups.sh @@ -12,7 +12,7 @@ for u in borg-*; do sudo BORG_RELOCATED_REPO_ACCESS_IS_OK=y BORG_REPO=${BORG_REPO} -u ${u} -s <<'EOF' echo "$(date) Verifying ${BORG_REPO} ..." - /opt/borg/bin/borg check --verify-data + /opt/borg/bin/borg check --lock-wait=3600 --verify-data if [[ $? -ne 0 ]]; then echo "$(date) *** Verification failed" echo "Inconsistency found in backup ${BORG_REPO} on $(hostname) at $(date)" |