Greetings,
Running Bacula 3.0.3,
Is there a KeepAlive parameter for the Control Connection between
FileDaemon and Director during a Backup/Restore operation?
Thing is, We are saving a server across an appliance. The Bacula
Director is not the Storage Daemon.
So, The Director opens a
ot;
So the Capital Letter (or not) was the problem.
That's where the problem was since it appears to work just fine now.
I am using Bacula 3.0.3 and winbacula 3.0.3a
Hope this will help others with similar configuration issues.
M. Sébastien LELIEVRE a écrit :
John Drescher a écrit :
John Drescher a écrit :
Did you restart the sd after adding tse01-dv?
Yes, I did
Does your linux machines use tse01-dv?
No, each machine has its on $HOSTNAME-dv, but those devices are on the
same Storage Daemon
Thank you for you support !
--
Cordialement
Sébastien
M. Sébastien LELIEVRE a écrit :
Greetings everyone,
I keep receiving the error I paste below. This error only occurs on
Windows client saves ; Linux clients are saved just fine !
I do not understand line 4 below since it points to a tse01 volume
(tse01 is another Windows server
Greetings everyone,
I keep receiving the error I paste below. This error only occurs on
Windows client saves ; Linux clients are saved just fine !
I do not understand line 4 below since it points to a tse01 volume
(tse01 is another Windows server) ; configuration seems ok tough.
What am I
Reynier Pérez Mira a écrit :
Julien Cigar wrote:
http://wiki.bacula.org/doku.php?id=application_specific_backups:oracle_rdbms
This describe the process when both applications Oracle DB and Bacula
are in the same system (server as far as I understood) but I have this
separated: Bacula is
Greetings,
We are now running Bacula-3.0.2 compiled from sources on an Ubuntu 8.04
LTS server distribution.
Our aim is to restore very specific files of a backup on another client
every week.
In order to do this, we use a shell script that specifies every options,
files and directories we need
