Univention Bugzilla – Bug 56434
No /var/univention-backup made for Samba with mdb backend
Last modified: 2024-05-17 13:03:46 CEST
/etc/cron.d/univention-samba4-backup uses /usr/sbin/univention-samba4-backup and that doesn't work with a Samba sam.ldb that uses mdb/lmdb as backend databases. As a result customers with large sam.ldb backend databases will have no nightly snapshots in /var/univention-backup/samba which are sometimes useful in support situations. Systems like these can be identified e.g. like this: === root@ucs:~# ldbsearch -H sam.ldb -b '@PARTITION' -s base backendStore # record 1 dn: @PARTITION backendStore: mdb ===
Successful build Package: univention-samba4 Version: 9.0.14-1 Branch: ucs_5.0-0 Scope: errata5.0-5
The new version of /usr/sbin/univention-samba4-backup now generates a lot of output, that's not good for use in a cron job.
fixed, redirect stdout to null in cron job Successful build Package: univention-samba4 Version: 9.0.14-2 Branch: ucs_5.0-0 Scope: errata5.0-5
and for the test * removed 51_samba4/65samba4_backup.py * don't delete files in 51_samba4/68univention-samba-backup, just test if there is a new backup archive after runnung univention-samba4-backup Successful build Package: ucs-test Version: 10.0.19-7 Branch: ucs_5.0-0 Scope: errata5.0-5
Verified: * Functionality * Package update * Advisory
<https://errata.software-univention.de/#/?erratum=5.0x811>
*** Bug 55535 has been marked as a duplicate of this bug. ***