Thank you John, I have a couple of questions which are outlined below. >> When I run two jobs at the same time which want to write to two >> different >> tapes, the second one fails immediately rather than both spooling and >> the >> first one to finish de-spooling to tape, this is clear from the >> following >> error message: >> 03-Oct 07:00 abc-dir: Start Backup JobId 58, >> Job=def-backup.2007-10-03_07.00.00 >> 03-Oct 07:00 abc-dir: Using Device "DLT-V4" >> 03-Oct 07:00 xyz-fd: ClientRunBeforeJob: run command >> "/etc/bacula/waitforntbackup" >> 03-Oct 11:09 backupserver-sd: def-backup.2007-10-03_07.00.00 Fatal >> error: >> acquire.c:355 Wanted to append to Volume "CNI910", but device "DLT-V4" >> (/dev/nst0) is busy writing on "CNI911" . >> 03-Oct 11:09 xyz-fd: def-backup.2007-10-03_07.00.00 Fatal error: >> job.c:1758 Bad response to Append Data command. Wanted 3000 OK data >> , got 3903 Error append data >> > The weird part here is that bacula started a second job knowing it > could not write to the second tape at the same time as the first tape. Could it have done this because it has an autochanger?
> In normal circumstances on a single device bacula will only allow > concurrency on the jobs that want to use the same pool and they all > write to the same volume. So what you are saying is that it should have queued the jobs? Many thanks, Spencer ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
