amtape - Control Amanda changers
amtape [-o configoption...]
config subcommand [subcommand_options...]
Amtape is the command-line interface to Amanda's tape changers
(amanda-changers(7)) and to the taperscan algorithm
Tape changers maintain a notion of the current slot for
each configuration. This may or may not correspond to an actual physical
state of the device, but is used by some taperscan algorithms to minimize
searching through the slots.
Amtape uses the default changer. To use a different changer, use
the config override option, e.g., -otpchanger=otherchanger.
Call the changer create method, it create the vtape root
dirtectory or the s3 bucket.
Search for and load the Amanda tape with label [label],
also setting the current slot.
slot slot [drive drive]
Load the volume in the given slot, also setting the
current slot. The slot names current, next, first, and
last have special meaning.
Shorthand for slotcurrent.
Show the contents of all slots, based on the changer's
cached metadata. This is a quick operation as it does not load or unload any
volumes, but is not supported by all changers.
Show the contents of all slots (or listed slots) by
loading each slot and reading its label. This can be very slow. The slots
arguments is of the form 1,3-5,7.
Reset the changer to a known state. This subcommand is
intended to clear any unknown and potentially incorrect state the changer may
Eject the tape currently in the drive. This only applies
to some changers. Specify a drive (by drive number) if more than one drive is
If a cleaning tape is defined for the changer, used it to
clean the specified drive. The [drive] is optional if the changer only has one
sync the catalog with a device that support it,
Run the taperscan algorithm (see
), displaying information about the progress of the
Update changer state. Consult amanda-changers(7)
for changer-specific details on the format of what.
Verify the changer is correctly configured. Can be useful
for chg-robot and chg-ndmp.
See the "CONFIGURATION OVERRIDE" section in
Dustin J. Mitchell <firstname.lastname@example.org>
James da Silva <email@example.com>
Stefan G. Weichinger <firstname.lastname@example.org>