To my mind, the correct behaviour would be for the director to terminate
the job after FDConnectTimeout has elapsed and then to inform the
storage daemon that the job has been cancelled / had an error. At the
moment, it looks like the director cancels the job but leaves the
stor
In case anyone finds them useful, I built a set of RPMs of Bacula 2.0
for Fedora Core. They are available at http://rodgers.org.uk/ . I
presume that "proper" RPMs will become available soon.
Chris.
-
Take Surveys. Earn Cas
To my mind, the correct behaviour would be for the director to terminate
the job after FDConnectTimeout has elapsed and then to inform the
storage daemon that the job has been cancelled / had an error. At the
moment, it looks like the director cancels the job but leaves the
stor
>> To my mind, the correct behaviour would be for the director to terminate
>> the job after FDConnectTimeout has elapsed and then to inform the
>> storage daemon that the job has been cancelled / had an error. At the
>> moment, it looks like the director cancels the job but leaves the
>> storage d
Alan Brown wrote:
>> This backup scheme works fine when the ngorongoro machine is powered on.
>> All the backup jobs run in order, and then the catalog backup runs last.
>> The problems only arise when ngorongoro (a Windows XP client) is powered
>> down at the time bacula runs.
>
>
> Ah
>
Alan Brown wrote:
>>> "waiting to reserve a device" means that all available tape drives are
>>> in use by jobs using other Pools.
>>
>>
>> What does it mean when the "tape device" is actually a hard disk
>> directory with different files in there, one for each "tape"?
>
>
> Effectively the same
Alan Brown wrote:
>> You might configure concurrent jobs as a solution.
>
>
> It won't help in this situation and the message tends to indicate
> concurrent jobs are setup.
I don't think they are. My config file
(http://laplace.chem.ox.ac.uk/b/bacula-dir.conf) contains this block:
Director {
Chris Rodgers wrote:
> Chris Rodgers wrote:
>
>>Does anyone have any ideas what is causing bacula to jam up like this?
>>
>>I'm sorry if I have provided too much information, but I don't have any
>>real idea which parts of the configuration/etc. may
Chris Rodgers wrote:
> Does anyone have any ideas what is causing bacula to jam up like this?
>
> I'm sorry if I have provided too much information, but I don't have any
> real idea which parts of the configuration/etc. may be to blame.
That's what used to hap
Does anyone have any ideas what is causing bacula to jam up like this?
I'm sorry if I have provided too much information, but I don't have any
real idea which parts of the configuration/etc. may be to blame.
Thanks,
Chris.
---
Dear all,
I have bacula (bacula-mysql-1.38.2-1.rpm) installed on a Redhat FC4
system (Linux lilac.home 2.6.17-1.2142_FC4 #1 Tue Jul 11 22:41:14 EDT
2006 i686 athlon i386 GNU/Linux).
Bacula is set to back up various systems, including another PC on my
home network. Backups are saved to hard disk s
essful job at setting up something like this?
Yes, I have a setup like this working. I include the details below in
case this is useful to someone else.
Yours,
Chris Rodgers.
Server: Fedora Core 4
Client: Windows XP Home
Hi,
I use bacula to backup some machines on my home network. The machine
running bacula is set to boot up automatically each evening. It is then
responsible for waking the (Windows) clients using Wake-on-LAN, running
a backup and then shutting the other machine down.
However, sometimes the P
13 matches
Mail list logo
