older Bacula clients are not getting warnings from newer Bacula servers
Summary
| Reproducibility | Platform | OS | OS Version | Product Version |
|---|---|---|---|---|
| always | AMD64 | FreeBSD | 13.x | 9.x, 11.x, 13.x |
Description
See https://www.mail-archive.com/bacula-users@lists.sourceforge.net/msg73184.html for more detail
If a 9.6.7 client runs with a 13.0.3 server, job warnings are silently dropped and never presented to the user. All get is ' Termination: Backup OK -- with warnings'
If the client is updated to 13.0.3, the warnings appear in the job history.
i.e. Could not stat "/var/db/ingress/latest_commits/.zfs/snapshot/snapshot-for-backup": ERR=No such file or directory
Steps to Reproduce
- create a job on a 13.x server which will create warnings (specify a directory which does not exist)
- run the backup with a 9.x client
- run the backup with a 13.x client
This problem may have been caused by this commit: https://gitlab.bacula.org/bacula-community-edition/bacula-community/-/commit/fd926fc4671b054234fd3d5957bc05d303d87763
The result: possible data loss because the user is not shown the issue
Consequences: the long standing convention for version-compatibilty is broken. No longer does bacula-dir=bacula-sd>=bacula-fd hold. That implication is a big deal to users. This was one of main strengths of Bacula - it just worked.