We are using Puppet to configure Bareos for things like adding clients. Puppet manages the Bareos config files and re-starts Bareos when changes happen.
The trouble is that we have Puppet running in the background and if someone adds a client during a backup run Puppet re-starts Bareos in the middle of a bunch of backups. Which is bad. Has anybody figured out a method to notify Bareos about the need for a restart when the director comes idle? I know that some configuration APIs just released with version 16 of Bareos, but I don't quite have the time to adapt the Puppet manifests to that yet. -- 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 post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
