amflush(8) [redhat man page]

AMFLUSH(8)						      System Manager's Manual							AMFLUSH(8)

NAME

       amflush - flush Amanda backup files from holding disk to tape

SYNOPSIS

       amflush [ -f ] [ -D datestamp ]* config [ host [ disk ]* ]*

DESCRIPTION

       Amflush	writes Amanda backups from the holding disks to tape, and updates the Amanda info database and tape list accordingly.  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.

       -D  datestamp specify a	datestamp expression you want to flush, see the "DATASTAMP EXPRESSION" section of amanda(8) for a description.	-D
       20001225-7 will flush all dump from 25 december 2000 to 27 december 2000.

       You can specify many host/disk expressions, only disks that match an expression will be flushed. All disk are flushed if no expression  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 /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.

       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.

       See the amanda(8) man page for more details about Amanda.

EXAMPLE

       Amflush will search for holding areas associated with the PUCC 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 DailySet1
	      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.

AUTHOR

       James da Silva <jds@cs.umd.edu>
       University of Maryland, College Park

SEE ALSO

       amanda(8), amdump(8)

																	AMFLUSH(8)

AMDUMP(8)						  System Administration Commands						 AMDUMP(8)

NAME

       amdump - back up all disks in an Amanda configuration

SYNOPSIS

       amdump [--no-taper] [--exact-match] [-o configoption...] config [host [disk...]...]

DESCRIPTION

       Amdump is the main interface to the Amanda backup process. It loads the specified configuration and attempts to back up every disk
       specified by the disklist(5).  Amdump is normally run by cron.

       The command optionally takes a set of DLE specifications (see amanda-match(7)) to narrow the DLEs that will be dumped. All disks are dumped
       if no expressions are given.

       If a file named hold exists in the configuration directory, amdump will wait until it is removed before starting the backups. This allows
       scheduled backups to be delayed when circumstances warrant, for example, if the tape device is being used for some other purpose. While
       waiting, amdump checks for the hold file every minute.

       In some cases it is desirable to dump all Amanda clients to holding disk without writing anything to storage media. The --no-taper option
       instructs Amanda to not start the taper, and thus enter degraded mode immediately.

       See the amanda(8) man page for more details about Amanda.

OPTIONS

       host [disk]*
	   Specify the host and disk on which the command will work -- see the description of DLE specifications in amanda-match(7).

       --exact-match
	   The host and disk are parsed as exact values

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

EXAMPLE

       Here is a typical crontab entry. It runs amdump every weeknight at 1 a.m. as user bin:
       0 1 * * 1-5 bin /usr/local/sbin/amdump daily

       Please see the crontab(5) or crontab(1) manual page for the correct crontab format for your system.

MESSAGES

       amdump: waiting for hold file to be removed
	   The "hold" file exists and amdump is waiting for it to be removed before starting backups.

       amdump: amdump or amflush is already running, or you must run amcleanup
	   Amdump detected another amdump or amflush running, or the remains of a previous incomplete amdump or amflush run. This run is
	   terminated. If the problem is caused by the remains of a previous run, you must execute amcleanup(8) and then rerun amdump.

EXIT CODE

       The exit code of amdump is the ORed value of:
	0  = success
	1  = error
	2  = a dle give strange message
	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), amcheck(8), amcleanup(8), amrestore(8), amflush(8), cron(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.3							    01/10/2013								 AMDUMP(8)