1AMREPORT(8) System Administration Commands AMREPORT(8)
2
6 amreport - generate a formatted output of statistics for an Amanda run
7
9 amreport [-o configoption...] [(1) command-line options | (2) script
10 options] [config]
11 (1) [--log=logfile] [--ps=filename] [--text=filename] [--xml=filename]
13 [--print=printer] [--mail-text=recipient]
14 (2) [-i] [-M address] [-l logfile] [-f outputfile] [-p postscriptfile]
15 [--from-amdump]
16
18 Amreport generates a summary report of an Amanda backup run.
19 See the amanda(8) man page for more details about Amanda.
21
23 config
24 Name of the configuration to process. If no configuration name is
25 specified, amanda.conf is read from the current directory.
26 -o configoption
28 See the "CONFIGURATION OVERRIDE" section in amanda(8).
29 Amreport operates in two distinct modes. Command-line mode is intended
31 for use by an administrator from the command line, and uses long
32 command-line options for clarity. Script mode is intended for use from
33 scripts such as amdump, and has a lot of non-obvious default behaviors
34 to suit that need.
35 Unless a script-mode option is given, amreport defaults to command-line
37 mode. If no options are given, amreport writes a report for the most
38 recent logfile to stdout.
39 Command-Line Mode Options
41 --log=logfile
42 Use this logfile as the basis for the report. If this option is
43 given, then the report is a "historical" report and will not
44 include current state from e.g., holding disk and curinfo. If this
45 option is not specified, then the most recent logfile will be used.
46 --ps=filename
48 Write a postscript label to filename. See "LABEL PRINTING" below.
49 If filename is not specified, then the label is written to stdout.
50 --text=filename
52 Write a human-readable text report to filename. If filename is not
53 specified, then the report is written to stdout.
54 --xml=filename
56 Write an XML-formatted report to filename. If filename is not
57 specified, then the report is written to stdout.
58 --print=printer
60 Pipe a postscript label to lp or lpr, specifying the given printer.
61 If the printer is not specified, uses the default from the Amanda
62 configuration, or the system default printer.
63 --mail-text=recipient
65 Send a human-readable text report to the given recipient via the
66 mailer specified in the Amanda configuration. If the recipient is
67 not specified, this uses the mailto from the Amanda configuration.
68 Script Mode Options
70 -i
71 Don't email the report.
72 -M address
74 Mail the report to address instead of the mailto value from
75 amanda.conf.
76 -l logfile
78 Name of the log file to parse to generate the report. If a log file
79 is not specified, it defaults to the file $logdir/log, where
80 $logdir is the log directory defined in amanda.conf.
81 -f outputfile
83 Normally, amreport sends the report via e-mail to the mailto user
84 as defined in the amanda.conf file. If outputfile is specified,
85 then the report is put in outputfile.
86 -p postscriptfile
88 Send the postscript output to the file postscriptfile instead of to
89 the lpr(1) command. This option has an effect only if the lbl-templ
90 directive is specified in amanda.conf.
91 --from-amdump
93 Force script mode. Has no other effect.
94
96 Amanda's text report format is divided into several sections. Some of
97 these sections only appear if they are not empty.
98 Although newer versions of Amanda try to use the term "volume" to refer
100 to a unit of storage, amreport still uses the term "tape", even if
101 backups are done to non-tape devices, to allow scripts which parse
102 amreport's output to continue to function.
103 Summary
105 Hostname: bkserver
106 Org : DailySet1
107 Config : Daily
108 Date : February 25, 2009
109 These dumps were to tape Daily-103.
111 The next tape Amanda expects to use is: Daily-142
112 FAILURE DUMP SUMMARY:
114 jamon.slikon.local /var lev 0 FAILED [/bin/tar exited with status 2]
115 The summary section describes the run in broad terms, giving the server
117 hostname, organization (from the org configuration parameter),
118 configuration name, and dump date. This is followed by a description of
119 the volumes and holding disk used, and an rough estimate of the
120 volume(s) Amanda will use on the next run.
121 Brief notices of any unusual circumstances will also be included here.
123 Statistics
125 STATISTICS:
126 Total Full Incr.
127 -------- -------- --------
128 Estimate Time (hrs:min) 0:00
129 Run Time (hrs:min) 0:01
130 Dump Time (hrs:min) 0:00 0:00 0:00
131 Output Size (meg) 1.6 0.0 1.6
132 Original Size (meg) 1.6 0.0 1.6
133 Avg Compressed Size (%) 100.0 100.0 100.0 (level:#disks ...)
134 Filesystems Dumped 4 1 3 (1:3)
135 Avg Dump Rate (k/s) 1555.1 134.2 1787.3
136 Tape Time (hrs:min) 0:00 0:00 0:00
138 Tape Size (meg) 1.6 0.0 1.6
139 Tape Used (%) 5.5 0.1 5.4 (level:#disks ...)
140 Filesystems Taped 4 1 3 (1:3)
141 (level:#parts ...)
142 Parts Taped 4 1 3 (1:3)
143 Avg Tp Write Rate (k/s) 143966 27624.3 151811
144 USAGE BY TAPE:
146 Label Time Size % DLEs Parts
147 metals-013 0:00 1650k 5.4 4 4
148 This section contains aggregate statistics for the entire run. The
150 three columns break down the results into a total for all data handled,
151 only full dumps, and only incremental dumps. In the right margin,
152 amreport indicates the breakdown of dump levels at the dumper and the
153 taper.
154 The rows have the following meanings:
156 Estimate Time
158 The time used by the planner to estimate dump sizes.
159 Run Time
161 Total runtime, from the invocation of amdump to its completion.
162 Dump Time
164 Total time spent dumping clients.
165 Output Size
167 Total quantity of data dumped, after compression.
168 Original Size
170 Total quantity of data dumped, before compression.
171 Avg Compressed Size
173 Compression ratio, calculated from the previous two rows.
174 Filesystems Dumped
176 Number of DLEs dumped.
177 Avg Dump Rate
179 Average speed at which clients produced data. Note that, for dumps
180 done directly to a slow device, rather than to holding disk, this
181 rate may reflect a write speed constrained by the device speed.
182 Tape Time
184 Total time spent writing to storage volumes. This includes time
185 spent changing tapes, including time spent waiting for flush
186 thresholds to be met.
187 Tape Size
189 Total quantity of data written to storage volumes.
190 Tape Used
192 Fraction of the total allocated storage (tapetype length times
193 runtapes) actually used.
194 Filesystems Taped
196 Number of filesystems written to storage. This may be larger or
197 smaller than the number of filesystems dumped, due to flushes or
198 dumps left on holding disk.
199 Parts Taped
201 Number of split parts writtten to storage. If this number is very
202 large, then the split size may be too small.
203 Avg Tp Write Rate
205 Taper speed, based on the tape time and tape size, above. Note
206 that, because the tape time includes time spent on tasks other than
207 writing to tape, this does not necessary reflect the device's real
208 write speed. However, the value is useful for capacity planning, as
209 it reflects a realistic estimate of how quickly Amanda can write
210 data to storage.
211 Usage by Tape
213 USAGE BY TAPE:
214 Label Time Size % DLEs Parts
215 Conf-001 0:00 20320k 66.2 1 4
216 Conf-002 0:00 6470k 21.1 0 2
217 This short section gives per-volume statistics: time spent writing to
219 the volume; bytes written to the volume; portion of the expected tape
220 length used; number of DLEs started, and total number of split parts
221 written.
222 Notes
224 NOTES:
225 taper: tape DAILY-37 kb 30720 fm 3 [OK]
226 This section contains any informational log messages from the run. Most
228 messages are self-explanatory. The taper message shown in the example
229 is always present, and is redundant to the previous section. It
230 indicates that 30720 kb were written to "DAILY-37" in 3 files.
231 Failure and Strange Details
233 FAILED DUMP DETAILS:
234 /-- jamon.slikon.local /var lev 0 FAILED [/bin/tar exited with status 2]
236 sendbackup: info BACKUP=APPLICATION
237 sendbackup: info APPLICATION=amgtar
238 sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |amgtar -f... -
239 sendbackup: info COMPRESS_SUFFIX=.gz
240 sendbackup: info end
241 ? /bin/tar: ./gdm: Cannot savedir: Permission denied
242 | Total bytes written: 943831040 (901MiB, 4.9MiB/s)
243 | /bin/tar: Error exit delayed from previous errors
244 sendbackup: error [/bin/tar exited with status 2]
245 sendbackup: size 921710
246 sendbackup: end
247 \\--------
248 STRANGE DUMP DETAILS:
250 /-- bsdfw.slikon.local / lev 0 STRANGE
252 sendbackup: info BACKUP=APPLICATION
253 sendbackup: info APPLICATION=amgtar
254 sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |amgtar -f... -
255 sendbackup: info COMPRESS_SUFFIX=.gz
256 sendbackup: info end
257 | /bin/tar: ./tmp/.X11-unix/X0: socket ignored
258 | Total bytes written: 5530869760 (5.2GiB, 3.0MiB/s)
259 sendbackup: size 5401240
260 sendbackup: end
261 \\--------
262 This section expands on failures and strange results indicated in
264 earlier sections. In both cases, the details contain a messages
265 produced by the underlying backup tool - GNU tar, in this example.
266 Failed dumps have actually failed, and the reasons are usually clear.
267 Strange dumps, however, are regarded as successful by Amanda, but
268 contain messages that Amanda did not recognize and which may be of
269 interest to the operator.
270 Dump Summary
272 DUMP SUMMARY:
273 DUMPER STATS TAPER STATS
274 HOSTNAME DISK L ORIG-kB OUT-kB COMP% MMM:SS KB/s MMM:SS KB/s
275 -------------------------- ------------------------------------- ---------------
276 strontium /etc 1 270 270 -- 0:00 1146.3 0:00 140918.6
277 strontium -me/elantra 1 10 10 -- 0:00 65.6 0:00 9033.4
278 strontium /local 0 20 20 -- 0:00 133.9 0:00 27624.3
279 strontium -ository_13 1 1350 1350 -- 0:01 2568.5 0:00 175006.5
280 The dump summary table has one row for each DLE processed during the
282 run. The "L" column gives the level of the dump. The remaining colums
283 are divided into dumper stats and taper stats.
284 The dumper stats give the original (before compression) and output
286 (after compression) size of each dump, as well as a compression ratio,
287 if applicable. The column labeled "MMM:SS" gives the time spent on that
288 dump, and the next column is the calculated dump rate.
289 The taper stats give the time and speed with which the dump was written
291 to storage. This value is the sum of the times for each part, and as
292 such does not include time spent switching volumes.
293
295 Amanda can print postscript labels describing the contents of tape(s)
296 written in a run. The labels are designed to be folded and inserted
297 into the tape case along with the tape or hole punched and put in a
298 3-ring binder. Various label templates are provided to format data for
299 different tape sizes.
300 The information printed varies slightly between label templates due to
302 size constraints. Labels contain one line for each host/file-system
303 pair and may also contain the file number on the tape, the level of the
304 dump, the original size of the dump and the size of the (possibly
305 compressed) tape file.
306 Add the lbl-templ parameter to the tapetype definition in amanda.conf
308 to enable labels. If you don't add this line to your tapetype
309 definition, amreport will not print tape labels.
310 You may use the printer keyword in amanda.conf to print to other than
312 the system default printer.
313
315 Amanda provides label templates for the following tape types. These are
316 pretty generic labels and should be easy to customize for other tape
317 types or particular site needs.
318 * ExaByte 8mm tapes
320 * DAT 4mm tapes
321 * DLT tapes
322 * 3-ring binder
323 The 3-ring binder type is the most generic. It may be used to make a
325 hardcopy log of the tapes.
326
328 The exit code of amreport is the ORed value of:
329 0 = success
330 1 = error
331 2 = a dle give strange message
332 4 = a dle failed
333 8 = Don't know the status of a dle (RESULT_MISSING in the report)
334 16 = tape error or no more tape
335
337 amanda(8), amflush(8)
338 The Amanda Wiki: : http://wiki.zmanda.com/
340
342 Stefan G. Weichinger <sgw@amanda.org>
343Amanda 3.3.3 01/10/2013 AMREPORT(8)