.\" Title: amanda-changers
.\" Author: Dustin J. Mitchell <dustin@zmanda.com>
.\" Generator: DocBook XSL Stylesheets vsnapshot_8273 <http://docbook.sf.net/>
-.\" Date: 06/01/2010
+.\" Date: 10/18/2010
.\" Manual: Miscellanea
-.\" Source: Amanda 3.1.0
+.\" Source: Amanda 3.2.0
.\" Language: English
.\"
-.TH "AMANDA\-CHANGERS" "7" "06/01/2010" "Amanda 3\&.1\&.0" "Miscellanea"
+.TH "AMANDA\-CHANGERS" "7" "10/18/2010" "Amanda 3\&.2\&.0" "Miscellanea"
.\" -----------------------------------------------------------------
.\" * set default formatting
.\" -----------------------------------------------------------------
tapedev "chg\-robot:/dev/sg1"
property "tape\-device" "0=tape:/dev/nst0"
property append "tape\-device" "1=tape:/dev/nst1"
- device_property "BLOCK_SIZE" "512k"
+ device\-property "BLOCK_SIZE" "512k"
}
# \&.\&.\&.
tapedev "hp\-robot"
.PP
Devices, too, can take properties to control their behavior (see
\fBamanda-devices\fR(7))\&. Device properties can come from four places: implicit device properties (from tapetype parameters), global device properties (from global
-\fIdevice_property\fR
+\fIdevice\-property\fR
parameters), properties in device definitions, and properties in changer definitions\&. Properties are applied in this order, with later properties taking priority\&.
.PP
There are only three implicit properties:
\fIchangerfile\fR
must exist; it is used to save the state file\&.
.PP
+The child devices are specified using the same syntax as for the RAIT device (see
+\fBamanda-changers\fR(7))\&. The range specification can be especially useful here:
+.sp
+.nf
+tpchanger "chg\-multi:s3:mycompany\-backups/tape\-{001\&.\&.100}"
+.fi
+.PP
This changer is not fast\-search capable\&.
.SS "Properties"
.PP
The username for the NDMP server\&.
.RE
+.PP
+VERBOSE
+.RS 4
+
+If true, enables the NDMJOB library\'s verbose (packet\-level) debugging\&.
+.RE
.SS "Unmaintained Changers"
.PP
Amanda has many other changer scripts and programs beyond those described here (see the