11 \fB\\$1\fP \\$2 \fI\\$3\fP \\$4 \fI\\$5\fP \\$6 \\$7
14 \fB\\$1\fP \fI\\$2\fP \\$3 \\$4 \\$5
17 \fB\\$1\fP \\$2 \fI\\$3\fP \\$4 \fI\\$5\fP \\$6 \\$7
21 amadmin \- administrative interface to control Amanda backups
31 performs various administrative tasks on the
37 man page for more details about Amanda.
44 parameter pair operate on all disks in the
48 if no disks are specified.
51 is also marked as being optional,
52 the command operates on all hosts and disks in the
58 are special expression, see the "HOST & DISK EXPRESSION" section
65 Show the current version and some compile time and runtime parameters.
68 parameter must be present but is ignored.
70 .P1 force-bump [ hostname [ disks ]* ]+
75 to bump to a new incremental level during the next Amanda run.
77 .P1 force-no-bump [ hostname [ disks ]* ]+
82 to not bump to a new incremental level during the next Amanda run.
84 .P1 unforce-bump [ hostname [ disks ]* ]+
91 .P1 force [ hostname [ disks ]* ]+
96 to do a full (level 0) backup during the next Amanda run.
98 .P1 unforce [ hostname [ disks ]* ]+
103 .P2 reuse tapelabel [ ... ]
105 will be available for reuse at their point in the tape cycle.
107 .P2 no-reuse tapelabel [ ... ]
109 will not be reused when their turn comes up again in the tape cycle.
110 Note that if this causes the number of reusable tapes to drop below the
113 value, Amanda will request new tapes until the count is satisfied again.
115 .P1 due [ hostname [ disks ]* ]*
116 Show when the next full dump is due.
118 .P3 "find\fP [ \fB--sort\fP \fBhkdlb\fP ]\fB" [ hostname [ disks ]* ]*
119 Display all backups currently on tape or in the holding disk.
120 The tape label or holding disk filename,
122 and status are displayed.
126 option changes the sort order using the following flags:
140 An uppercase letter reverses the sort order for that key.
141 The default sort order is
144 .P1 delete [ hostname [ disks ]* ]+
152 Note: if you do not also remove the disk from the
154 file, Amanda will treat it as a new disk during the next run.
157 Display the tape(s) Amanda expects to write to during the next run.
162 Display the current bump threshold parameters, calculated for all backup
165 .P3 "balance\fP [ \fB--days\fP \fB<num>\fP ]\fB"
166 Display the distribution of full backups throughout the dump schedule.
168 .P1 export [ hostname [ disks ]* ]*
169 Convert records from the Amanda database
170 to a text format that may be transmitted to another Amanda
177 records read from standard input to a form Amanda uses
178 and insert them into the database on this machine.
180 .P1 disklist [ hostname [ disks ]* ]*
183 information for each of the
188 Mostly used for debugging.
190 .P1 info [ hostname [ disks ]* ]*
192 database record for each of the
197 Mostly used for debugging.
199 Request three specific file systems on
201 get a full level 0 backup during the next Amanda run.
205 $ amadmin @DEFAULT_CONFIG@ 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.
212 Request all file systems on
214 get a full level 0 backup during the next Amanda run.
219 $ amadmin @DEFAULT_CONFIG@ force machine-b
220 amadmin: machine-b:/ is set to a forced level 0 tonight.
221 amadmin: machine-b:/var is set to a forced level 0 tonight.
222 amadmin: machine-b:/usr is set to a forced level 0 tonight.
223 amadmin: machine-b:/home is set to a forced level 0 tonight.
233 The other file systems will still get a full level 0 backup.
237 $ amadmin @DEFAULT_CONFIG@ unforce machine-b /home
238 amadmin: force command for machine-b:/home cleared.
242 Locate backup images of
248 column displays either a tape label or a filename depending on whether
249 the image is on tape or is still in the holding disk.
250 If the image is on tape, the
252 column tells you which file on the tape has the image
253 (file number zero is a tape label).
254 This column shows zero and is not meaningful if the image
255 is still in the holding disk.
258 column tells you whether the backup was successful or had
263 $ amadmin @DEFAULT_CONFIG@ find machine-c /var
264 date host disk lv tape or file file status
265 2000-11-09 machine-c /var 0 000110 9 OK
266 2000-11-08 machine-c /var 2 000109 2 OK
267 2000-11-07 machine-c /var 2 /amanda/20001107/machine-c._var.2 0 OK
268 2000-11-06 machine-c /var 2 000107 2 OK
269 2000-11-05 machine-c /var 2 000106 3 OK
270 2000-11-04 machine-c /var 2 000105 2 OK
271 2000-11-03 machine-c /var 2 000104 2 OK
272 2000-11-02 machine-c /var 2 000103 2 OK
273 2000-11-01 machine-c /var 1 000102 5 OK
274 2000-10-31 machine-c /var 1 000101 3 OK
282 If you do not also remove the disk from the
284 file, Amanda will treat it as a new disk during the next run.
288 $ amadmin @DEFAULT_CONFIG@ delete machine-d /workspace
289 amadmin: machine-d:/workspace deleted from database.
290 amadmin: NOTE: you'll have to remove these from the disklist yourself.
294 Find the next tape Amanda will use
300 $ amadmin @DEFAULT_CONFIG@ tape
301 The next Amanda run should go onto tape 123456 or a new tape.
305 Show how well full backups are balanced across the dump cycle.
308 column is the day the backups are due for a full backup.
310 shows the number of filesystems doing full backups that night, and
314 show the estimated total size of the backups
315 before and after any compression, respectively.
319 column shows how far off that night's backups are from the average size
320 (shown at the bottom of the balance column).
321 Amanda tries to keep the backups within +/- 5%,
322 but since the amount of data on each filesystem is always changing,
323 and Amanda will never delay backups just to rebalance the schedule,
324 it is common for the schedule to fluctuate by larger percentages.
326 in the case of a tape or backup failure,
327 a bump will occur the following night,
328 which will not be smoothed out until the next pass through the schedule.
330 The last line also shows an estimate of how many Amanda runs will be
331 made between full backups for a file system.
332 In the example, a file system will probably have a full backup done
333 every eight times Amanda is run (e.g. every eight days).
337 $ amadmin @DEFAULT_CONFIG@ balance
338 due-date #fs orig KB out KB balance
339 -------------------------------------------
340 11/10 Mon 21 930389 768753 +5.1%
341 11/11 Tue 29 1236272 733211 +0.2%
342 11/12 Wed 31 1552381 735796 +0.6%
343 11/13 Thu 23 1368447 684552 -6.4%
344 11/14 Fri 32 1065603 758155 +3.6%
345 11/15 Sat 14 1300535 738430 +0.9%
346 11/16 Sun 31 1362696 740365 +1.2%
347 11/17 Mon 30 1427936 773397 +5.7%
348 11/18 Tue 11 1059191 721786 -1.3%
349 11/19 Wed 19 1108737 661867 -9.5%
350 -------------------------------------------
351 TOTAL 241 12412187 7316312 731631 (estimated 8 runs per dumpcycle)
354 @CONFIG_DIR@/\fIconfig\fP/amanda.conf
356 James da Silva <jds@cs.umd.edu>
358 University of Maryland, College Park