amplot(8) [centos man page]
AMPLOT(8) System Administration Commands AMPLOT(8) NAME
amplot - visualize the behavior of Amanda SYNOPSIS
amplot [-b] [-c] [-e] [-g] [-l] [-p] [-t T] amdump_files DESCRIPTION
Amplot reads an amdump output file that Amanda generates each run (e.g. amdump.1) and translates the information into a picture format that may be used to determine how your installation is doing and if any parameters need to be changed. Amplot also prints out amdump lines that it either does not understand or knows to be warning or error lines and a summary of the start, end and total time for each backup image. Amplot is a shell script that executes an awk program (amplot.awk) to scan the amdump output file. It then executes a gnuplot program (amplot.g) to generate the graph. The awk program is written in an enhanced version of awk, such as GNU awk (gawk(1) version 2.15 or later) or nawk(1). During execution, amplot generates a few temporary files that gnuplot uses. These files are deleted at the end of execution. See the amanda(8) man page for more details about Amanda. OPTIONS
-b Generate b/w postscript file (need -p). -c Compress amdump_files after plotting. -e Extend the X (time) axis if needed. -g Direct gnuplot output directly to the X11 display (default). -p Direct postscript output to file YYYYMMDD.ps (opposite of -g). -l Generate landscape oriented output (needs -p). -t T Set the right edge of the plot to be T hours. The amdump_files may be in various compressed formats (compress, gzip, pact, compact). INTERPRETATION
The figure is divided into a number of regions. There are titles on the top that show important statistical information about the configuration and from this execution of amdump. In the figure, the X axis is time, with 0 being the moment amdump was started. The Y axis is divided into 5 regions: QUEUES: How many backups have not been started, how many are waiting on space in the holding disk and how many have been transferred successfully to tape. %BANDWIDTH: Percentage of allowed network bandwidth in use. HOLDING DISK: The higher line depicts space allocated on the holding disk to backups in progress and completed backups waiting to be written to tape. The lower line depicts the fraction of the holding disk containing completed backups waiting to be written to tape including the file currently being written to tape. The scale is percentage of the holding disk. TAPE: Tape drive usage. %DUMPERS: Percentage of active dumpers. The idle period at the left of the graph is time amdump is asking the machines how much data they are going to dump. This process can take a while if hosts are down or it takes them a long time to generate estimates. BUGS
Reports lines it does not recognize, mainly error cases but some are legitimate lines the program needs to be taught about. SEE ALSO
amanda(8), amdump(8), gnuplot(1), compress(1), gzip(1) The Amanda Wiki: : http://wiki.zmanda.com/ AUTHORS
Olafur Gudmundsson <ogud@tis.com> Trusted Information Systems Stefan G. Weichinger <sgw@amanda.org> Amanda 3.3.3 01/10/2013 AMPLOT(8)
Check Out this Related Man Page
AMANDA(8) System Administration Commands AMANDA(8) NAME
amanda - The Open Source Backup Platform DESCRIPTION
This manual page gives an overview of the Amanda commands and configuration files for quick reference. COMMANDS Here are all the Amanda commands. Each one has its own manual page. See them for all the gory details. o amaddclient(8), o amadmin(8), o amaespipe(8), o amarchiver(8), o amcheck(8), o amcheckdb(8), o amcheckdump(8), o amcleanup(8), o amcrypt-ossl-asym(8), o amcrypt-ossl(8), o amcrypt(8), o amcryptsimple(8), o amdevcheck(8), o amdump(8), o amfetchdump(8), o amflush(8), o amgetconf(8), o amgpgcrypt(8), o amgtar(8), o amlabel(8), o amoverview(8), o ampgsql(8), o amplot(8), o amraw(8), o amrecover(8), o amreport(8), o amrestore(8), o amrmtape(8), o amsamba(8), o amserverconfig(8), o amservice(8), o amstar(8), o amstatus(8), o amsuntar(8), o amtape(8), o amtapetype(8), o amtoc(8), o amvault(8), o amzfs-sendrecv(8), o amzfs-snapshot(8), o script-email(8), CONFIGURATION FILES o amanda.conf(5), o amanda-client.conf(5), o disklist(5), o tapelist(5), DATA FORMATS o amanda-archive-format(5), CONCEPTS o amanda-applications(7), o amanda-auth(7), o amanda-changers(7), o amanda-compatibility(7), o amanda-devices(7), o amanda-interactivity(7), o amanda-match(7), o amanda-scripts(7), o amanda-taperscan(7), CONFIGURATION FILES
There are four user-editable files that control the behavior of Amanda. The first two are amanda.conf(5) and amanda-client.conf(5), the main configuration files for the server and client, respectively. They contain parameters to customize Amanda for the site. Next is the disklist(5) file, which lists hosts and disk partitions to back up. Last is the seldom-edited tapelist(5) file, which lists tapes that are currently active. These files are described in more detail in the following sections. All configuration files are stored in individual configuration directories, usually under /etc/amanda/. A site will often have more than one configuration. For example, it might have a normal configuration for everyday backups and an archive configuration for infrequent full archival backups. The configuration files would be stored under directories /etc/amanda/normal/ and /etc/amanda/archive/, respectively. Part of the job of an Amanda administrator is to create, populate and maintain these directories. Most Amanda applications take a "config" parameter; this is generally the (unqualified) name of the configuration directory, e.g., normal. If the parameter is . (dot), the current directory is used. This feature is present for backward compatibility, but is not commonly used. Configuration Override Most commands allow the override of specific configuration options on the command line, using the -o option. This option has the form -oname=value. An optional space is allowed after the -o. Each configuration option should be specified in a separate command-line option. For global options, name is simply the name of the option, e.g., amdump -oruntapes=2 For options in a named section of the configuration, name has the form SECTION:section_name:name, where SECTION is one of TAPETYPE, DUMPTYPE, HOLDINGDISK, or INTERFACE, and section_name is the name of the tapetype, dumptype, holdingdisk, or interface. Examples: amdump -o TAPETYPE:HP-DAT:length=2000m amdump -o DUMPTYPE:no-compress:compress="server fast" amdump -o HOLDINGDISK:hd1:use="-100 mb" amdump -o INTERFACE:local:use="2000 kbps" When overriding device properties, one must carefully quote the command line to simulate the syntax of real configuration files. The following example should serve as a guide: amdump -o 'device-property="PROPERTY_MAX_VOLUME_USAGE" "100000"' Note that configuration overrides are not effective for tape changers, which supply a tapedev based on their own configuration. In order to override tapedev, you must also disable any changer: amdump -otapedev=/dev/nst1 -otpchanger='' AUTHORS
James da Silva <jds@amanda.org> Stefan G. Weichinger <sgw@amanda.org> Amanda 3.3.3 01/10/2013 AMANDA(8)