Name of the configuration to process. If no configuration
name is specified, amanda.conf is read from the current directory.

-o configoption

See the "CONFIGURATION OVERRIDE" section in
amanda(8).

Amreport operates in two distinct modes. Command-line mode is
intended for use by an administrator from the command line, and uses long
command-line options for clarity. Script mode is intended for use from
scripts such as amdump, and has a lot of non-obvious default behaviors to
suit that need.

Unless a script-mode option is given, amreport defaults to
command-line mode. If no options are given, amreport writes a report for the
most recent logfile to stdout.

Use this logfile as the basis for the report. If this
option is given, then the report is a "historical" report and will
not include current state from e.g., holding disk and curinfo. If this option
is not specified, then the most recent logfile will be used.

--format=MODULE:DEST,DEST-ARG

Use the given perl module to format the report and send
it to DEST with the given DEST-ARG.

Amanda's text report format is divided into several sections. Some of these
sections only appear if they are not empty.

Although newer versions of Amanda try to use the term
"volume" to refer to a unit of storage, amreport still uses the
term "tape", even if backups are done to non-tape devices, to
allow scripts which parse amreport's output to continue to function.

The summary section describes the run in broad terms, giving the
server hostname, organization (from the org configuration parameter),
configuration name, and dump date. This is followed by a description of the
volumes and holding disk used, and an rough estimate of the volume(s) Amanda
will use on the next run.

Brief notices of any unusual circumstances will also be included
here.

This section contains aggregate statistics for the entire run. The
three columns break down the results into a total for all data handled, only
full dumps, and only incremental dumps. In the right margin, amreport
indicates the breakdown of dump levels at the dumper and the taper.

The rows have the following meanings:

Estimate Time

The time used by the planner to estimate dump
sizes.

Run Time

Total runtime, from the invocation of amdump to its
completion.

Dump Time

Total time spent dumping clients.

Output Size

Total quantity of data dumped, after compression.

Original Size

Total quantity of data dumped, before compression.

Avg Compressed Size

Compression ratio, calculated from the previous two
rows.

Filesystems Dumped

Number of DLEs dumped.

Avg Dump Rate

Average speed at which clients produced data. Note that,
for dumps done directly to a slow device, rather than to holding disk, this
rate may reflect a write speed constrained by the device speed.

Tape Time

Total time spent writing to storage volumes. This
includes time spent changing tapes, including time spent waiting for flush
thresholds to be met.

Tape Size

Total quantity of data written to storage volumes.

Tape Used

Fraction of the total allocated storage (tapetype length
times runtapes) actually used.

Filesystems Taped

Number of filesystems written to storage. This may be
larger or smaller than the number of filesystems dumped, due to flushes or
dumps left on holding disk.

Parts Taped

Number of split parts writtten to storage. If this number
is very large, then the split size may be too small.

Avg Tp Write Rate

Taper speed, based on the tape time and tape size, above.
Note that, because the tape time includes time spent on tasks other than
writing to tape, this does not necessary reflect the device's real write
speed. However, the value is useful for capacity planning, as it reflects a
realistic estimate of how quickly Amanda can write data to storage.

This short section gives per-volume statistics: time spent writing
to the volume; bytes written to the volume; portion of the expected tape
length used; number of DLEs started, and total number of split parts
written.

This section contains any informational log messages from the run.
Most messages are self-explanatory. The taper message shown in the example
is always present, and is redundant to the previous section. It indicates
that 30720 kb were written to "DAILY-37" in 3 files.

This section expands on failures and strange results indicated in
earlier sections. In both cases, the details contain a messages produced by
the underlying backup tool - GNU tar, in this example. Failed dumps have
actually failed, and the reasons are usually clear. Strange dumps, however,
are regarded as successful by Amanda, but contain messages that Amanda did
not recognize and which may be of interest to the operator.

The dump summary table has one row for each DLE processed during
the run. The "L" column gives the level of the dump. The remaining
colums are divided into dumper stats and taper stats.

The dumper stats give the original (before compression) and output
(after compression) size of each dump, as well as a compression ratio, if
applicable. The column labeled "MMM:SS" gives the time spent on
that dump, and the next column is the calculated dump rate.

The taper stats give the time and speed with which the dump was
written to storage. This value is the sum of the times for each part, and as
such does not include time spent switching volumes.

Amanda can print postscript labels describing the contents of tape(s) written in
a run. The labels are designed to be folded and inserted into the tape case
along with the tape or hole punched and put in a 3-ring binder. Various label
templates are provided to format data for different tape sizes.

The information printed varies slightly between label templates
due to size constraints. Labels contain one line for each host/file-system
pair and may also contain the file number on the tape, the level of the
dump, the original size of the dump and the size of the (possibly
compressed) tape file.

Add the lbl-templ parameter to the tapetype definition in
amanda.conf to enable labels. If you don't add this line to your tapetype
definition, amreport will not print tape labels.

You may use the printer keyword in amanda.conf to print to
other than the system default printer.