/dev/st0 in
use. Any thoughts on that?
I'm running 1.36.2 on Debian sarge (I'm aware it's old but it's also
what's available in sarge!).
Regards,
Juliet
--
+
+ Ms Juliet Kemp
Bacula to time out fail the blocked job in these circumstances? The
FD/SD Connect Timeout config options don't do the job, as connection
with FD or SD isn't the problem.
Regards,
Juliet
--
+
+ Ms Juliet Kemp
it?
On a slight tangent: this error happened on Friday meant that none of
the other backups happened. Is there an option I can set such that an
error like this will lead to a time-out after a certain period of time?
Cheers,
Juliet
--
Juliet Kemp
Computer Manager
does change
slightly in 1.38, though).
Cheers,
Juliet
--
Juliet Kemp
Computer Manager[EMAIL
PROTECTED]
Astrophysics Group, Imperial College +44 (0)20 7594 7543
---
This SF.net email
[EMAIL PROTECTED] wrote:
Every time I do a run and select client1 I get the following error
messages:
01-Feb 12:58 ninja3-dir: *Console*.2006-02-01_12.51.37 Warning:
bnet.c:853 Could not connect to Storage daemon on ninja3:9103.
ERR=Connection refused
All the passwords match is there
Florian Schnabel wrote:
Juliet Kemp wrote:
How long is it normal for pruning/purging a volume to take? I have
found that it takes several hours, even if only purging 2 or 3 jobs (
incremental jobs, rather than full ones) - this obviously can delay
backups quite significantly.
pruning
with the tape? Or
just the database?
I'm running 1.36.3, on Linux, using MySQL as the backend. It's quite
an old machine, as well. My backup is to LTO-3 tapes in an autochanger
(backing up etc works fine).
Thanks for any help/comments!
Juliet Kemp
successfully built bacula-fd for that installed it on
everything. It's just Solaris that's problematic, not helped by the
fact that my Linux sysadmin experience is rather more than my Solaris
sysadmin experience.)
Many thanks for any help,
Juliet
--
Juliet Kemp
Computer Manager
