>>>>> On Thu, 6 May 2021 21:54:54 +0200, Peter Milesson said: > > On 2021-05-06 15:51, Josip Deanovic wrote: > > On Wednesday 2021-05-05 20:53:42 Peter Milesson wrote: > >> Hi folks, > >> > >> After upgrading to Bacula 9.2.2, the following backup error occurs when > >> the daily catalog backup is run: > > [...] > > > >> The normal backups seem to terminate without any errors. It's quite > >> clear that the bacula.sql file cannot be created or written, which > >> triggers the error message. The spool directory /spool/bacula is > >> otherwise used by Bacula during normal backups without any error > >> messages. The directory /spool/bacula is owned by bacula:bacula and with > >> permissions 0750. > >> > >> I assume that the MySQL database bacula is backed up in this job. If it > >> is so, I do not worry very much, as there is a cron job run separately, > >> that backs up the bacula database to an external server. > >> > >> I'm grateful for any input concerning this problem. > > Hello! > > > > Are you sure it is not defined in your FileSet named "Catalog"? > > > > > > Regards! > > > Hi Josip, > > It worked under Bacula 9.0.6. I'm using the same configuration files, > just with tweaks for different paths. The bacula.sql file is defined in > the FileSet named "Catalog" as /spool/bacula/bacula.sql. So it really > should work. I will try an even later version during the weekend.
What is the WorkingDirectory in your bacula-dir.conf? The make_catalog_backup.pl script writes to bacula.sql file to that directory. __Martin _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
