At first I was somewhat confused about what the current behaviour is, both
by this thread, the documentation and my experience with file matching
algorithms used by other programs such as the various shells.
Judging from your example below I believe you may be confused about the
current behaviour
I apologize if this has been addressed, but I
couldnt find anything in the archives. If this is the incorrect
list for this inquiry, please point me in the correct direction.
Ive been using Bacula (1.36.0) to back up our
servers for about 2 years now. Everything has been running fine,
Lowe, Bryan wrote:
are backing up fine, it’s just those 2 that choke. When I check my
firewall logs, the service that gets blocked seems to be different every
week! One week it’s tcp port 39450 and port 36401, the next week it’s
50596 and 39398, etc.
It sounds like you're looking
I have been looking at the Sourceforge page and am confused as to
what is the latest stable release as opposed to an experimental one.
I'm just a Bacula user, not developer, but I would consider Bacula quite a
mature and stable software. Like any software, it has some bugs that will be
found
Hello,
I'm sorry, I'm not interested in changing how WildFile currently works. I
thought about it a long time, and IMO changing it would create lots of
problems with current users, not to mention require changing the manual.
In addition, I am not interested in FNM_FILE_NAME, because unless
Bob Ward wrote:
the latest stable release, it sure would be nice. But I suppose if it were
that simple, I could have hired a relative. ;^)
I don't think Kern makes unstable releases, just stable ones. If
you want unstable code you checkout CVS :)
Bob Ward
--
Chris Crowther
On Monday 17 April 2006 13:55, Dominic Marks wrote:
Bob Ward wrote:
All-
I have been looking at the Sourceforge page and am confused as to what is
the latest stable release as opposed to an experimental one. If the
Sourceforge format would allow for a simple definitive statement that
It seems from this discussion the manual needs changing anyways.
FNM_FILE_NAME is GNU specific, posix uses FNM_PATHNAME, behaviour is the
same. I just used FNM_FILE_NAME because that is what you already use in
some places in the source. So I don't believe there is any portability
issue,
How very strange, I originally had FNM_PATHNAME in the email and then did a
grep to see which of the two names were used in the source. However
sometime between doing the grep and editting the email I swapped the two in
my head. The source refers to FNM_PATHNAME not FNM_FILE_NAME. But it is
I am new to bacula and I am trying to configure my setup. I am running
Fedora Core 3 and using a Dell 124T. From what I can see the Dell 124T
has passed all of the tests. So now I am trying to edit the
configuration files.
In the bacula-sd.conf I have this defined:
Autochanger {
Name =
Hi everyone
I'm currently trying to configure bacula (I'm a newbie). But I've some little
problems.
I've made the definitions for 4 tapepools. In bacula-dir.conf, I've 2 jobs:
Job {
Name = Intranetserver
Type = Backup
Level = Full
Client = localhost-fd
FileSet = Full Set
Schedule =
Hi people. I want to test my tape device with bacula 1.38.5 running on FreeBSD 5.4-p10. My tape device is: *HP Surestore Ultrium 230 *Tape 200GB *SCSI card is one Adaptec 29160
My dmesg output say this:pass0 at ahc0 bus 0 target 6 lun 0pass0: HP Ultrium 1-SCSI E22D Removable Sequential Access
You need to add a storage resource to bacula-dir.conf.
This is the abstraction for a device controlled by a Storage Daemon.
You probably want something like
Storage {
Name = name, this is what you put in the Job / JobDefs
Address = IP Address or Name of system running bacula-sd
SDPort =
I thought I'd share a cool little tweak that I did to my bacula-
dir.conf file to write a bootstrap as well as email it (multiple
copies are always good). This way you don't need to worry about
maintaining an additional script.
Write Bootstrap = | /bin/sh -c '/usr/bin/tee BOOTSTRAP_FILE
OK I see where I made that mistake. I now get the following errors at
startup:
[EMAIL PROTECTED] bin]# ./bacula start
Starting the Bacula Storage daemon
Starting the Bacula File daemon
Starting the Bacula Director daemon
17-Apr 13:27 bacula-dir: Fatal error: type directive in Job
BackupCatalog
First off I don't think you're allowed to have multiple resources of the
same type with the same name. So I would either rename one of them or if
you aren't using it just remove it. The job resource must contain those
directives, either specified in the job resource or inherited from a
JobDefs.
Ok. Thanks to Robert and some more RTFM work I was able to start bacula.
I now have a new issue. This is the first time running this so bacula
sees that no Full backup was performed and elevates the differential to
a Full. Here is what I get:
*run
A job name must be specified.
The defined Job
Sorry I'm too poor to have an autochanger :-). Someone else will have to
take over from here.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Boris
Sent: Monday, April 17, 2006 11:27 AM
To: bacula-users@lists.sourceforge.net
Subject: RE:
On the 132T I had to edit the mtx-changer script and change sleep 15 to wait_for_device ( documented in script ) even though the btape utility worked fine.Cheers,EricOn 4/17/06,
Robert Nelson [EMAIL PROTECTED] wrote:
Sorry I'm too poor to have an autochanger :-).Someone else will have totake over
Thanks again Dan the Problem is solved not sure how!! Seems to be woking now
all except the status just a little box with an x in it. Quite strange what do
u think might have caused this to start working?
- RYAN M. vAN GINNEKEN [EMAIL PROTECTED] wrote:
- Dan Langille [EMAIL PROTECTED]
From list jobs I see the following jobstatus:
A
C
R
T
f
What do they mean? Is there a place where the complete list of values is
explained? Tried the pdf manual and a search for jobstatus did not return
a list that I could find.
---
21 matches
Mail list logo
