1 .\"Generated by db2man.xsl. Don't modify this, modify the source.
10 .de Sp \" Vertical space (when we can't use .PP)
16 .ie \\n(.$>=3 .ne \\$3
20 .TH "AMADMIN" 8 "" "" ""
22 amadmin - administrative interface to control Amanda backups
25 \fBamadmin\fR \fIconfig\fR \fIcommand\fR [\fIcommand\fRĀ \fIoptions\fR]
29 performs various administrative tasks on the
30 \fBconfig\fR\fBAmanda\fR
35 man page for more details about
43 ] parameter pair operate on all disks in the
47 if no disks are specified. Where
49 is also marked as being optional, the command operates on all hosts and disks in the
54 are special expressions, see the "HOST & DISK EXPRESSION" section of
59 Show the current version and some compile time and runtime parameters. The
61 parameter must be present but is ignored.
63 \fBforce-bump\fR [ \fBhostname\fR [ \fBdisks\fR ]* ]+
68 to bump to a new incremental level during the next
72 \fBforce-no-bump\fR [ \fBhostname\fR [ \fBdisks\fR ]* ]+
77 to not bump to a new incremental level during the next
81 \fBunforce-bump\fR [ \fBhostname\fR [ \fBdisks\fR ]* ]+
88 \fBforce\fR [ \fBhostname\fR [ \fBdisks\fR ]* ]+
93 to do a full (level 0) backup during the next
97 \fBunforce\fR [ \fBhostname\fR [ \fBdisks\fR ]* ]+
102 \fBreuse\fR \fBtapelabel\fR [ ... ]
103 The tapes listed will be available for reuse at their point in the tape cycle.
105 \fBno-reuse\fR \fBtapelabel\fR [ ... ]
106 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
107 \fBamanda.conf\fR\fBtapecycle\fR
110 will request new tapes until the count is satisfied again.
112 \fBdue\fR [ \fBhostname\fR [ \fBdisks\fR ]* ]*
113 Show when the next full dump is due.
115 \fBfind\fR [ \fB--sort\fR \fIhkdlpb\fR ]\fB\fR [ \fBhostname\fR [ \fBdisks\fR ]* ]*
116 Display all backups currently on tape or in the holding disk. The tape label or holding disk filename, file number, and status are displayed.
120 option changes the sort order using the following flags:
135 An uppercase letter reverses the sort order for that key. The default sort order is
138 \fBdelete\fR [ \fBhostname\fR [ \fBdisks\fR ]* ]+
148 .nr an-no-space-flag 1
152 If you do not also remove the disk from the
154 file, \fBAmanda\fR will treat it as a new disk during the next run..TP
158 expects to write to during the next run. See also
162 Display the current bump threshold parameters, calculated for all backup levels.
164 \fBbalance\fR [ \fB--days\fR \fI<num>\fR ]\fB\fR \fB\fR \fB\fR
165 Display the distribution of full backups throughout the dump schedule.
167 \fBexport\fR [ \fBhostname\fR [ \fBdisks\fR ]* ]*
168 Convert records from the
170 database to a text format that may be transmitted to another
177 \fBexport\fRed records read from standard input to a form
179 uses and insert them into the database on this machine.
181 \fBdisklist\fR [ \fBhostname\fR [ \fBdisks\fR ]* ]*
184 information for each of the
188 (or all hosts). Mostly used for debugging.
190 \fBinfo\fR [ \fBhostname\fR [ \fBdisks\fR ]* ]*
191 Display the database record for each of the
195 (or all hosts). Mostly used for debugging.
198 Request three specific file systems on
200 get a full level 0 backup during the next
205 $ amadmin daily force machine-a / /var /usr
206 amadmin: machine-a:/ is set to a forced level 0 tonight.
207 amadmin: machine-a:/var is set to a forced level 0 tonight.
208 amadmin: machine-a:/usr is set to a forced level 0 tonight.
211 Request all file systems on
213 get a full level 0 backup during the next
218 $ amadmin daily force machine-b
219 amadmin: machine-b:/ is set to a forced level 0 tonight.
220 amadmin: machine-b:/var is set to a forced level 0 tonight.
221 amadmin: machine-b:/usr is set to a forced level 0 tonight.
222 amadmin: machine-b:/home is set to a forced level 0 tonight.
230 \fBmachine-b\fR. The other file systems will still get a full level 0 backup.
233 $ amadmin daily unforce machine-b /home
234 amadmin: force command for machine-b:/home cleared.
237 Locate backup images of
242 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
244 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
246 column tells you whether the backup was successful or had some type of error.
249 $ amadmin daily find machine-c /var
250 date host disk lv tape or file file part status
251 2000\-11\-09 machine\-c /var 0 000110 9 -- OK
252 2000\-11\-08 machine\-c /var 2 000109 2 -- OK
253 2000\-11\-07 machine\-c /var 2 /amanda/20001107/machine-c._var.2 0 OK
254 2000\-11\-06 machine\-c /var 2 000107 2 -- OK
255 2000\-11\-05 machine\-c /var 2 000106 3 -- OK
256 2000\-11\-04 machine\-c /var 2 000105 2 -- OK
257 2000\-11\-03 machine\-c /var 2 000104 2 -- OK
258 2000\-11\-02 machine\-c /var 2 000103 2 -- OK
259 2000\-11\-01 machine\-c /var 1 000102 5 -- OK
260 2000\-10\-31 machine\-c /var 1 000101 3 -- OK
266 \fBmachine-d\fR. If you do not also remove the disk from the
270 will treat it as a new disk during the next run.
273 $ amadmin daily delete machine-d /workspace
274 amadmin: machine-d:/workspace deleted from database.
275 amadmin: NOTE: you'll have to remove these from the disklist yourself.
280 will use (in this case,
285 The next \fBAmanda\fR run should go onto tape 123456 or a new tape.
288 Show how well full backups are balanced across the dump cycle. The
290 column is the day the backups are due for a full backup.
292 shows the number of filesystems doing full backups that night, and
296 show the estimated total size of the backups before and after any compression, respectively.
300 column shows how far off that night's backups are from the average size (shown at the bottom of the balance column).
302 tries to keep the backups within +/- 5%, but since the amount of data on each filesystem is always changing, and
304 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.
306 The last line also shows an estimate of how many
308 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
310 is run (e.g. every eight days).
313 $ amadmin daily balance
314 due-date #fs orig KB out KB balance
315 -------------------------------------------
316 11/10 Mon 21 930389 768753 +5.1%
317 11/11 Tue 29 1236272 733211 +0.2%
318 11/12 Wed 31 1552381 735796 +0.6%
319 11/13 Thu 23 1368447 684552 -6.4%
320 11/14 Fri 32 1065603 758155 +3.6%
321 11/15 Sat 14 1300535 738430 +0.9%
322 11/16 Sun 31 1362696 740365 +1.2%
323 11/17 Mon 30 1427936 773397 +5.7%
324 11/18 Tue 11 1059191 721786 -1.3%
325 11/19 Wed 19 1108737 661867 -9.5%
326 -------------------------------------------
327 TOTAL 241 12412187 7316312 731631 (estimated 8 runs per dumpcycle)
331 /usr/local/etc/amanda/\fBconfig\fR/amanda.conf
338 Stefan G. Weichinger,
339 <sgw@amanda.org>, maintainer of the
340 \fBAmanda\fR-documentation: XML-conversion