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