On 2010May12 2:42 AM, frank cheong wrote:
Dear All,
I have just finished setting up bacula 5.0.2 and have no problem in
backing up local host, while it complained the following error when I
add a second client :-
Fatal error: Failed to connect to Storage daemon: server:9103 12-May
12:41
On 2010May10 10:48 AM, McCann, Brian wrote:
Hi all. I've got a configuration issue that's been driving me nuts
for weeks now. I backup several Windows machines using Bacula, to a
large disk array. Each workstation gets its own pool. My problem is
that I have the pool theoretically set to
On 2010Feb10 8:50 AM, Steve Polyack wrote:
On 2/10/2010 8:16 AM, Petar Bogdanovic wrote:
I want use bzip2 to compress my file, because I thing bzip2 is more
efficient...
Really?
[...]
255526 bytes less while six times slower..
This is extremely dependent on the contents of
On 2010Feb10 10:31 AM, John Doe wrote:
From: Sean M Clark smcl...@tamu.edu
xz/lzma is another consideration. At moderate compression levels, lzma
seems to be about the same or slightly faster than bzip2 with a little
better compression. At lower compression levels it seems like it's
about
On 2010Jan20 9:19 AM, Carlo Filippetto wrote:
I don't know the answare, but if it runs samba means the the SO is
linux, so I think you can connect to it with ssh, and there I think
you can put and run one static-bacula-fd and the confing file..
If this works well in same folder you will find
On 2010Jan20 4:07 PM, mehma sarja wrote:
What NAS did you get sd working on?
Mehma
===
It was a LaCie 2big network. It took a bit of effort to figure out
how to get access to get bacula-sd installed, but it's actually been
running quite well ever since.
And, yes, I actually DID put in a
On 2010Jan14 7:25 AM, Gavin McCullagh wrote:
[...]
One way to make it more concise would be to drop the repetition of
the directory name, something like.
fd-name JobId X:
c:/WINDOWS/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f7f11d50a3a
links elsewhere. Not Following.
If
Carlo Filippetto wrote:
Hi,
I would like to know if is true that I have so slow troughput as this:
[...]
FULL
-
Elapsed time: 1 day 22 hours 13 mins 37 secs
[...]
Rate: 371.7 KB/s
Software Compression: 15.5 %
[...]
All my jobs have the maximum
Gary R. Schmidt wrote:
On Fri, October 30, 2009 01:43, Sean M Clark wrote:
[...] The
problem is, I could never manage to get ClientRunBeforeJob to
correctly pass the full pathname with spaces in it
[...]
able to get
Client Run Before Job = \D:\\Documents and Settings\\me\\My
Documents
ebollengier wrote:
Sean M Clark wrote:
[...]
The problem is, I could never manage to get "ClientRunBeforeJob" to
correctly pass the full pathname with spaces in it, despite trying every
combination of single-quotes, double-quotes, escaped spaces (i.e.
"C:\
Pascal Clermont wrote:
I have added a new machine to be backed up with bacula and I cannot
get a full backup, always have these weird errors. the current setup
is all centos 5.3 86_64 and every other host besides this one have
been working flawlessly for over 6 months.
DIR Version: Version:
George Shaw wrote:
As far as I can determine, the Win64 bacula-fd service does not actually
read the provided conf file. It complains about being unable to read a
“monitor_n...@” file on line 35. This is indeed how the default conf
file comes after setup (as listed in bacula-fd.conf.in in the
We've got several machines where Symantec Antivirus appears to butt in
and bog down file tranfers severely as it apparently scans every single
file before it's transferred (or at least this is what I believe is
happening).
Previously, we found that we could temporarily halt Symantec at the
start
I just tried to update bacula-fd on one of our client macs which had
been working only minutes before. Now network connections to bacula-fd
are failing except from localhost. I tried re-installing the older 2.x
version that was previous on it, and now IT has the same symptoms.
There's a regular
I've just attempted to add a couple of Mac OSX (Tiger - yes, still...)
clients to our bacula system using the current 3.0.1 bacula-fd.
Backups on these clients have a couple of problems. First, there's the
fact that they both choke to death a few GB into the initial Full backup
with a series of
I've tried 2.4.3 and 2.4.4 by hand, and 2.4.4 via macports, and they all
do the same thing. This is on Mac OSX 10.5.6 Leopard (uname -r = 9.6.0).
I've tried both the full build and --enable-client-only.
The seem to build okay, up until they hit filed. The individual modules
get compiled, and
16 matches
Mail list logo
