amtapetype(8) [debian man page]
AMTAPETYPE(8) System Administration Commands AMTAPETYPE(8) NAME
amtapetype - generate a tapetype definition by testing the device directly SYNOPSIS
amtapetype [-h] [-c] [-f] [-p] [-b blocksize] [-t typename] [-l label] [-o configoption...] [config] [device] DESCRIPTION
amtapetype generates a tapetype entry for Amanda by testing the device directly. OPTIONS
Note The options for amtapetype have changed in version 2.6.1 -h Display the help message. -c Run only the hardware compression detection heuristic test and stop. This takes a few minutes only. -f Run amtapetype even if the loaded volume is already labeled. -p Run only the device property discovery. -b blocksize block size to use with the device (default: 32k) -t typename Name to give to the new tapetype definition. -l label Label to write on the tape (default is randomly generated). -o configoption See the "CONFIGURATION OVERRIDE" section in amanda(8). If a configuration is specified, it is loaded and used to configure the device. Note that global configuration parameters are not applied to the device, so if you need to apply properties to a device to run amtapetype, you should supply those properties in a named device section. EXAMPLE
Generate a tapetype definition for your tape device: % amtapetype -f /dev/nst0 NOTES
If the device cannot reliably report its comprssion status (and as of this writing, no devices can do so), hardware compression is detected by measuring the writing speed difference of the tape drive when writing an amount of compressable and uncompresseable data. If your tape drive has very large buffers or is very fast, the program could fail to detect hardware compression status reliably. Volume capacity is determined by writing one large file until an error, interpereted as end-of-tape, is encountered. In the next phase, about 100 files are written to fill the tape. This second phase will write less data, because each filemark consumes some tape. With a little arithmetic, amtapetype calculates the size of these filemarks. All sorts of things might happen to cause the amount of data written to vary enough to generate a strange file mark size guess. A little more "shoe shining" because of the additional file marks (and flushes), dirt left on the heads from the first pass of a brand new tape, the temperature/humidity changed during the multi-hour run, a different amount of data was written after the last file mark before EOT was reported, etc. Note that the file mark size might really be zero for whatever device this is, and it was just the measured capacity variation that caused amtapetype to think those extra file marks in pass 2 actually took up space. SEE ALSO
amanda(8), amanda.conf(5) The Amanda Wiki: : http://wiki.zmanda.com/ AUTHORS
Dustin J. Mitchell <dustin@zmanda.com> Zmanda, Inc. (http://www.zmanda.com) Jean-Louis Martineau <martineau@zmanda.com> Zmanda, Inc. (http://www.zmanda.com) Amanda 3.3.1 02/21/2012 AMTAPETYPE(8)
Check Out this Related Man Page
AMLABEL(8) System Administration Commands AMLABEL(8) NAME
amlabel - label an Amanda tape SYNOPSIS
amlabel [--barcode barcode] [--meta meta-label] [--assign] [-f] [--version] [-o configoption...] config [label] [slot slot] DESCRIPTION
This command applies a label to an Amanda volume, erasing the volume in the process. Amanda uses labels to identify volumes: amdump(8) and amflush(8) verify the label before writing to make sure the proper volume is loaded, and the recovery programs use the label to ensure they are reading the data they expect. If no [slot] and no [barcode] is given, then amlabel labels the tape in the current slot of the default changer. If a slot is given, it labels the volume in that slot. If a barcode is given, it labels the volume with that barcode. Label may be any string that does not contain whitespace and that matches the labelstr (see amanda.conf(5)). If [label] is not given, an autolabel is generated, see autolabel in amanda.conf(5). If [--assign] is given, the barcode and meta-label are assigned to the label without labeling the volume. The label must already be in the tapelist file. This command also appends the new volume to the tapelist(5) file, so that they will be used in the order they are labeled (depending on the taperscan in use -- see amanda-taperscan(7)). As a precaution, amlabel will not write a label if the volume already contains an active label or if the label specified is on an active tape. The [-f] (force) flag bypasses these verifications. OPTIONS
--barcode barcode With [--assign], assign the barcode to the label. Without [--assign], label the volume with that barcode. --meta meta-label Assign the meta label to the label after labeling the volume. --assign Assign the barcode or meta-label to the label without labeling the volume. The label must already be in the tapelist file. -f Force the label operation; see above --version Output version information -o configoption See the "CONFIGURATION OVERRIDE" section in amanda(8). EXAMPLE
Write an Amanda label with the string "DMP000" on the current volume: % amlabel daily DMP000 Label the tape in slot 3 of the changer with the label "DMP003": % amlabel daily DMP003 slot 3 MESSAGES
Label 'label' doesn't match labelstr 'labelstr' The given label does not match the configured labelstr. Even with -f, this is an error. Label 'label' already on a volume The given label is already on another volume in the tapelist, and Amanda will not write it to this volume unless forced. Found label 'label', but it is not from configuration config. The label amlabel found on the volume does not match this configuration's labelstr, so it is probably part of a different Amanda configuration. Amanda will not overwrite the label unless it is forced. Volume with label 'label' contains data from this configuration. The label amlabel found on the volume still has valid data on it and Amanda will not overwrite it unless forced. Note that this does not distinguish between active and inactive volumes. SEE ALSO
amanda(8), amanda.conf(5), tapelist(5), amanda-taperscan(7), amdump(8), amflush(8) The Amanda Wiki: : http://wiki.zmanda.com/ AUTHORS
James da Silva <jds@amanda.org> Stefan G. Weichinger <sgw@amanda.org> Dustin J. Mitchell <dustin@zmanda.com> Zmanda, Inc. (http://www.zmanda.com) Amanda 3.3.3 01/10/2013 AMLABEL(8)