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