Re: [Bacula-users] Temporarily disable schedule for single client?

[John S. <st...@lu...>]

Angus> I've run into this a few times in the past couple of weeks, and
Angus> I'd like to know if there is a workaround to it at all.  There
Angus> are times when I would like to have a client backup be disabled
Angus> for a certain period of time (ie.  User is on vacation, and
Angus> computer is turned off for one reason or another).  Is there a
Angus> way to have a client temporarily disabled?  I know that all I
Angus> really need to do is comment out the schedule line in the
Angus> config file, and restart the daemons.  But, I would like this
Angus> to be able to happen without having to change the config file.

It would be great if you didn't have to stop/restart the daemons to
update configuration files as well.  Any word on when this will be
supported?  It shouldn't be too hard to implement I would think.  

Heck, I'd like to have all the configuration information put into the
SQL DB as well, with the required bare metal restore info dumped to a
file that's read-only in times of need.  Otherwise all the
configuration stuff is kept in a central place.  Then you could have a
command to generate the bacula-fd.conf file as you add clients.  Then
you'd just have to copy/push the file out to the client and presto,
off you go.

John