>
> Thanks for the input guys. I thought that was sort of an error state,
but
> knowing it's not means I can move on to the next problem. ;)
>
> I was actually going to ask next if I should install the 32 bit
storage and
> director services, and the 64 bit file service, so glad I don't even
need
>
> Hello,
>
> We have been using Bacula Version: 2.2.7 for our backup needs. Today
morning
> we have received a fatal error and the backup could not be completed.
Strange
> enough the backup termination status is saying OK. If you have any
kind of
> hint to resolution of this error then kindly
Hello,
We have been using Bacula Version: 2.2.7 for our backup needs. Today morning
we have received a fatal error and the backup could not be completed. Strange
enough the backup termination status is saying OK. If you have any kind of hint
to resolution of this error then kindly suggest th
Thanks for the input guys. I thought that was sort of an error state, but
knowing it's not means I can move on to the next problem. ;)
I was actually going to ask next if I should install the 32 bit storage and
director services, and the 64 bit file service, so glad I don't even need to
ask that n
>
> I'm new to bacula so please bear with me.
>
> I've installed the 32 bit bacula on x64 windows (because it's the
server).
> First thing I had to do was run make-tables.cmd in order to get the
director
> service to start. Then without modifying the conf files at all, I get
this
> status message
>
> I’ve installed the 32 bit bacula on x64 windows (because it’s the server).
> First thing I had to do was run make-tables.cmd in order to get the director
> service to start. Then without modifying the conf files at all,
>
Generally on most distributions and installations you must modify the
.co
I'm new to bacula so please bear with me.
I've installed the 32 bit bacula on x64 windows (because it's the server).
First thing I had to do was run make-tables.cmd in order to get the director
service to start. Then without modifying the conf files at all, I get this
status message for the sto
>
> What is going to happen when bacula used up the numbers for volumes?
Is it
> going to increase to a 5 digit format, or is it going to crash, or is
it just
> going to start from 0001? If it restarts from 0001, is it going to
still keep
> the same number as before for each client, or is it goin
Hi all,
I have a problem with running out of numbers for labeling volumes in bacula
3.0.0. Please help.
Here are the details: we have about 400 clients. We keep 4 full backups a
month (1 per week), and 6 incrementals (6 per week), so we keep a total of
28 volumes at any times for each cli
Hello,
07.06.2009 09:22, mehma sarja wrote:
> Does the compression happen at the fd side or at the sd side?
As John stated, on the FD side.
> * My fd side is Solaris and gzip version is: gzip 1.3.5 (2002-09-30)
Which version of gzip you have is not important as the compression
takes place ins
2009/6/7 mehma sarja :
> Does the compression happen at the fd side or at the sd side?
>
On the fd side.
John
--
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generati
Hi group,
I'm not sure if I have hit a bug, and if so, if it is worth reporting:
bacula version
bacula-dir Version: 2.4.4 (28 December 2008) i686-pc-linux-gnu suse 11.0
# uname -a
Linux localhost 2.6.27.21-0.1-default #1 SMP 2009-03-31 14:50:44 +0200
i686 i686 i386 GNU/Linux
In trying to work
Does the compression happen at the fd side or at the sd side?
* My fd side is Solaris and gzip version is: gzip 1.3.5 (2002-09-30)
* And another fd side is Solaris with the same version 1.3.5 - and it does
compression fine.
* My sd side is FreeBSD and gzip version is: FreeBSD gzip 20070711
Yudh
13 matches
Mail list logo
