If this ever happens to anyone else, see if either/both of these happened during one of the volume writes:
1. The disk which bacula uses for its logs became full 2. Someone did an apt-get update/dnf update or whatever during the backup. 1. Definitley just hit us so we had to start the whole job again, and it is suspected 2. did too, and possible earlier, so it is possible some library or component bacula was depending on got changed mid-backup? +---------------------------------------------------------------------- |This was sent by bill.dam...@yahoo.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +---------------------------------------------------------------------- ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
