3 Prev Chapter 36. The Amanda Manual Pages. Next
5 -------------------------------------------------------------------------------
9 amadmin
\14 administrative interface to control Amanda backups
13 amadmin config command [command_options...] [-oconfigoption]...
17 Amadmin performs various administrative tasks on the config Amanda
19 See the amanda(8) man page for more details about Amanda.
23 Commands that take a hostname [ disks ] parameter pair operate on all disks in
24 the disklist for that hostname if no disks are specified. Where hostname is
25 also marked as being optional, the command operates on all hosts and disks in
26 the disklist. Both hostname and disks are special expressions; see the "HOST &
27 DISK EXPRESSION" section of amanda(8) for a description.
28 Commands that take one or more dumpspec parameters operate on the set of dumps
29 specified by all of the expressions. See the "DUMP SPECIFICATIONS" section of
30 amanda(8) for a description.
34 Show the current version and some compile time and runtime parameters.
35 The config parameter must be present but is ignored.
37 force-bump [ hostname [ disks ]* ]+
38 Force the disks on hostname to bump to a new incremental level during the
41 force-no-bump [ hostname [ disks ]* ]+
42 Force the disks on hostname to not bump to a new incremental level during
45 unforce-bump [ hostname [ disks ]* ]+
46 Undo a previous force-bump or force-no-bump command.
48 force [ hostname [ disks ]* ]+
49 Force the disks on hostname to do a full (level 0) backup during the next
52 unforce [ hostname [ disks ]* ]+
53 Undo a previous force command.
55 reuse tapelabel [ ... ]
56 The tapes listed will be available for reuse at their point in the tape
59 no-reuse tapelabel [ ... ]
60 The tapes listed will not be reused when their turn comes up again in the
61 tape cycle. Note that if this causes the number of reusable tapes to drop
62 below the amanda.conf tapecycle value, Amanda will request new tapes
63 until the count is satisfied again.
65 due [ hostname [ disks ]* ]*
66 Show when the next full dump is due.
68 find [ --sort hkdlpb ] [ hostname [ disks ]* ]*
69 Display all backups currently on tape or in the holding disk. The tape
70 label or holding disk filename, file number, and status are displayed.
71 The --sort option changes the sort order using the following flags:
80 An uppercase letter reverses the sort order for that key. The default
83 holding delete hostname [ disk [ datestamp [ .. ] ] ]
84 Delete holding files matching the given specification. At least a
85 hostname must be provided.
87 holding list [-l] [ hostname [ disk [ datestamp [ .. ] ] ] ]
88 List holding files matching the given specification, or all holding files
89 if no specification is provided. With '-l', additional information (size
90 and level) is provided.
92 delete [ hostname [ disks ]* ]+
93 Delete the specified disks on hostname from the Amanda database.
97 If you do not also remove the disk from the disklist file, Amanda will
98 treat it as a new disk during the next run.
101 Display the tape(s) Amanda expects to write to during the next run. See
105 Display the current bump threshold parameters, calculated for all backup
108 balance [ --days <num> ]
109 Display the distribution of full backups throughout the dump schedule.
111 export [ hostname [ disks ]* ]*
112 Convert records from the Amanda database to a text format that may be
113 transmitted to another Amanda machine and imported.
116 Convert exported records read from standard input to a form Amanda uses
117 and insert them into the database on this machine.
119 disklist [ hostname [ disks ]* ]*
120 Display the disklist information for each of the disks on hostname (or
121 all hosts). Mostly used for debugging.
123 info [ hostname [ disks ]* ]*
124 Display the database record for each of the disks on hostname (or all
125 hosts). Mostly used for debugging.
128 See the "CONFIGURATION OVERRIDE" section in amanda(8).
133 Request three specific file systems on machine-a get a full level 0 backup
134 during the next Amanda run.
136 $ amadmin daily force machine-a / /var /usr
137 amadmin: machine-a:/ is set to a forced level 0 tonight.
138 amadmin: machine-a:/var is set to a forced level 0 tonight.
139 amadmin: machine-a:/usr is set to a forced level 0 tonight.
141 Request all file systems on machine-b get a full level 0 backup during the next
144 $ amadmin daily force machine-b
145 amadmin: machine-b:/ is set to a forced level 0 tonight.
146 amadmin: machine-b:/var is set to a forced level 0 tonight.
147 amadmin: machine-b:/usr is set to a forced level 0 tonight.
148 amadmin: machine-b:/home is set to a forced level 0 tonight.
150 Undo the previous force request for /home on machine-b. The other file systems
151 will still get a full level 0 backup.
153 $ amadmin daily unforce machine-b /home
154 amadmin: force command for machine-b:/home cleared.
156 Locate backup images of /var from machine-c. The tape or file column displays
157 either a tape label or a filename depending on whether the image is on tape or
158 is still in the holding disk. If the image is on tape, the file column tells
159 you which file on the tape has the image (file number zero is a tape label).
160 This column shows zero and is not meaningful if the image is still in the
161 holding disk. The status column tells you whether the backup was successful or
162 had some type of error.
164 $ amadmin daily find machine-c /var
165 date host disk lv tape or file file part status
166 2000-11-09 machine-c /var 0 000110 9 -- OK
167 2000-11-08 machine-c /var 2 000109 2 -- OK
168 2000-11-07 machine-c /var 2 /amanda/20001107/machine-c._var.2 0 OK
169 2000-11-06 machine-c /var 2 000107 2 -- OK
170 2000-11-05 machine-c /var 2 000106 3 -- OK
171 2000-11-04 machine-c /var 2 000105 2 -- OK
172 2000-11-03 machine-c /var 2 000104 2 -- OK
173 2000-11-02 machine-c /var 2 000103 2 -- OK
174 2000-11-01 machine-c /var 1 000102 5 -- OK
175 2000-10-31 machine-c /var 1 000101 3 -- OK
177 Forget about the /workspace disk on machine-d. If you do not also remove the
178 disk from the disklist file, Amanda will treat it as a new disk during the next
181 $ amadmin daily delete machine-d /workspace
182 amadmin: machine-d:/workspace deleted from database.
183 amadmin: NOTE: you'll have to remove these from the disklist yourself.
185 Find the next tape Amanda will use (in this case, 123456).
188 The next Amanda run should go onto tape 123456 or a new tape.
190 Show how well full backups are balanced across the dump cycle. The due-date
191 column is the day the backups are due for a full backup. #fs shows the number
192 of filesystems doing full backups that night, and orig KB and out KB show the
193 estimated total size of the backups before and after any compression,
195 The balance column shows how far off that night's backups are from the average
196 size (shown at the bottom of the balance column). Amanda tries to keep the
197 backups within +/- 5%, but since the amount of data on each filesystem is
198 always changing, and Amanda will never delay backups just to rebalance the
199 schedule, it is common for the schedule to fluctuate by larger percentages. In
200 particular, in the case of a tape or backup failure, a bump will occur the
201 following night, which will not be smoothed out until the next pass through the
203 The last line also shows an estimate of how many Amanda runs will be made
204 between full backups for a file system. In the example, a file system will
205 probably have a full backup done every eight times Amanda is run (e.g. every
208 $ amadmin daily balance
209 due-date #fs orig KB out KB balance
210 -------------------------------------------
211 11/10 Mon 21 930389 768753 +5.1%
212 11/11 Tue 29 1236272 733211 +0.2%
213 11/12 Wed 31 1552381 735796 +0.6%
214 11/13 Thu 23 1368447 684552 -6.4%
215 11/14 Fri 32 1065603 758155 +3.6%
216 11/15 Sat 14 1300535 738430 +0.9%
217 11/16 Sun 31 1362696 740365 +1.2%
218 11/17 Mon 30 1427936 773397 +5.7%
219 11/18 Tue 11 1059191 721786 -1.3%
220 11/19 Wed 19 1108737 661867 -9.5%
221 -------------------------------------------
222 TOTAL 241 12412187 7316312 731631 (estimated 8 runs per dumpcycle)
227 /usr/local/etc/amanda/config/amanda.conf
231 James da Silva, <jds@amanda.org> : Original text
232 Stefan G. Weichinger, <sgw@amanda.org>, maintainer of the Amanda-documentation:
237 amanda(8), amcheck(8), amdump(8), amrestore(8), amfetchdump(8)
238 -------------------------------------------------------------------------------
241 Chapter 36. The Amanda Manual Pages. Home amaespipe