[flexbackup-help] RE: loader

[Corey M. <ma...@pu...>]

"mtx next" unloads the current tape and then loads a tape from the next 
higher numbered slot -- my autoloader also automatically loads the first 
tape on startup (no need for the first mtx load; which it wouldn't 
matter anyway as "mtx next" will put in a tape... mtx load requires a 
slot number; unload does not (tape goes back into the slot it came from)

You could do mtx unload at the end, but an mtx next is probably 
preferable (make the next tape the first of the next set)

My autoloader does not do barcodes so this isn't an issue there. It also 
has a sequential mode which will span the tapes for me automatically 
(make them act as one tape)

As a suggestion, you might want to have a tape-change script (e.g. echo 
"Please insert new tape, then press enter"; read) or "mtx next" or 
however the end user would want to change the tapes... when you hit the 
end of the medium (that is an ideal solution though)

Hope this helps,
	--Corey

sample output (tape 1 is already loaded as if it were power-cycled):
[root@backup root]# mtx next
Unloading Data Transfer Element into Storage Element 1...done
[root@backup root]# mtx inquiry
Product Type: Medium Changer
Vendor ID: 'SEAGATE '
Product ID: 'LTO LDR CLL1600 '
Revision: 'S17r'
Attached Changer: No
[root@backup root]# mtx status
   Storage Changer /dev/changer:1 Drives, 8 Slots ( 0 Import/Export )
Data Transfer Element 0:Full (Storage Element 2 Loaded)
       Storage Element 1:Full
       Storage Element 2:Empty
       Storage Element 3:Full
       Storage Element 4:Full
       Storage Element 5:Full
       Storage Element 6:Full
       Storage Element 7:Full
       Storage Element 8:Full
[root@backup root]# mtx next
Unloading Data Transfer Element into Storage Element 2...done
[root@backup root]# mtx status
   Storage Changer /dev/changer:1 Drives, 8 Slots ( 0 Import/Export )
Data Transfer Element 0:Full (Storage Element 3 Loaded)
       Storage Element 1:Full
       Storage Element 2:Full
       Storage Element 3:Empty
       Storage Element 4:Full
       Storage Element 5:Full
       Storage Element 6:Full
       Storage Element 7:Full
       Storage Element 8:Full
[root@backup root]# mtx next
Unloading Data Transfer Element into Storage Element 3...done
[root@backup root]# mtx status
   Storage Changer /dev/changer:1 Drives, 8 Slots ( 0 Import/Export )
Data Transfer Element 0:Full (Storage Element 4 Loaded)
       Storage Element 1:Full
       Storage Element 2:Full
       Storage Element 3:Full
       Storage Element 4:Empty
       Storage Element 5:Full
       Storage Element 6:Full
       Storage Element 7:Full
       Storage Element 8:Full
[root@backup root]# mtx last
Unloading Data Transfer Element into Storage Element 4...done
[root@backup root]# mtx status
   Storage Changer /dev/changer:1 Drives, 8 Slots ( 0 Import/Export )
Data Transfer Element 0:Full (Storage Element 8 Loaded)
       Storage Element 1:Full
       Storage Element 2:Full
       Storage Element 3:Full
       Storage Element 4:Full
       Storage Element 5:Full
       Storage Element 6:Full
       Storage Element 7:Full
       Storage Element 8:Empty
[root@backup root]# mtx first
Unloading Data Transfer Element into Storage Element 8...done
[root@backup root]# mtx status
   Storage Changer /dev/changer:1 Drives, 8 Slots ( 0 Import/Export )
Data Transfer Element 0:Full (Storage Element 1 Loaded)
       Storage Element 1:Empty
       Storage Element 2:Full
       Storage Element 3:Full
       Storage Element 4:Full
       Storage Element 5:Full
       Storage Element 6:Full
       Storage Element 7:Full
       Storage Element 8:Full

[ Stephane Gauthier wrote: ]
  > I'm currently researching for a cheap backup solution for a cluster 
of 8
  > machines using an HP Surestore DAT 40x6e autoloader and was 
wondering if
  > you were planning on adding generic support  for loaders? (via the 
mtx util)

  I don't have access to such a device, or knowledge of how to operate them,
  so I'd need someone to work out the details, modify things, test, etc.

  About all I have is an mtx manpage :)

  One archive spanning multiple tapes would be hard, but bolting on mtx
  support to normal operation should not be too bad.

  Using flexbackups' method of "each set == new tape if doing level 0", 
do we
  just use "mtx next" instead of the manual prompting that's there now?

  It is mainly a matter of something like:
     - "mtx load" to start off,
     - "mtx next" to switch to a new tape
     - "mtx unload" when done
     - use "scsitape" rather than "mt"?

  Or is there more to it?  Just doing a quick search I can't find anything
  like an "mtx howto" document.  From what I understand some of these things
  get quite fancy and can do bar-code labels and such....


  (Anyone who knows how changers+mtx work is welcome to help out)


  --
   Edwin Huffstutler
   edwinh@co...   GnuPG Key ID: AE782DC9