Hello,
Kern Sibbald schrieb:
On Monday 12 December 2005 12:54, Volker Dierks wrote:
Sorry, I forgot to attach the file ... here it is.
Well, you fell into a documentation error. Please remove the line from your
Device resources that says:
Maximum Changer Wait = 10 minutes
it is incorrect. Despite what the *old* documentation said, the time *must*
be specified in seconds.
Yes. ;-)
Even better: Also edit the script to use the wait_for_tape function (or
whatever it's called.) Assuming you can reliably get the tape status,
this is a much cleaner solution - I've seen tape load times from a few
seconds to some minutes one one and the same drive (DLT, admittedly :-)
but I prefer to wait until a drive is ready over the fixed timeout.
Also, in case the security timeout in the function waiting for the tape
to be loaded ever triggers, it is useful to write some log data,
especially containing tapealert data. I think that, given a sufficently
long emergency timeout, almost all cases of a tape not recognized by the
tape drive indicate a serious failure.
For example my configuration:
- in mtx-changer's wait_for_drive function, I poll every three seconds
for some hundred times.
- In bacula-sd.conf, I set a timeout of 20 minutes or something. This
should never be reached, of course.
If you want to set it to 10 minutes you need to set it to 600.
You probably also want to increast the sleep in mtx-changer ...
Definitely...
Arno
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
