Hi Bruno, thanks for your remarks.
I have an additional daily cronjob that does a pg_dumpall to another server; having a bareos-fd-postgresql backup of the bareos database is more a "it's there why not use it?" approach for playing around with the features bareos offers. The configuration and stuff comes from an ansible playbook.
The archive_cleanup_command is never executed on the master, that's right. It's configured just because I wanted to have it already set in case I setup a replication in the future. I'll remove the line and see what happens.
The error comes up quite seldom. There are something like four to ten days in a row where everything works fine. Increasing the debug level is a good idea.
Kind regards, Philippe -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/ca3c290a-b97c-4b9e-87f5-06e5402f7d16%40quarantine.de.
