On Mon, 2002-10-28 at 02:39, Francis Potter wrote:
> I have three questions, and I hope someone can help! Thanks in advance.
> QUESTION #1
> I'm trying to run Bacula on OpenBSD. So far, it seems like things are
> working except for the stop/start script, which seems to get the pid
> wrong (no big deal to work around). Has anyone tried Bacula on OpenBSD?
> Any reason why it shouldn't work?
As far as I know, no one has tried Bacula on OpenBSD. It will probably
not work without some minor modifications, but there is no reason why
we shouldn't be able to make it work.
Thanks for pointing out the problems with the "bacula" script. I wrote
that ages ago before I had pid files and should have updated it long
ago. I have now modified it so that it is much more likely to work
on your system. I'll send you a copy in another email.
> QUESTION #2
> I don't have a tape drive. I am trying to back up to a file and restore
> from it, to learn how the program works. (Config files included below.)
> Just for testing, I back up one small directory of web content. In the
> console, I said
> run TestSave
> and it seems like it ran OK. I can see that it's put some content into
> the directory where I told it to back up (/home/bacula/test). But then I
> try to restore it using
> run RestoreFiles
It would probably be better to use the "restore" command, unless
you take care to tweak the JobId in the RestoreFile job to
correspond to the job that saved the files.
> and it puts the job in some kind of queue. When I type
> status dir
> it says:
> roy-dir Version: 1.26a (25 October 2002)
> Daemon started 26-Oct-2002 22:27, 1 Job run.
> Last Job TestSave.2002-10-26_22.28.40 finished at 26-Oct-2002 22:28
> Files=0 Bytes=0 Termination Status=OK
> Console connected at 26-Oct-2002 22:48
> JobId 10 Job RestoreFiles.2002-10-26_22.37.57 is waiting execution.
> JobId 9 Job TestSave.2002-10-26_22.35.37 has been canceled.
> JobId 8 Job TestSave.2002-10-26_22.35.00 has been canceled.
> Backup job "TestSave" scheduled for 27-Oct-2002 01:05
> So my restore job is "waiting execution". Why? Shouldn't the "run"
> command in the console run the job right away? What is it waiting for?
> How can I get it to run, to see if it works?
> Note that I tried to run the backup job again in between a couple times,
> then cancelled them. Is that why the resore job is waiting? How can I
> really get rid of those jobs and get the restore to run?
I am not sure why the job is hanging, most likely because something
is not set properly for your system (e.g. pthreads). To keep this
email relatively short, I have added a new chapter to the manual
entitled "Porting Notes". You will find a lot more detail there on
how to go about getting Bacula running on a non-supported system.
Please see the online manual at:
Since most other features of Bacula seem to be working, this
could simply be a problem with attempting to restore with
an improper path to the File. Although Bacula works quite well
saving to files, I have not explicitly tried giving it
a bad Restore job, so it may be waiting for you to mount
the proper volume, which is of course, a bit stupid
for a file, but that is what Bacula wants.
The best way to get rid of those jobs is to cancel them
(as you did), then mount the backup file from the
Console. Just say "mount" and it will probably select
the correct pool. That should free up the jobs. If
not, the only solution is to bring down the daemons
and restart them.
> QUESTION #3
> I tried using bls and bextract to see what's in the archive, but it
> keeps trying to mount my file as if it were a tape. Here's what I get:
> roy# bls /home/bacula/test
> bls: bls Warning: acquire.c:92 Volume on /home/bacula is not a Bacula
> labeled Volume, because:
> block.c:444 Read zero bytes on device /home/bacula.
> Mount Volume "test" on device /home/bacula and press return when ready:
These programs do work with files, but you need to give them the
filename where the backup was done (i.e. the Volume name). In looking
at your conf files below, I would guess that things will work better
when you say:
though I have always used /tmp/Volumename, so there could possibly
be a problem with handling multiple slashes.
> I defined the label in the console; isn't that right? Here's a list
> media from the console:
> *list media
> Defined Pools:
> 1: Default
> Item 1 selected automatically.
> | MediaId | VolumeName | MediaType | VolStatus | VolBytes |
> LastWritten | VolRetention | Recycle | Slot |
> | 1 | myVolume | File | Append | 31,610 | 2002-10-26
> 22:28:49 | 31,536,000 | 1 | 0 |
This looks fine to me. It shows that you did write on the
Volume, so things look pretty good -- it should just be a matter
of getting the path to the Volume correct on the ./bls and ./bextract
> I don't think it's a permissions problem since the file looks like this
> in ls:
> drwxrwxrwx 2 root wheel 512 Oct 26 22:24 test
> Bacula looks like a good application and I'd love to use it for our
> server and small office (6 people, ~10 machines) if I can get it to
> work. Thanks in advance for the help!
I've taken a careful look at your configuration files
and they look good to me.
Please let us know if you get it to work