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 unforce [ hostname [ disks ]* ]+
76 Undo a previous force command.
77 reuse tapelabel [ ... ]
79 The tapes listed will be available for reuse at their point in the
80 tape cycle.
81 no-reuse tapelabel [ ... ]
83 The tapes listed will not be reused when their turn comes up again
84 in the tape cycle. Note that if this causes the number of reusable
85 tapes to drop below the amanda.conf tapecycle value, Amanda will
86 request new tapes until the count is satisfied again.
87 Tape marked no-reuse are available for recovery, marking them
89 no-reuse is a security to be sure amanda will not overwrite them.
90 due [ hostname [ disks ]* ]*
92 Show when the next full dump is due.
93 find [ --sort hkdlpbfw ] [ hostname [ disks ]* ]*
95 Display all backups currently on tape or in the holding disk. The
96 tape label or holding disk filename, file number, and status are
97 displayed.
98 The --sort option changes the sort order using the following flags:
100 h: host name
102 k: disk name
103 d: dump timestamp
104 l: backup level
105 p: dump part
106 b: tape label
107 f: filenum on tape
108 w: write timestamp
109 An uppercase letter reverses the sort order for that key. The
111 default sort order is hkdlpbfw.
112 holding delete hostname [ disk [ datestamp [ .. ] ] ]
114 Delete holding files matching the given specification. At least a
115 hostname must be provided.
116 holding list [-l] [-d] [ hostname [ disk [ datestamp [ .. ] ] ] ]
118 List holding files matching the given dump specification, or all
119 holding files if no specification is provided. See amanda-match(7)
120 for more information on dump specifications. With '-l', additional
121 information (size, level, and whether the dump is outdated) is
122 provided. With '-d', only outdated dumps are shown.
123 An outdated holding file is one which is not required for a restore
125 of the most recent dump. Note that outdated dumps may still be
126 required for restores at earlier dates. For example, assume that a
127 DLE had a level 0 on Monday, level 1's Tuesday through Thursday,
128 and a level 2 on Friday. Then the files required for a restore of
129 Fridays (the most recent) dump are those from Monday (level 0),
130 Thursday (level 1), and Friday (level 2). Tuesday and Wednesday's
131 files are outdated.
132 delete [ hostname [ disks ]* ]+
134 Delete the specified disks on hostname from the Amanda database.
135 Note
137 If you do not also remove the disk from the disklist(5) file,
138 Amanda will treat it as a new disk during the next run.
139 tape
141 Display the tape(s) Amanda expects to write to during the next run.
142 See also amcheck(8).
143 bumpsize
145 Display the current bump threshold parameters, calculated for all
146 backup levels.
147 balance [ --days <num> ]
149 Display the distribution of full backups throughout the dump
150 schedule.
151 export [ hostname [ disks ]* ]*
153 Convert records from the Amanda database to a text format that may
154 be transmitted to another Amanda machine and imported.
155 import
157 Convert exported records read from standard input to a form Amanda
158 uses and insert them into the database on this machine.
159 disklist [ hostname [ disks ]* ]*
161 Display the disklist(5) information for each of the disks on
162 hostname (or all hosts). Mostly used for debugging.
163 hosts
165 Output a list of distinct hosts in the disklist(5), one per line,
166 for easy use in shell scripts.
167 dles
169 Output a list of distinct DLEs in the disklist(5), one per line
170 with host and diskname separated by a space, for easy use in shell
171 scripts.
172 info [ hostname [ disks ]* ]*
174 Display the database record for each of the disks on hostname (or
175 all hosts). Mostly used for debugging.
176 -o configoption
178 See the "CONFIGURATION OVERRIDE" section in amanda(8).
179
181 Request three specific file systems on machine-a get a full level 0
182 backup during the next Amanda run.
183 $ amadmin daily force machine-a / /var /usr
184 amadmin: machine-a:/ is set to a forced level 0 tonight.
185 amadmin: machine-a:/var is set to a forced level 0 tonight.
186 amadmin: machine-a:/usr is set to a forced level 0 tonight.
187 Request all file systems on machine-b get a full level 0 backup during
189 the next Amanda run.
190 $ amadmin daily force machine-b
191 amadmin: machine-b:/ is set to a forced level 0 tonight.
192 amadmin: machine-b:/var is set to a forced level 0 tonight.
193 amadmin: machine-b:/usr is set to a forced level 0 tonight.
194 amadmin: machine-b:/home is set to a forced level 0 tonight.
195 Undo the previous force request for /home on machine-b. The other file
197 systems will still get a full level 0 backup.
198 $ amadmin daily unforce machine-b /home
199 amadmin: force command for machine-b:/home cleared.
200 Locate backup images of /var from machine-c. The tape or file column
202 displays either a tape label or a filename depending on whether the
203 image is on tape or is still in the holding disk. If the image is on
204 tape, the file column tells you which file on the tape has the image
205 (file number zero is a tape label). This column shows zero and is not
206 meaningful if the image is still in the holding disk. The status column
207 tells you whether the backup was successful or had some type of error.
208 $ amadmin daily find machine-c /var
209 date host disk lv tape or file file part status
210 2000-11-09 machine-c /var 0 000110 9 -- OK
211 2000-11-08 machine-c /var 2 000109 2 -- OK
212 2000-11-07 machine-c /var 2 /amanda/20001107/machine-c._var.2 0 OK
213 2000-11-06 machine-c /var 2 000107 2 -- OK
214 2000-11-05 machine-c /var 2 000106 3 -- OK
215 2000-11-04 machine-c /var 2 000105 2 -- OK
216 2000-11-03 machine-c /var 2 000104 2 -- OK
217 2000-11-02 machine-c /var 2 000103 2 -- OK
218 2000-11-01 machine-c /var 1 000102 5 -- OK
219 2000-10-31 machine-c /var 1 000101 3 -- OK
220 Forget about the /workspace disk on machine-d. If you do not also
222 remove the disk from the disklist(5) file, Amanda will treat it as a
223 new disk during the next run.
224 $ amadmin daily delete machine-d /workspace
225 amadmin: machine-d:/workspace deleted from database.
226 amadmin: NOTE: you'll have to remove these from the disklist(5) yourself.
227 Find the next tape Amanda will use (in this case, 123456).
229 $ amadmin daily tape
230 The next Amanda run should go onto tape 123456 or a new tape.
231 Show how well full backups are balanced across the dump cycle. The
233 due-date column is the day the backups are due for a full backup. #fs
234 shows the number of filesystems doing full backups that night, and orig
235 KB and out KB show the estimated total size of the backups before and
236 after any compression, respectively.
237 The balance column shows how far off that night's backups are from the
239 average size (shown at the bottom of the balance column). Amanda tries
240 to keep the backups within +/- 5%, but since the amount of data on each
241 filesystem is always changing, and Amanda will never delay backups just
242 to rebalance the schedule, it is common for the schedule to fluctuate
243 by larger percentages. In particular, in the case of a tape or backup
244 failure, a bump will occur the following night, which will not be
245 smoothed out until the next pass through the schedule.
246 The last line also shows an estimate of how many Amanda runs will be
248 made between full backups for a file system. In the example, a file
249 system will probably have a full backup done every eight times Amanda
250 is run (e.g. every eight days).
251 $ amadmin daily balance
252 due-date #fs orig KB out KB balance
253 -------------------------------------------
254 11/10 Mon 21 930389 768753 +5.1%
255 11/11 Tue 29 1236272 733211 +0.2%
256 11/12 Wed 31 1552381 735796 +0.6%
257 11/13 Thu 23 1368447 684552 -6.4%
258 11/14 Fri 32 1065603 758155 +3.6%
259 11/15 Sat 14 1300535 738430 +0.9%
260 11/16 Sun 31 1362696 740365 +1.2%
261 11/17 Mon 30 1427936 773397 +5.7%
262 11/18 Tue 11 1059191 721786 -1.3%
263 11/19 Wed 19 1108737 661867 -9.5%
264 -------------------------------------------
265 TOTAL 241 12412187 7316312 731631 (estimated 8 runs per dumpcycle)
266
268 amanda(8), amanda(8), amcheck(8), amdump(8), amrestore(8),
269 amfetchdump(8), amanda-match(7)
270 The Amanda Wiki: : http://wiki.zmanda.com/
272
274 James da Silva <jds@amanda.org>
275 Stefan G. Weichinger <sgw@amanda.org>
277Amanda 3.3.3 01/10/2013 AMADMIN(8)