On Mon, 9 Nov 2026 at 09:24, Stefan G. Weichinger via Bacula-users <[email protected]> wrote: > > Am 09.11.26 um 09:12 schrieb Stefan G. Weichinger via Bacula-users: > > So, yes, my jobs look encrypted. Now for restore tests ... > > Sorry for my ongoing report: > > I tested a restore via bacularis now. > > It seems to work but I get loads of these lines in the report: > > bacula-sd JobId 485: Ready to read from volume "Vol-0071" on File device > "FileStorage_QNAP_NAS" (/mnt/nas_bacula_storage/). > bacula-sd JobId 485: Forward spacing Volume "Vol-0071" to addr=37997567510 > > pre01svbmd02-fd JobId 485: Error: filed/restore.c:1859 Missing > cryptographic signature for C:/tmp/bacula-restores/... > pre01svbmd02-fd JobId 485: Error: filed/restore.c:1859 Missing > cryptographic signature for C:/tmp/bacula-restores/... > > A quick look into the restored files looks OK: I can open pdfs, for example. > > I understand that the storage daemon (is that the one reporting here?) > does not have the keys to decrypt the data. But it looks quite scary > this way, with thousands of errors in the restore job. Shouldn't that be > hidden from me ... ? Do I miss something?
Hello Stefan, Those error messages come from Bacula File Daemon 'pre01svbmd02-fd'. It looks like restored job files do not have the signatures. If you use encryption for these backups, this can mean that the restored backup was not encrypted. I would propose to look at the first lines of the restore job log. There is information what jobids were taken into account in this restore: localhost-dir JobId 1234: Restoring files from JobId(s) XXX,YYY,ZZZ and check in the job logs of all the jobids: XXX,YYY,ZZZ if the Encryption flag was 'yes'. Best regards, Marcin Haba _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
