Hi folks,
While Bacula backups are running, the library system (IBM TS3200)
figures one of the tape drives requires head cleaning and tries to load
the cleaning tape.
Following is the first email message generated from the tape-library:
-------------------------- start ----------------------------
Device : <
FLX10D488 AT xxx DOT com>
Attention : Drive Cleaning request
Drive number: 0x01, 1
This message was generated automatically from
IBM 3573-TL
---------------------------- end -----------------------------
The next email alert generated immediately after the first one:
--------------------------- start --------------------------------
Device : <
FLX10D488 AT xxx DOT com>
Attention : Crit or Warn Drive Tape Alert flag
Number: 0x20, 32
Drive number: 0x01, 1
Tape Alert Flag: 0x15, 21
This message was generated automatically from
IBM 3573-TL
---------------------------- end -------------------------------------
After a few minutes, Bacula sends a "Backup Fatal Error" message:
-------------------------- start
----------------------------------------
17-Dec 06:03 backupserver-sd JobId 6587: 3304 Issuing autochanger "load
slot 34, drive 0" command.
17-Dec 06:06 backupserver-sd JobId 6587: Fatal error: 3992 Bad
autochanger "load slot 34, drive 0": ERR=Child died from signal 15:
Termination.
Results=Program killed by Bacula watchdog (timeout)
17-Dec 06:06 backupserver-fd JobId 6587: Fatal error: job.c:1811 Bad
response to Append Data command. Wanted 3000 OK data
, got 3903 Error append data
-------------------------------- end
--------------------------------------
Anyone has had the same experience? Anyway to prevent this "tape
library and Bacula tripping over each other" in the future?
TIA.