diff --git a/CHANGELOG.md b/CHANGELOG.md index 12bbd5f..abf67ec 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,11 @@ +## 4.9.3 2026-08-30 + + ### Changed + - Report a failed move to the backup location as a failed backup to Zabbix, so that the + `[{#NAME}] Backup - Failed with errors` trigger fires when a dump never reached its + destination + + ## 4.9.2 2026-08-24 ### Changed diff --git a/rootfs/container/functions/10-dbbackup b/rootfs/container/functions/10-dbbackup index 91ecaa6..99fa070 100644 --- a/rootfs/container/functions/10-dbbackup +++ b/rootfs/container/functions/10-dbbackup @@ -1630,10 +1630,15 @@ dbbackup_post_dbbackup() { silent dbbackup_run_as_user zabbix_sender -c "${ZABBIX_CONFIG_PATH}"/"${ZABBIX_CONFIG_FILE}" -k dbbackup.backup -o '[{"{#NAME}":"'${backup_job_db_host}.${backup_job_db_name}'"}]' local zabbix_payload=$(dbbackup_run_as_user mktemp) + ## The backup only counts as successful when it also reached its destination - + ## exit_code covers the dump alone, move_exit_code the move to the backup location. + local zabbix_status="${exit_code}" + if [ "${move_exit_code:-0}" != "0" ] ; then zabbix_status=1 ; fi + cat <