Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

amcleanup(8) [centos man page]

AMCLEANUP(8)						  System Administration Commands					      AMCLEANUP(8)

NAME
amcleanup - run the Amanda cleanup process after a failure SYNOPSIS
amcleanup [-k] [-p] [-r] [-v] 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). The amcleanupdisk program is run with the same [-r] and [-v] options. See the amanda(8) man page for more details about Amanda. OPTIONS
-k Kill all process listed in the log file are their child. if there is no log file, then kill all amdump and amflush process and their child. -p Do the cleanup only if all process listed in the log file are already terminated. -r Remove bad file in holding disk. This options is passed to amcleanupdisk. -v Generate verbose output. This options is passed to amcleanupdisk. EXAMPLES
This example runs the Amanda cleanup process by hand after a failure. % amcleanup daily 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/local/sbin/amcleanup daily If nothing needs to be done, amcleanup exits normally with the message: amcleanup: no unprocessed logfile to clean up. SEE ALSO
amanda(8), amdump(8) 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 AMCLEANUP(8)

Check Out this Related Man Page

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)
Man Page