On Wednesday 06 March 2002 09:37 am, Zhen Liu wrote: [snip]
>From: Zhen Liu <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Date: Mon, 04 Mar 2002 12:03:21 -0500 > >Hi, > >I am working on the amanda backup project now, and I am a newbie for >both amanda and linux... right now, I have some problem with our tape >changer...SOS!!! & HELP!!! > >The OS I am working on is Linux RH7.1, the tape changer we have is >Adic Fastor, Quantum 7000 tape drive. > >I guess that something must be wrong with my configuration...when i >run amcheck i get "amcheck-server: could not get changer info: open: >/dev/sg0: success" > >-----relevant part from /etc/amanda/daily/amanda.conf---- > >runtapes 2 >tpchanger "chg-scsi" >tapedev "0" >changerfile "etc/amanda/DailySet1/changer.conf" >changerdev "dev/sg0 ^^^^^^^^^^^^^^^^^^^^ I don't believe this is the correct device for the changer although it varies from mechanism to mechanism. It also isn't required to define it twice as you have here, and in fact it could confuse things. Some changers address the changer robot at the next device up in the scsi address scheme, and some will address it at Logical Unit 1 at the same bus ID number as the drive is, using lun 0 for the drive. In order to see the rest of such a device that uses lun's other than 0, you will have to re-compile your kernel after turning on the 'SCAN ALL LUNS' option with a "make xconfig" or other method. This will make the boot a little slower, particularly if the actual device address is 6 as it will scan all luns for all bus addresses, taking about 1 second per lun at 7 luns per address. Because of this, I usually set the hardware address to whatever is the next one above any disk drives, purposely placing the disks first in the find sequence so they don't get re-addressed if the tape drive sneezes wrong. Once that is done and the new kernel installed and the machine rebooted, you may then inspect (less /var/log/dmesg) the boot records to see what actual device has been assigned to the robot when it was found. Insert that line in the changer.conf file, leaving the one in amanda.conf out completely. >----- /etc/amanda/DailySet1/changer.conf----- >number_configs 1 ># eject 1 >sleep 60 >cleanmax 1000 >changerdev /dev/sg0 > ># ># Next comes the data for drive 0 ># >config 0 >drivenum 0 >dev /dev/nst0 >startuse 0 >enduse 6 >statfile /etc/amanda/DailySet1/st0-slot >cleancart -1 >cleanfile /etc/amanda/DailySet1/st0-clean >usagecount /etc/amanda/DailySet1/st0-totaltime > > >So, I am totally lost...Help? Do you keep a cleaning tape in the last numerical slot? If so, reduce the enduse by one, and tell it the 'cleancart' is in that last slot. Amanda will then do it automaticly (or should anyway) when the drive says it needs cleaning. And FWIW, cleaning tapes should not be reused 1000 times as they will have become way too contaminated to be usefull after 5 or 6 passes at best. But, amanda counts the number of times its been used for one cleaning cycle, and that normally is just a small fraction of the tape in the cartridge. Some drives won't even rewind the cleaning tape, forcing a fresh tape when that one is used up. -- Cheers, Gene
