Hi, I am trying to use Base jobs as an extra level above Full backups, so that I run Base every three months and Full every month.
In my setup, I have essentially created a copy of the normal job with "-base" added to its name, and this seems to work fine. I have two problems. The first is that md5sum are missing from some files. This is mostly an annoyance, but it means about 10% of the data is included in the Full backup, even if the data is unchanged. Actually I should make a separate post about this. The more serious issue is that the temporary Basefiles_JOBID table is gone by the time the job completes. This causes the job to have a "fatal error", and it blocks the storage daemon until I cancel the job manually in bconsole (in itself a bug/misfeature - the SD should be able to signal cancellation of a job to DIR). I wonder how I can debug this - it is a mystery to me how the temporary table can vanish like that. One recent change I have made is to enable Reconnect for the Catalog, but I hope that doesn't mean Bareos starts doing reconnects on its own accord (unless necessary). As far as I can tell, it has not reconnected. Better logging and support for logstash was mentioned in a previous release notes - is it possible to feed the logs in a structured manner into Elasticsearch or similar? I am running Bareos from "master" branch, PostgreSQL 9.3.14, kernel 4.7 (compiled from Linus' tree). -- Kjetil T. Homme Redpill Linpro AS - Changing the game -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
