Which version of amanda are you using? Are you sure the tape-device property is correctly set? try: amtape Weekly1-library1 verify
Jean-Louis On 10/02/2014 03:29 PM, Mike Driscoll wrote:
I’ve used amanda with virtual tapes successfully for years. I’m now attempting to add a physical tape library for the first time, a StorageTek SL150 with two LTO6 drives. After I have confidence in the configuration and some testing, the first few actual, scheduled dumps run fine. But around the 4th or 5th regularly scheduled dump, I consistently get errors about barcode mismatches with tape labels. I label tapes using commands like this: amlabel -f --barcode CA0014 Weekly1-library1 Weekly1-library1-CA0014 First, is there documentation to define specific definitions for LTO6 and or StorageTek libraries? The only source I’ve found is this, but these devices are absent. http://wiki.zmanda.com/index.php/Tapetype_definitions Absent that, does anyone have any advice about how to avoid delayed/intermittent barcode mismatch problems? Here’s a typical example of the error: ERROR: Slot 16, label 'Weekly1-library1-CA0014', mismatch barcode between changer 'CA0017' and tapelist file 'CA0014' Server check took 245.881 seconds amanda.conf file includes: define changer sl150-robot { tapedev "chg-robot:/dev/changer" #tape/by-id/scsi-3500104f000d21512" property "tape-device" "0=tape:/dev/nst0" "1=tape:/dev/nst1” length 2442818848 kbytes filemark 1806 kbytes speed 74006 kps blocksize 32 kbytes } labelstr "Weekly1-library1-CA00[0-9][0-9]" amrecover_changer "sl150-robot" tapedev "sl150-robot" tapetype LTO6
