On 2007.07.02. 21:52, [EMAIL PROTECTED] wrote:
>
>
> Ah...
>
> Some clarification: by clients, I meant the client application, the bacula-fd
> agent rather then the machines themselves, though in general if you can use
> RunBeforeJob with a completely shut down system and have no problems, do
well.
Thanks,
Andrew
-Original Message-
From: Kyle Marsh <[EMAIL PROTECTED]>
Sent: Mon, July 2, 2007 12:19 pm
To: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] start/stop client on demand
When I was having problems with downed clients causing y backups to
wait for
When I was having problems with downed clients causing y backups to
wait for a long time, someone suggested using RunBeforeJob to ping the
client and if it failed, to reschedule for an hour later. The
suggestion was also made to netboot the computers, back them up, and
if they were not on to begin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Do not schedule a job, just run it when you feel like running it. This
makes the most sense. To do this, you would create a job, but include no
schedule.
[EMAIL PROTECTED] wrote:
>
> Hi all,
>
> I'm a new user to bacula and I'm trying to start
Hi all,
I'm a new user to bacula and I'm trying to start using
this at work to replace the current mix of scripts that do backups (to
disk). One of the requested requirements is to leave the clients off for
as long as possible, preferably turning them on only when a job is ready to run
