Amanda log files: Difference between revisions

From wiki.zmanda.com
Jump to navigation Jump to search
(Reworked Log and Debug files on Backup client)
m (Fix broken links for Amanda log files)
 
(21 intermediate revisions by 5 users not shown)
Line 1: Line 1:
==Backup server==
Amanda produces several types of log files, with distinct purposes.
*  amdump.<run #> for each run for each amanda configuration. This log file is created in the same directory specified by the "logdir" parameter in the [[amanda.conf]] file.


This log file can be used for debugging an amdump run. This log file is read by [[amplot]] and [[amstatus]] command. amdump.1 contains the
* [[Amanda_log_files/Debug Logs|Debug Logs]] ({{file|{server,client}/''config''/''prog''.YYYYMMDDHHMMSS.debug}}) contain debugging messages that are useful for finding bugs in Amanda.
most recent run information.
* [[Amanda_log_files/Amdump Logs|Amdump Logs]] ({{file|amdump.N}} or {{file|amflush.N}}) contain a description of amdump's actions, parsed by amstatus. Amflush has a similar mechanism.
 
* [[Amanda_log_files/Trace Logs|Trace Logs]] ({{file|log.YYMMDDHHMMSS.N}} or {{file|log.YYYYMMDD.N}}) contain specially formatted log messages about a run which can later be read by other Amanda applications to find out what Amanda did during the run.
* log.<year><month><day>.<run #> for each run for each configuration. This log file is created in the directory specified by
* Syslog may also contain errors from ''inetd'' or ''xinetd'', or hardware errors indicating problems with hard drives, tape changers, tape drives, etc.
the "logdir" parameter in the [[amanda.conf]] file.
{{Languages}}
 
Run number is 0 for the most recent run. This log file is used for generating backup reports ([[amreport]]). Each line in the file begins with a keyword. Depending on the keyword, rest of the line is parsed. Backup statistics can obtained from the log file.
 
These log files are also used to locate the dumps on tapes with "amadmin xx find".
 
Do not delete these log files. Amanda takes care of the them when they are not needed anymore.
 
* System log (logged by syslogd utility). This log may contain errors regarding xinetd configuration. It can also contain device error
logs.
 
==Log and Debug Files on the Backup Client==
 
The different commands that run on the Amanda client (amandad, sendsize, runtar, rundump) create files with debugging information in the AMANDA_DBG directory.  This directory is defined at compile time and can be found with the [[amadmin]] command:
 
$ amadmin x version | grep DBG
AMANDA_DBG=/tmp/amanda
 
Usually the value is /tmp/amanda, but some distro's have it defined as /var/log/amanda.
This directory should be writeable by the dumpuser on the client. Amanda tries to create it if it does not exist.
 
The first part of the debug filename is the command name, followed by the date and time when the command was started, optionally followed by a sequence number, and ends in ".debug":
 
$ ls /tmp/amanda
amandad.20051207000402.debug
amandad.20051207000402000.debug
amandad.20051207004031.debug
amandad.20051207004713.debug
runtar.200512070004031.debug
runtar.200512070004713.debug
sendbackup.20051207004031.debug
sendbackup.20051207004713.debug
sendsize.20051207000402.debug
 
The [[amrecover]] command communicates with the programs amindexd on the Amanda index server and amidxtaped on the Amanda tape server (usually the same host), and both of these programs create a debug file in AMANDA_DBG on the Amanda server.
 
The Amanda server also trims the server Log files (see above) and index files, and these two utilities store their debug information on the server AMANDA_DBG directory: amtrmlog.''datetime''.debug and amtrmidx.''datetime''.log.
 
The debug files are removed automatically by Amanda after a few days, usually 4, a value defined at compile time:
 
$ amadmin x version | grep DAYS
AMANDA_DEBUG_DAYS=4
 
You may remove the files manually, especially handy when debugging a setup, and concentrating only on the debug files created in the last run.

Latest revision as of 18:16, 16 December 2023

Amanda produces several types of log files, with distinct purposes.

  • Debug Logs ({server,client}/config/prog.YYYYMMDDHHMMSS.debug) contain debugging messages that are useful for finding bugs in Amanda.
  • Amdump Logs (amdump.N or amflush.N) contain a description of amdump's actions, parsed by amstatus. Amflush has a similar mechanism.
  • Trace Logs (log.YYMMDDHHMMSS.N or log.YYYYMMDD.N) contain specially formatted log messages about a run which can later be read by other Amanda applications to find out what Amanda did during the run.
  • Syslog may also contain errors from inetd or xinetd, or hardware errors indicating problems with hard drives, tape changers, tape drives, etc.

Other languages: [[::Amanda log files|English]] {{#ifexist: {{#if: | | {{#if: | :}}Amanda log files}}/Fr |  • {{#if: |français| [[::Amanda log files/Fr|français]]}}|}}

{{#ifexist: {{#if: | | {{#if: | :}}Amanda log files}}/Zh-cn |  • {{#if: |中文（中国大陆）| [[::Amanda log files/Zh-cn|中文（中国大陆）]]}}|}}


Retrieved from ‘http://wiki.zmanda.com/index.php?title=Amanda_log_files&oldid=9015’