1AMADMIN(8) System Administration Commands AMADMIN(8)
2
6 amadmin - administrative interface to control Amanda backups
7
9 amadmin [--version] [--no-default] [--print-source] [--exact-match]
10 [-o configoption...] config command [command_options...]
11
13 Amadmin performs various administrative tasks on the config Amanda
14 configuration.
15 See the amanda(8) man page for more details about Amanda.
17
19 --version
20 Print the version and exit.
21 --no-default
23 Do not print default values for config and disklist commands.
24 --print-source
26 Print where a value is defined for config and disklist commands.
27 --exact-match
29 The host and disk are parsed as exact values
30
32 Commands that take a hostname [ disks ] parameter pair operate on all
33 disks in the disklist(5) for that hostname if no disks are specified.
34 Where hostname is also marked as being optional, the command operates
35 on all hosts and disks in the disklist(5) when no hostname is given.
36 Both hostname and disks are match expressions; see amanda-match(7) for
37 a description.
38 version
40 Show the current version and some compile time and runtime
41 parameters. The config parameter must be present but is ignored.
42 estimate [ hostname [ disks ]* ]*
44 Print the server estimate for the dles, each output lines have the
45 following format:
46 hostname diskname level size
47 hostname
49 The quoted hostname
50 diskname
52 The quoted diskname
53 level
55 The level of the estimate
56 size
58 The estimate size in kbytes
59 force-bump [ hostname [ disks ]* ]+
61 Force the disks on hostname to bump to a new incremental level
62 during the next Amanda run.
63 force-no-bump [ hostname [ disks ]* ]+
65 Force the disks on hostname to not bump to a new incremental level
66 during the next Amanda run.
67 unforce-bump [ hostname [ disks ]* ]+
69 Undo a previous force-bump or force-no-bump command.
70 force [ hostname [ disks ]* ]+
72 Force the disks on hostname to do a full (level 0) backup during
73 the next Amanda run.
74 force-level-1 [ hostname [ disks ]* ]+
76 Force the disks on hostname to do a level 1 backup during the next
77 Amanda run.
78 unforce [ hostname [ disks ]* ]+
80 Undo a previous force or force-level-1 command.
81 retention [ tapelabel ... ]
83 Print the retention for each tapes.
84 reuse tapelabel [ ... ]
86 The tapes listed will be available for reuse at their point in the
87 tape cycle.
88 no-reuse tapelabel [ ... ]
90 The tapes listed will not be reused when their turn comes up again
91 in the tape cycle. Note that if this causes the number of reusable
92 tapes to drop below the amanda.conf tapecycle value, Amanda will
93 request new tapes until the count is satisfied again.
94 Tape marked no-reuse are available for recovery, marking them
96 no-reuse is a security to be sure amanda will not overwrite them.
97 due [ hostname [ disks ]* ]*
99 Show when the next full dump is due.
100 find [ --sort hkdlspbfw ] [ hostname [ disks ]* ]*
102 Display all backups currently on tape or in the holding disk. The
103 storage name, tape label or holding disk filename, file number, and
104 status are displayed.
105 The --sort option changes the sort order using the following flags:
107 h: host name
109 k: disk name
110 d: dump timestamp
111 l: backup level
112 p: dump part
113 b: tape label
114 s: storage name
115 f: filenum on tape
116 w: write timestamp
117 An uppercase letter reverses the sort order for that key. The
119 default sort order is hkdlspbfw.
120 holding delete hostname [ disk [ datestamp [ .. ] ] ]
122 Delete holding files matching the given specification. At least a
123 hostname must be provided.
124 holding list [-l] [-d] [ hostname [ disk [ datestamp [ .. ] ] ] ]
126 List holding files matching the given dump specification, or all
127 holding files if no specification is provided. See amanda-match(7)
128 for more information on dump specifications. With '-l', additional
129 information (size, level, and whether the dump is outdated) is
130 provided. With '-d', only outdated dumps are shown.
131 An outdated holding file is one which is not required for a restore
133 of the most recent dump. Note that outdated dumps may still be
134 required for restores at earlier dates. For example, assume that a
135 DLE had a level 0 on Monday, level 1's Tuesday through Thursday,
136 and a level 2 on Friday. Then the files required for a restore of
137 Fridays (the most recent) dump are those from Monday (level 0),
138 Thursday (level 1), and Friday (level 2). Tuesday and Wednesday's
139 files are outdated.
140 delete [ hostname [ disks ]* ]+
142 Delete the specified disks on hostname from the Amanda database.
143 Note
145 If you do not also remove the disk from the disklist(5) file,
146 Amanda will treat it as a new disk during the next run.
147 tape [ --days <num> ]
149 Display the tape(s) Amanda expects to write to during the next run.
150 See also amcheck(8).
151 bumpsize
153 Display the current bump threshold parameters, calculated for all
154 backup levels.
155 balance [ --days <num> ]
157 Display the distribution of full backups throughout the dump
158 schedule.
159 export [ hostname [ disks ]* ]*
161 Convert records from the Amanda database to a text format that may
162 be transmitted to another Amanda machine and imported.
163 import
165 Convert exported records read from standard input to a form Amanda
166 uses and insert them into the database on this machine.
167 config
169 Dump the full internal representation of this config, in text
170 format.
171 disklist [ hostname [ disks ]* ]*
173 Display the disklist(5) information for each of the disks on
174 hostname (or all hosts). Mostly used for debugging.
175 hosts
177 Output a list of distinct hosts in the disklist(5), one per line,
178 for easy use in shell scripts.
179 dles
181 Output a list of distinct DLEs in the disklist(5), one per line
182 with host and diskname separated by a space, for easy use in shell
183 scripts.
184 info [ hostname [ disks ]* ]*
186 Display the database record for each of the disks on hostname (or
187 all hosts). Mostly used for debugging.
188 -o configoption
190 See the "CONFIGURATION OVERRIDE" section in amanda(8).
191
193 Request three specific file systems on machine-a get a full level 0
194 backup during the next Amanda run.
195 $ amadmin daily force machine-a / /var /usr
196 amadmin: machine-a:/ is set to a forced level 0 tonight.
197 amadmin: machine-a:/var is set to a forced level 0 tonight.
198 amadmin: machine-a:/usr is set to a forced level 0 tonight.
199 Request all file systems on machine-b get a full level 0 backup during
201 the next Amanda run.
202 $ amadmin daily force machine-b
203 amadmin: machine-b:/ is set to a forced level 0 tonight.
204 amadmin: machine-b:/var is set to a forced level 0 tonight.
205 amadmin: machine-b:/usr is set to a forced level 0 tonight.
206 amadmin: machine-b:/home is set to a forced level 0 tonight.
207 Undo the previous force request for /home on machine-b. The other file
209 systems will still get a full level 0 backup.
210 $ amadmin daily unforce machine-b /home
211 amadmin: force command for machine-b:/home cleared.
212 Locate backup images of /var from machine-c. The tape or file column
214 displays either a tape label or a filename depending on whether the
215 image is on tape or is still in the holding disk. If the image is on
216 tape, the file column tells you which file on the tape has the image
217 (file number zero is a tape label). This column shows zero and is not
218 meaningful if the image is still in the holding disk. The status column
219 tells you whether the backup was successful or had some type of error.
220 $ amadmin daily find machine-c /var
221 date host disk lv tape or file file part status
222 2000-11-09 machine-c /var 0 000110 9 -- OK
223 2000-11-08 machine-c /var 2 000109 2 -- OK
224 2000-11-07 machine-c /var 2 /amanda/20001107/machine-c._var.2 0 OK
225 2000-11-06 machine-c /var 2 000107 2 -- OK
226 2000-11-05 machine-c /var 2 000106 3 -- OK
227 2000-11-04 machine-c /var 2 000105 2 -- OK
228 2000-11-03 machine-c /var 2 000104 2 -- OK
229 2000-11-02 machine-c /var 2 000103 2 -- OK
230 2000-11-01 machine-c /var 1 000102 5 -- OK
231 2000-10-31 machine-c /var 1 000101 3 -- OK
232 Forget about the /workspace disk on machine-d. If you do not also
234 remove the disk from the disklist(5) file, Amanda will treat it as a
235 new disk during the next run.
236 $ amadmin daily delete machine-d /workspace
237 amadmin: machine-d:/workspace deleted from database.
238 amadmin: NOTE: you'll have to remove these from the disklist(5) yourself.
239 Find the next tape Amanda will use (in this case, 123456).
241 $ amadmin daily tape
242 The next Amanda run should go onto tape 123456 or a new tape.
243 Show how well full backups are balanced across the dump cycle. The
245 due-date column is the day the backups are due for a full backup. #fs
246 shows the number of filesystems doing full backups that night, and orig
247 KB and out KB show the estimated total size of the backups before and
248 after any compression, respectively.
249 The balance column shows how far off that night's backups are from the
251 average size (shown at the bottom of the balance column). Amanda tries
252 to keep the backups within +/- 5%, but since the amount of data on each
253 filesystem is always changing, and Amanda will never delay backups just
254 to rebalance the schedule, it is common for the schedule to fluctuate
255 by larger percentages. In particular, in the case of a tape or backup
256 failure, a bump will occur the following night, which will not be
257 smoothed out until the next pass through the schedule.
258 The last line also shows an estimate of how many Amanda runs will be
260 made between full backups for a file system. In the example, a file
261 system will probably have a full backup done every eight times Amanda
262 is run (e.g. every eight days).
263 $ amadmin daily balance
264 due-date #fs orig KB out KB balance
265 -------------------------------------------
266 11/10 Mon 21 930389 768753 +5.1%
267 11/11 Tue 29 1236272 733211 +0.2%
268 11/12 Wed 31 1552381 735796 +0.6%
269 11/13 Thu 23 1368447 684552 -6.4%
270 11/14 Fri 32 1065603 758155 +3.6%
271 11/15 Sat 14 1300535 738430 +0.9%
272 11/16 Sun 31 1362696 740365 +1.2%
273 11/17 Mon 30 1427936 773397 +5.7%
274 11/18 Tue 11 1059191 721786 -1.3%
275 11/19 Wed 19 1108737 661867 -9.5%
276 -------------------------------------------
277 TOTAL 241 12412187 7316312 731631 (estimated 8 runs per dumpcycle)
278
280 amanda(8), amanda(8), amcheck(8), amdump(8), amrestore(8),
281 amfetchdump(8), amanda-match(7)
282 The Amanda Wiki: : http://wiki.zmanda.com/
284
286 James da Silva <jds@amanda.org>
287 Stefan G. Weichinger <sgw@amanda.org>
289Amanda 3.5.4 07/27/2023 AMADMIN(8)