Dear Julien,
Under 2.6 try (note stsetoptions, not stoptions):
mt -f /dev/nst0 stsetoptions 0
dmesg | grep st0
That should give you the information you need. Clearly from the existing info
your drive is coming
Up incorrectly. What remains to be seen is whether we can force it permanently
to
Dear Julian,
This is good, but we were both referring to in between jobs (after daemon has
started). The original commands I gave:
mt -f /dev/nst0 setstoptions 0
grep st0 /var/log/messages
Will show you if these settings are being changed indvertedly by either (a)
bacula or (b) the kernel drive
Dear Julien,
The only thing I can suggest now is that you review what happens to the
tape options via:
mt -f /dev/nst0 stoptions 0
grep st0 /var/log/messages
Between backup and restore (i.e. before backup and before restore but
after the mount command) in case they are being reset somehow (by th
Dear Julian,
In order to execute 'tapeinfo' in Linux you need to make sure the 'sg'
module is loaded. This is the generic scsi module and can be loaded as
follows:
modprobe sg
You can check it's loaded with:
lsmod | grep sg
You can force this to be loaded at boot time by adding it to
/etc/modu
Dear Thomas,
I had a similar problem with my setup. It turned out that the version of
mtx installed on the machine was a little too far out of date and didn't
handle the additional 'zero' being added to indicate the drive index
from the mtx-changer script.
Assuming you have the same issue, I sug
Dear Gregory & Brauer,
I circumvented this issue in 1.36 using the following technique:
We have an autoloader that has tapes changed every day.
Prior to running the scheduled jobs for the night the first job (with high
priority so it runs first) is an admin job that uses the
RunBeforeJob script to
Dear Sylvain,
This indicates that the storage daemon requires root privileges to
alter the scsi drive's configuration (such as setting the buffer size).
This actually caused a significant amount of problems for me when trying
to run an autochanger and in the end the only way I could resolve it wa
Dear Paul,
When performing a job, the file daemon (FD) connects _directly_ to the storage
daemon (SD).
This is different from the console which performs status requests via the
director daemon (DIR).
This can cause confusion when setting up firewalls and making sure ports are
open.
You need t
Dear Kern,
Thanks for this, I'll get the test version patched sometime in the next 2-3
days.
Best Regards,
Brett
-Original Message-
From: Kern Sibbald [mailto:[EMAIL PROTECTED]
Sent: 15 August 2005 17:56
To: Brett Delle Grazie
Cc: bacula-users@lists.sourceforge.net; [EMAIL PROTECTED];
Dear Kern,
I'm inclined to agree with Phil & Thomas and your own comments.
Since the FileSet we use includes the 'readfifo' option, why not:
never overwrite an existing fifo if this option is set on a restore operation?
It then becomes the Run before client's job to create this fifo with the
ap
Dear Thomas,
Thanks,
These scripts were most helpful!
I've thought about a couple of solutions which bypass the manual modification
to the permissions and the
issue where the restore is started before the pipe is created. They go like
this:
1) add to the bacula group the db2inst1 user and re
Hi,
I'm using bacula to
backup a DB2 database to a fifo.
The backup is
working correctly thanks to the additions made to the developer's
documentation.
The problem I have
at the moment is getting the restore process to work.
The idea was to
create the fifo (using mkfifo) in the same loca
Hi,
I already have
bacula installed on a two machine system and am very pleased with it's
operation and performance - great job!
I'd like to use it
in different installation where the director and storage daemons
reside on different machines.
I'm using Redhat
Enterpise Linux AS 2.1 and 3 (
13 matches
Mail list logo
