3 .\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
8 .TH "AMADMIN" "8" "08/22/2008" "" ""
9 .\" disable hyphenation
11 .\" disable justification (adjust text to left margin only)
14 amadmin - administrative interface to control Amanda backups
17 \fBamadmin\fR \fIconfig\fR \fIcommand\fR [\fIcommand_options\fR...] [\fB\-o\ \fR\fIconfigoption\fR]...
21 performs various administrative tasks on the
28 man page for more details about
36 ] parameter pair operate on all disks in the
40 if no disks are specified\. Where
42 is also marked as being optional, the command operates on all hosts and disks in the
47 are special expressions; see the "HOST & DISK EXPRESSION" section of
51 Commands that take one or more
53 parameters operate on the set of dumps specified by all of the expressions\. See the "DUMP SPECIFICATIONS" section of
59 Show the current version and some compile time and runtime parameters\. The
61 parameter must be present but is ignored\.
64 \fBforce\-bump\fR [ \fIhostname\fR [ \fIdisks\fR ]* ]+
70 to bump to a new incremental level during the next
75 \fBforce\-no\-bump\fR [ \fIhostname\fR [ \fIdisks\fR ]* ]+
81 to not bump to a new incremental level during the next
86 \fBunforce\-bump\fR [ \fIhostname\fR [ \fIdisks\fR ]* ]+
95 \fBforce\fR [ \fIhostname\fR [ \fIdisks\fR ]* ]+
101 to do a full (level 0) backup during the next
106 \fBunforce\fR [ \fIhostname\fR [ \fIdisks\fR ]* ]+
113 \fBreuse\fR \fItapelabel\fR [ \.\.\. ]
115 The tapes listed will be available for reuse at their point in the tape cycle\.
118 \fBno\-reuse\fR \fItapelabel\fR [ \.\.\. ]
120 The tapes listed will not be reused when their turn comes up again in the tape cycle\. Note that if this causes the number of reusable tapes to drop below the
125 will request new tapes until the count is satisfied again\.
129 are available for recovery, marking them
131 is a security to be sure amanda will not overwrite them\.
134 \fBdue\fR [ \fIhostname\fR [ \fIdisks\fR ]* ]*
136 Show when the next full dump is due\.
139 \fBfind\fR [ \fB\-\-sort\fR \fIhkdlpb\fR ] [ \fIhostname\fR [ \fIdisks\fR ]* ]*
141 Display all backups currently on tape or in the holding disk\. The tape label or holding disk filename, file number, and status are displayed\.
145 option changes the sort order using the following flags:
151 \fIl\fR: backup level
156 An uppercase letter reverses the sort order for that key\. The default sort order is
160 \fBholding delete\fR \fIhostname\fR [ \fIdisk\fR [ \fIdatestamp\fR [ \.\. ] ] ]
162 Delete holding files matching the given specification\. At least a hostname must be provided\.
165 \fBholding list\fR [\-l] [\-d] [ \fIhostname\fR [ \fIdisk\fR [ \fIdatestamp\fR [ \.\. ] ] ] ]
167 List holding files matching the given specification, or all holding files if no specification is provided\. With \'\-l\', additional information (size, level, and whether the dump is outdated) is provided\. With \'\-d\', only outdated dumps are shown\.
169 An outdated holding file is one which is not required for a restore of the
171 dump\. Note that outdated dumps may still be required for restores at earlier dates\. For example, assume that a DLE had a level 0 on Monday, level 1\'s Tuesday through Thursday, and a level 2 on Friday\. Then the files required for a restore of Fridays (the most recent) dump are those from Monday (level 0), Thursday (level 1), and Friday (level 2)\. Tuesday and Wednesday\'s files are outdated\.
174 \fBdelete\fR [ \fIhostname\fR [ \fIdisks\fR ]* ]+
185 .nr an-no-space-flag 1
189 If you do not also remove the disk from the
193 will treat it as a new disk during the next run\.
200 expects to write to during the next run\. See also
206 Display the current bump threshold parameters, calculated for all backup levels\.
209 \fBbalance\fR [ \fB\-\-days\fR \fI<num>\fR ]
211 Display the distribution of full backups throughout the dump schedule\.
214 \fBexport\fR [ \fIhostname\fR [ \fIdisks\fR ]* ]*
216 Convert records from the
218 database to a text format that may be transmitted to another
227 \fBexport\fRed records read from standard input to a form
229 uses and insert them into the database on this machine\.
232 \fBdisklist\fR [ \fIhostname\fR [ \fIdisks\fR ]* ]*
236 information for each of the
240 (or all hosts)\. Mostly used for debugging\.
243 \fBinfo\fR [ \fIhostname\fR [ \fIdisks\fR ]* ]*
245 Display the database record for each of the
249 (or all hosts)\. Mostly used for debugging\.
252 \fB\-o\fR \fIconfigoption\fR
254 See the "\fBCONFIGURATION OVERRIDE\fR" section in
259 Request three specific file systems on
261 get a full level 0 backup during the next
265 $ amadmin daily force machine\-a / /var /usr
266 amadmin: machine\-a:/ is set to a forced level 0 tonight\.
267 amadmin: machine\-a:/var is set to a forced level 0 tonight\.
268 amadmin: machine\-a:/usr is set to a forced level 0 tonight\.
271 Request all file systems on
273 get a full level 0 backup during the next
277 $ amadmin daily force machine\-b
278 amadmin: machine\-b:/ is set to a forced level 0 tonight\.
279 amadmin: machine\-b:/var is set to a forced level 0 tonight\.
280 amadmin: machine\-b:/usr is set to a forced level 0 tonight\.
281 amadmin: machine\-b:/home is set to a forced level 0 tonight\.
289 \fImachine\-b\fR\. The other file systems will still get a full level 0 backup\.
291 $ amadmin daily unforce machine\-b /home
292 amadmin: force command for machine\-b:/home cleared\.
295 Locate backup images of
298 \fImachine\-c\fR\. The
300 column displays either a tape label or a filename depending on whether the image is on tape or is still in the holding disk\. If the image is on tape, the
302 column tells you which file on the tape has the image (file number zero is a tape label)\. This column shows zero and is not meaningful if the image is still in the holding disk\. The
304 column tells you whether the backup was successful or had some type of error\.
306 $ amadmin daily find machine\-c /var
307 date host disk lv tape or file file part status
308 2000\-11\-09 machine\-c /var 0 000110 9 \-\- OK
309 2000\-11\-08 machine\-c /var 2 000109 2 \-\- OK
310 2000\-11\-07 machine\-c /var 2 /amanda/20001107/machine\-c\._var\.2 0 OK
311 2000\-11\-06 machine\-c /var 2 000107 2 \-\- OK
312 2000\-11\-05 machine\-c /var 2 000106 3 \-\- OK
313 2000\-11\-04 machine\-c /var 2 000105 2 \-\- OK
314 2000\-11\-03 machine\-c /var 2 000104 2 \-\- OK
315 2000\-11\-02 machine\-c /var 2 000103 2 \-\- OK
316 2000\-11\-01 machine\-c /var 1 000102 5 \-\- OK
317 2000\-10\-31 machine\-c /var 1 000101 3 \-\- OK
323 \fImachine\-d\fR\. If you do not also remove the disk from the
327 will treat it as a new disk during the next run\.
329 $ amadmin daily delete machine\-d /workspace
330 amadmin: machine\-d:/workspace deleted from database\.
331 amadmin: NOTE: you\'ll have to remove these from the disklist yourself\.
336 will use (in this case,
340 The next \fIAmanda\fR run should go onto tape 123456 or a new tape\.
343 Show how well full backups are balanced across the dump cycle\. The
345 column is the day the backups are due for a full backup\.
347 shows the number of filesystems doing full backups that night, and
351 show the estimated total size of the backups before and after any compression, respectively\.
355 column shows how far off that night\'s backups are from the average size (shown at the bottom of the balance column)\.
357 tries to keep the backups within +/\- 5%, but since the amount of data on each filesystem is always changing, and
359 will never delay backups just to rebalance the schedule, it is common for the schedule to fluctuate by larger percentages\. In particular, in the case of a tape or backup failure, a bump will occur the following night, which will not be smoothed out until the next pass through the schedule\.
361 The last line also shows an estimate of how many
363 runs will be made between full backups for a file system\. In the example, a file system will probably have a full backup done every eight times
365 is run (e\.g\. every eight days)\.
367 $ amadmin daily balance
368 due\-date #fs orig KB out KB balance
369 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
370 11/10 Mon 21 930389 768753 +5\.1%
371 11/11 Tue 29 1236272 733211 +0\.2%
372 11/12 Wed 31 1552381 735796 +0\.6%
373 11/13 Thu 23 1368447 684552 \-6\.4%
374 11/14 Fri 32 1065603 758155 +3\.6%
375 11/15 Sat 14 1300535 738430 +0\.9%
376 11/16 Sun 31 1362696 740365 +1\.2%
377 11/17 Mon 30 1427936 773397 +5\.7%
378 11/18 Tue 11 1059191 721786 \-1\.3%
379 11/19 Wed 19 1108737 661867 \-9\.5%
380 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
381 TOTAL 241 12412187 7316312 731631 (estimated 8 runs per dumpcycle)
385 /usr/local/etc/amanda/\fIconfig\fR/amanda\.conf
392 Stefan G\. Weichinger,
393 <sgw@amanda\.org>, maintainer of the
394 \fIAmanda\fR\-documentation: XML\-conversion
401 \fBamfetchdump\fR(8),
402 : http://wiki.zmanda.com