amcleanup(8) [redhat man page]

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

NAME

       amcleanup - run the Amanda cleanup process after a failure

SYNOPSIS

       amcleanup config

DESCRIPTION

       Amcleanup  generates  the  Amanda  Mail Report and updates the Amanda databases after a system failure on a tape server host.  This cleanup
       process is normally done automatically as part of the amdump program, but if amdump cannot complete for some reason (usually because  of  a
       tape server host crash), amcleanup must be run some time later (usually during system boot).

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

EXAMPLES

       This example runs the Amanda cleanup process by hand after a failure.

	      % amcleanup DailySet1

       Putting	the following line in a system boot script (e.g. /etc/rc.local) runs the Amanda cleanup process as part of the reboot, eliminating
       the need to run it by hand.

	      /usr/sbin/amcleanup DailySet1

       If nothing needs to be done, amcleanup exits normally with the message:

	      amcleanup: no unprocessed logfile to clean up.

AUTHOR

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

SEE ALSO

       amanda(8), amdump(8)

																      AMCLEANUP(8)

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

NAME

       amdump - back up all disks in an Amanda configuration

SYNOPSIS

       amdump config [ host [ disk ]* ]*

DESCRIPTION

       Amdump  switches  to the appropriate Amanda configuration directory, e.g. /etc/amanda/config, then attempts to back up every disk specified
       by the amanda.conf file.  Amdump is normally run by cron.

       You can specify many host/disk expression, only disks that match an expression will be dumped. All disk are dumped  if  no  expression  are
       given.

       If file /etc/amanda/config/hold exists, 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.

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

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/sbin/amdump DailySet1

       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 ter-
	      minated.	If the problem is caused by the remains of a previous run, you must execute amcleanup(8) and then rerun amdump.

AUTHOR

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

SEE ALSO

       amanda(8), amcheck(8), amcleanup(8), amrestore(8), amflush(8), cron(8)

																	 AMDUMP(8)