Hello, Arno Lehmann wrote:
Well, I haven't tried jobs going to different drives in one autochanger, so I won't discuss that part of your report.
Hopefully this is supported?! The "Maximum Changer Wait" option seems reasonable for the situation that both drives need a new tape at the same time. I'll increase this to 10 minutes because the loader is slow and fresh loaded tapes are read in even more slowly. I had to change the sleep time in mtx-changer (the load case) to 140 seconds. But to make that point clear .. no tape change was initiated whilst the descibed incedent occurred.
Usually, I'd see if the problem can be reproduced with the existing system setup. If that's possible, I'd first check if the actual cause might be purely SCSI device related.
That's what I'm going to do first. I'll create the second pool again (with the same tapes) and put all nodes into that pool. So a complete (Full) backup of all nodes should be done on drive two (150 GB). If this succeeds I'll try both drives again with 1.38.2 because all SCSI cables have been changed on Friday. If it fails again, I'll give 1.38.3 a try. Volker ------------------------------------------------------- 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
