After setting "autoclean=1" as well as appropriate values for cleanslot and 
autocleancount inside /etc/amanda/<config>/changer.conf, is there a way to 
confirm when the autoclean process runs, assuming the autocleancount has been 
reached?  When I check the debug log 
(/var/log/amanda/chg-zd-mtx.20120304014524.debug) from last Sunday's dump after 
which I was expecting an autocleaning--I see where the cleaner tape was loaded, 
but I don't think it was in the drive long enough to have been used to clean 
it.  Does this look like the autoclean process ran successfully and if so, is 
there a way to have AMANDA include the cleaning status in it's mail report?  
I'm running version 2.5.0p2-8 that's provided/built for Red Hat Enterprise 
Linux Server release 5.7 x86_64.  The tape from slot 13 was used for last 
Sunday's dump and cleanslot is set to 16.

<snip>
01:45:26 Running: mtx unload 13 0
01:46:38 Exit code: 0
         Stderr:
Unloading Data Transfer Element into Storage Element 13...done
01:46:38          -> status 0, result "Unloading Data Transfer Element into 
Storage Element 13...done"
01:46:38 Return (0) -> 13 /dev/nst0
01:46:38 LOADSLOT -> loading tape from slot 16 to drive 0 (/dev/nst0)
01:46:38 Running: mtx load 16 0
01:47:28 Exit code: 0
01:47:28          -> status 0, result ""
01:47:28 Running: sleep 120
01:49:28 Exit code: 0
01:49:28 Return (0) -> 16 /dev/nst0
01:49:28 Running: mtx status
01:49:30 Exit code: 0
         Stdout:
  Storage Changer /dev/changer:1 Drives, 16 Slots ( 0 Import/Export )
Data Transfer Element 0:Full (Storage Element 16 Loaded):VolumeTag = CLNU00L1   
                     
      Storage Element 1:Full :VolumeTag=000052L3                        
      Storage Element 2:Full :VolumeTag=000053L3                        
      Storage Element 3:Full :VolumeTag=000054L3                        
      Storage Element 4:Full :VolumeTag=000055L3                        
      Storage Element 5:Full :VolumeTag=000056L3                        
      Storage Element 6:Full :VolumeTag=000057L3                        
      Storage Element 7:Full :VolumeTag=000058L3                        
      Storage Element 8:Full :VolumeTag=000059L3                        
      Storage Element 9:Full :VolumeTag=000020L3                        
      Storage Element 10:Full :VolumeTag=000027L3                        
      Storage Element 11:Full :VolumeTag=000022L3                        
      Storage Element 12:Full :VolumeTag=000023L3                        
      Storage Element 13:Full :VolumeTag=000024L3                        
      Storage Element 14:Full :VolumeTag=000025L3                        
      Storage Element 15:Full :VolumeTag=000026L3                        
      Storage Element 16:Empty
01:49:30 STATUS   -> currently loaded slot = 16
                  -> currently loaded barcode = "CLNU00L1"
01:49:30 EJECT    -> ejecting tape from /dev/nst0
01:49:30 STATUS   -> currently loaded slot = 16
                  -> currently loaded barcode = "CLNU00L1"
01:49:30 EJECT    -> moving tape from drive 0 to storage slot 16
01:49:30 Running: mtx unload 16 0
01:50:20 Exit code: 0
         Stderr:
Unloading Data Transfer Element into Storage Element 16...done
01:50:20          -> status 0, result "Unloading Data Transfer Element into 
Storage Element 16...done"
01:50:20 Return (0) -> 16 /dev/nst0
01:50:20 LOADSLOT -> loading tape from slot 16 to drive 0 (/dev/nst0)
01:50:20 Running: mtx load 16 0
01:51:03 Exit code: 0
01:51:03          -> status 0, result ""
01:51:03 Running: sleep 120
01:53:03 Exit code: 0
01:53:03 Exit (0) -> 16 /dev/nst0
chg-zd-mtx: pid 11628 finish time Sun Mar  4 01:53:03 2012



Thank you,

Pete Nichter
Network and UNIX System Administrator
State University of New York
Information Technology Exchange Center
E-mail: [email protected]
PGP Key ID: 6C4249B7



Reply via email to