Visit The New, Modern Unix Linux Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #7
Difficulty: Easy
Linux was invented by Linux Torvalds.
True or False?
Linux & Unix Commands - Search Man Pages

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

AMFLUSH(8)						  System Administration Commands						AMFLUSH(8)

NAME
amflush - flush Amanda backup files from holding disk to tape SYNOPSIS
amflush [-b] [-f] [-s] [-D datestamp] [-o configoption...] config [host [disk...]...] DESCRIPTION
Amflush writes Amanda backups from the holding disks to tape, and updates the Amanda info database and tapelist(5) accordingly. It is similar to amdump, but does not perform any backup operations on Amanda clients. Backups may stay in a holding disk when something is wrong with the tape at the time amdump is run. When this happens, the problem must be corrected and amflush run by hand. The command optionally takes a set of DLE specifications (see amanda-match(7)) to narrow the DLEs for which dumps will be flushed. All dumps in holding are flushed if no expressions are given. OPTIONS
-b Run amflush in batch mode. All datestamps are selected unless specified. The flush is started without confirmation. -f Run amflush in foreground. Amflush normally detaches itself from the tty and runs as a background process. With the -f option, amflush stays in the foreground. This is useful if amflush is run as part of another script that, for example, advances the tape after the flush is completed. -s Write log to stdout/stderr instead of the amflush log file. Requires the -f option. -D datestamp specify a datestamp expression you want to flush; see amanda-match(7) for details on the format of this expression. -D 20001225-7 will flush all dumps from 25 december 2000 to 27 december 2000. host [disk]* Specify the host and disk on which the command will work -- see the description of DLE specifications in amanda-match(7). -o configoption See the "CONFIGURATION OVERRIDE" section in amanda(8). You can specify many host/disk expressions, only disks that match an expression will be flushed. All disks are flushed if no expressions are given. see the "HOST & DISK EXPRESSION" section of amanda(8) for a description. Amflush will look in the holding disks specified by the amanda.conf file in /usr/local/etc/amanda/config for any non-empty Amanda work directories. It then prompts you to select a directory or to process all of the directories. The work directories in the holding disks are named by the date at the time amdump was run, e.g. 19910215. See the amanda(8) man page for more details about Amanda. EXAMPLE
Amflush will search for holding areas associated with the daily configuration. After you select which holding area to flush, amflush writes the data to tape, updates the databases and sends a mail report similar to amdump(8). % amflush MyConfig Scanning /amanda-hold... 20001113: found Amanda directory. 20001114: found Amanda directory. Multiple Amanda directories, please pick one by letter: A. 20001113 B. 20001114 Select directories to flush [A..B]: [ALL] all Flushing dumps in 20001113, 20001114, today: 20001117 to tape drive /dev/rmt/0mn. Expecting tape DMP014 or a new tape. (The last dumps were to tape DMP013) Are you sure you want to do this? yes Running in background, you can log off now. You'll get mail when amflush is finished. The following example causes amflush to flush everything to tape, then ejects tape, using 'at' to run the task in the background. % echo 'amflush -b -f MyConfig && mt offline' | at now EXIT CODE
The exit code of amflush is the ORed value of: 0 = success 1 = error 4 = a dle failed 8 = Don't know the status of a dle (RESULT_MISSING in the report) 16 = tape error or no more tape SEE ALSO
amanda(8), amdump(8), amanda-match(7) The Amanda Wiki: : http://wiki.zmanda.com/ AUTHORS
James da Silva <jds@amanda.org> Stefan G. Weichinger <sgw@amanda.org> Amanda 3.3.1 02/21/2012 AMFLUSH(8)

Featured Tech Videos