Hello,
After having been totally frustrated chasing this kernel crash for the last
few weeks (I really could not believe that it was not a Bacula bug), I have
finally found a work around and at the same time, proven that it is a SuSE
problem.
Last night, I loaded the Fedora FC4 kernel from
Dear listusers,
we are currently backing up 5 servers as a pilot before final
bacula-installation with storage unit and bg server ;-)
We configured expiration and pruning to suit our needs and everything's fine.
What we are experiencing is, that we need to insert another harddrive to
Hi guys, thanks your help, I've been added
SD_USER=bacula
SD_GROUP=tape
in bacula-ctl-sd
and everything it's fine
Jea
- Original Message -
From: Martin Simmons [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; bacula-users@lists.sourceforge.net
Sent: Thursday, September
Hi,
On 9/29/2006 11:19 AM, Benjamin Zeller wrote:
Dear listusers,
we are currently backing up 5 servers as a pilot before final
bacula-installation with storage unit and bg server ;-)
We configured expiration and pruning to suit our needs and everything's fine.
What we are
Hi gentlemen, I tried before to do things that could not be the best way to
backup my logical volume.
The problem:
I have many logical volumes from machines that could not be sttoped, then I
had two idea
The alternatives:
1- to do a backup for whole RAW partition making a snapshot
(lvcreate
On Fri, 29 Sep 2006, Kern Sibbald wrote:
After having been totally frustrated chasing this kernel crash for the last
few weeks (I really could not believe that it was not a Bacula bug), I have
finally found a work around and at the same time, proven that it is a SuSE
problem.
One of the
I use your point 2, and it works very well.
A Client Run Before Job stops the application, makes the snapshot,
restarts the application and mounts it on a different mount point.
A Client Run After Job unmounts the snapshot and removes it.
Obviously the File section specifies the snapshot mount
On Friday 29 September 2006 12:31, Alan Brown wrote:
On Fri, 29 Sep 2006, Kern Sibbald wrote:
After having been totally frustrated chasing this kernel crash for the
last
few weeks (I really could not believe that it was not a Bacula bug), I
have
finally found a work around and at the
On Fri, 29 Sep 2006, Kern Sibbald wrote:
One of the reason we dumped SLES on our production machines in favour of
RHEL was that SUSE was consistently shipping with mismatching dynamic and
static library versions - and would not fix it even when notified.
SuSE may be great for home systems
On Friday 29 September 2006 13:43, Alan Brown wrote:
On Fri, 29 Sep 2006, Kern Sibbald wrote:
One of the reason we dumped SLES on our production machines in favour of
RHEL was that SUSE was consistently shipping with mismatching dynamic and
static library versions - and would not fix it
Hi, I'm trying as you told me. The bacula it's backing up whole logical
volume
with the config:
Client {
Name = wrack-fd
Address = wrack.mydomain.com
Catalog = Catalogo
Password = seknmit5fwllkjh3g78klwuethñkw4nk645tig
}
Job {
Name = wrack
Client = wrack-fd
FileSet = RawPartition
I'll chime in with my endorsement of CentOS as well. I use it
specifically for compatibility testing
as a stand-in for RHEL as well as for commercial apps that only
officially support RedHat and have
never had a problem. The CentOS network also provides very timely
security updates at no
On Fri, 29 Sep 2006, Kern Sibbald wrote:
Centos is _very_ stable. RHEL can be licensed quite cheaply if you don't
buy the support package (about US$10/machine)
The last time I looked (some time ago), it was over $200/machine. That is too
much for me. For a company or someone serious about
On Friday 29 September 2006 14:39, Alan Brown wrote:
On Fri, 29 Sep 2006, Kern Sibbald wrote:
Centos is _very_ stable. RHEL can be licensed quite cheaply if you don't
buy the support package (about US$10/machine)
The last time I looked (some time ago), it was over $200/machine. That is
Hello,
Someone on this list appears to be bouncing email back causing it to get
delivered several times to the bacula-devel list. This seems to happen only
for email sent to both bacula-users and bacula-devel at the same time.
If you have recently subscribed or changed your email setup please
On Friday 29 September 2006 12:02, Arno Lehmann wrote:
Hi,
Hi Arno,
On 9/29/2006 11:19 AM, Benjamin Zeller wrote:
Dear listusers,
we are currently backing up 5 servers as a pilot before final
bacula-installation with storage unit and bg server ;-)
We configured expiration and
I'm catching up with this thread with interest after just coming into work
this morning. Kern, my sympathy. I can imagine how frustrated you are, but it
just goes to show how good a programmer you are, that it wasn't Bacula after
all!
After reading the merits weaknesses of RHEL, SUSE,
Hello.
Last night , one of my backup jobs started, but for some reason a
problem occour. Here is part of the status dir command:
Running Jobs:
JobId Level Name Status
==
1304 Full
On Friday 29 September 2006 16:53, Mike Reinehr wrote:
I'm catching up with this thread with interest after just coming into work
this morning. Kern, my sympathy. I can imagine how frustrated you are, but
it
just goes to show how good a programmer you are, that it wasn't Bacula after
all!
hi list,
1st there's a recurrent bug in the manual, you can't
use latex commands (\bf) inside a verbatim section.
i think there's an alternative section type where you
can do that.
that gives lines like these:
===
(in the Console program)
*{\bf restore}
First you select one or more JobIds
Kern,
On Friday 29 September 2006 10:28, Kern Sibbald wrote:
On Friday 29 September 2006 16:53, Mike Reinehr wrote:
I'm catching up with this thread with interest after just coming into
work this morning. Kern, my sympathy. I can imagine how frustrated you
are, but
it
just goes to
On Friday 29 September 2006 18:43, m listus wrote:
hi list,
1st there's a recurrent bug in the manual, you can't
use latex commands (\bf) inside a verbatim section.
i think there's an alternative section type where you
can do that.
There should not be any {\bf ...} inside a verbatim. If
On Fri, 29 Sep 2006, Les Mikesell wrote:
CentOS has some additions to the stock RH version as well,
like an optional kernel with firewire support and the
reiserfs and xfs filesystems. It uses yum for updates
and they generally stay within a few days of RH update
releases.
This is getting
If you point me to the exact file where there are
problems (the first
occurrence), I will be happy to fix it.
here's the diff -Naur for docs/manual/tips.tex taken
from your CVS (less than 1h ago).
i removed all {\bf inside verbatim sections, and
corrected 1 typo NFS,NSF.
if i have time, i
I just logged into Bacula from a client machine that has tighly restricted
access. It can only access its own pools, jobs, etc.
When I logged in with wx-console I was surprised by a sudden flood of queued
console messages for all jobs from last night. Those messages of course give
quite a
On Friday 29 September 2006 23:19, Michael Brennen wrote:
I just logged into Bacula from a client machine that has tighly restricted
access. It can only access its own pools, jobs, etc.
When I logged in with wx-console I was surprised by a sudden flood of queued
console messages for all
On Friday 29 September 2006 23:19, Michael Brennen wrote:
I just logged into Bacula from a client machine that has tighly restricted
access. It can only access its own pools, jobs, etc.
When I logged in with wx-console I was surprised by a sudden flood of queued
console messages for all
On Friday 29 September 2006 04:41 pm, Kern Sibbald wrote:
On Friday 29 September 2006 23:19, Michael Brennen wrote:
Offhand I don't see a good way in the Console resource to restrict
message access. Is the best option for the moment simply to disable
console message support and depend on
On Friday 29 September 2006 04:36 pm, Kern Sibbald wrote:
By the way, the current CVS has ACLs covering all the various restore
options.
I noted today on current cvs that the last 20 jobs list in the wx console now
gives a message about sql access denied or something like that. Thanks, that
hi michael,
You mentioned a few days ago that I might need to
supply some sort of
regression script test to demonstrate that. I don't
know what such a
regression script would look like or where to find
examples. If you can
point me to a section in the docs I will be glad to
supply
On Friday 29 September 2006 17:39, m listus wrote:
You mentioned a few days ago that I might need to
supply some sort of
regression script test to demonstrate that. I don't
know what such a
regression script would look like or where to find
examples. If you can
point me to a
hi,
i'm using 1.36.2 on sarge.
i get this kernel message on dmesg on a per job basis
i think:
st0: MTSETDRVBUFFER only allowed for root.
i read the Syslog Errors section in the tape testing
chapter, but it's too vague: . In general, the
message can be ignored providing you are sure that
your OS
32 matches
Mail list logo
