Bacula configuration for clients that are turned on and off randomly
- by Rastloser
I'm evaluating Bacula as a centralized backup tool for a small network where users will turn machines on and off unpredictably. Some of the headless Linux boxes I need to back up are intended to be turned off by pressing the on/off-button on the case, without any way of telling the user to wait for a backup job to finish.
So, we don't know when backup jobs may run (anacron might help with this, right?) and we don't know whether they'll be allowed to finish.
Is Bacula a reasonable choice for such an environment?