+\fBpost\-estimate\fR
+.RS 4
+Execute after the estimate command for all dle\&. Can only be run on server\&.
+.RE
+.PP
+\fBpost\-dle\-estimate\fR
+.RS 4
+Execute after the estimate command for the dle\&.
+.RE
+.PP
+\fBpost\-host\-estimate\fR
+.RS 4
+Execute after the estimate command for all dle for the client\&.
+.RE
+.PP
+\fBpre\-backup\fR
+.RS 4
+Execute before the backup command for all dle\&. Can only be run on server\&.
+.RE
+.PP
+\fBpre\-dle\-backup\fR
+.RS 4
+Execute before the backup command for the dle\&.
+.RE
+.PP
+\fBpre\-host\-backup\fR
+.RS 4
+Execute before the backup command for all dle for the client\&. It can\*(Aqt be run on client, it must be run on server
+.RE
+.PP
+\fBpost\-backup\fR
+.RS 4
+Execute after the backup command for all dle\&. Can only be run on server\&.
+.RE
+.PP
+\fBpost\-dle\-backup\fR
+.RS 4
+Execute after the backup command for the dle\&.
+.RE
+.PP
+\fBpost\-host\-backup\fR
+.RS 4
+Execute after the backup command for all dle for the client\&. It can\*(Aqt be run on client, it must be run on server
+.RE
+.PP
+\fBpre\-recover\fR
+.RS 4
+Execute before any level is recovered\&.
+.RE
+.PP
+\fBpost\-recover\fR
+.RS 4
+Execute after all levels are recovered\&.
+.RE
+.PP
+\fBpre\-level\-recover\fR
+.RS 4
+Execute before each level recovery\&.
+.RE
+.PP
+\fBpost\-level\-recover\fR
+.RS 4
+Execute after each level recovery\&.
+.RE
+.PP
+\fBinter\-level\-recover\fR
+.RS 4
+Execute between two levels of recovery\&.
+.RE
+.sp
+If you recover level 0 and 2 of the disk /usr with amrecover, it will execute:
+.nf
+script \-\-pre\-recover
+script \-\-pre\-level\-recover \-\-level 0
+#recovering level 0
+script \-\-post\-level\-recover \-\-level 0
+script \-\-inter\-level\-recover \-\-level 0 \-\-level 2
+script \-\-pre\-level\-recover \-\-level 2
+#recovering level 2
+script \-\-post\-level\-recover \-\-level 2
+script \-\-post\-recover
+.fi
+.RE
+.PP
+\fBproperty\fR [\fBappend\fR] [\fBpriority\fR] \fIstring\fR \fIstring\fR+
+.RS 4
+No default\&. You can set property for the script, each script have a different set of property\&. Both strings are quoted; the first string contains the name of the property to set, and the others contains its values\&.
+\fBappend\fR
+keyword append the values to the list of values for that property\&.
+\fBpriority\fR
+keyword disallow the setting of that property on the client\&.
+.RE
+.SH "DEVICE SECTION"
+.PP
+Backend storage devices are specified in
+\fBamanda\&.conf\fR
+in the form of "device" sections, which look like this:
+.nf
+define device \fIname\fR {
+ commend "\fIcomment (optional)\fR"
+ tapedev "\fIdevice\-specifier\fR"
+ device\-property "\fIprop\-name\fR" "\fIprop\-value\fR"
+ \&.\&.\&.
+}
+.fi
+.PP
+The { must appear at the end of a line, and the } on its own line\&.
+.PP
+\fIname\fR
+is the user\-specified name of this device\&. It is referenced from the global
+\fItapedev\fR
+parameter\&. The
+\fIdevice\-specifier\fR
+specifies the device name to use; see
+\fBamanda-devices\fR(7)\&. As with most sections, the
+\fIcomment\fR
+parmeter is optional and only for the user\*(Aqs convenience\&.
+.PP
+An arbitrary number of
+\fIdevice\-property\fR
+parameters can be specified\&. Again, see
+\fBamanda-devices\fR(7)
+for information on device properties\&.
+.SH "CHANGER SECTION"
+.PP
+Changers are described in
+\fBamanda\&.conf\fR
+in the form of "changer" sections, which look like this:
+.nf
+define changer \fIname\fR {
+ comment "\fIcomment (optional)\fR"
+ tpchanger "\fIchanger\-spec\fR"
+ changerdev "\fIdevice\-name\fR"
+ changerfile "\fIstate\-file\fR"
+ \&.\&.\&.
+}
+.fi
+.PP
+The { must appear at the end of a line, and the } on its own line\&.
+.PP
+\fIname\fR
+is the user\-specified name of this device\&. The remaining parameters are specific to the changer type selected\&.
+.PP
+See
+\fBamanda-changers\fR(7)
+for more information on configuring changers\&.
+.SH "INTERACTIVITY SECTION"
+.PP
+The
+\fBamanda\&.conf\fR
+file may define multiple interactivyt methods, although only one will be used \- that specified by the
+\fBinteractivity\fR
+parameter\&. The information is entered in a
+\fBinteractivity\fR
+section, which looks like this:
+.nf
+define interactivity \fIname\fR {
+ \fIinteractivity\-option\fR \fIinteractivity\-value\fR
+ \&.\&.\&.
+}
+.fi
+.PP
+The { must appear at the end of a line, and the } on its own line\&.
+.PP
+\fIname\fR
+is the user\-specified name of this interactivity\&. The remaining parameters are specific to the interactivity type selected\&.
+.PP
+The interactivity options and values are:
+.PP
+\fBcomment\fR \fIstring\fR
+.RS 4
+Default: not set\&. A comment string describing this interactivity\&.
+.RE
+.PP
+\fBplugin\fR \fIstring\fR
+.RS 4
+No default\&. Must be set to the name of the interactivity module, as described in
+\fBamanda-interactivity\fR(7)\&.
+.RE
+.PP
+\fBproperty\fR [\fBappend\fR] \fIstring\fR \fIstring\fR+
+.RS 4
+No default\&. You can set arbitrary properties for the interactivity\&. Each interactivity module has a different set of properties\&. The first string contains the name of the property to set, and the others contains its values\&. All strings should be quoted\&. The
+\fBappend\fR
+keyword appends the given values to an existing list of values for that property\&.
+.RE