1AMADMIN(8) 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 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. Both hostname and disks are
22 special expressions, see the "HOST & DISK EXPRESSION" section of
23 amanda(8) for a description.
24 version
26 Show the current version and some compile time and runtime
27 parameters. The config parameter must be present but is ignored.
28 force-bump [ hostname [ disks ]* ]+
30 Force the disks on hostname to bump to a new incremental level
31 during the next Amanda run.
32 force-no-bump [ hostname [ disks ]* ]+
34 Force the disks on hostname to not bump to a new incremental level
35 during the next Amanda run.
36 unforce-bump [ hostname [ disks ]* ]+
38 Undo a previous force-bump or force-no-bump command.
39 force [ hostname [ disks ]* ]+
41 Force the disks on hostname to do a full (level 0) backup during
42 the next Amanda run.
43 unforce [ hostname [ disks ]* ]+
45 Undo a previous force command.
46 reuse tapelabel [ ... ]
48 The tapes listed will be available for reuse at their point in the
49 tape cycle.
50 no-reuse tapelabel [ ... ]
52 The tapes listed will not be reused when their turn comes up again
53 in the tape cycle. Note that if this causes the number of reusable
54 tapes to drop below the amanda.conf tapecycle value, Amanda will
55 request new tapes until the count is satisfied again.
56 due [ hostname [ disks ]* ]*
58 Show when the next full dump is due.
59 find [ --sort hkdlpb ] [ hostname [ disks ]* ]*
61 Display all backups currently on tape or in the holding disk. The
62 tape label or holding disk filename, file number, and status are
63 displayed.
64 The --sort option changes the sort order using the following flags:
66 h: host name
68 k: disk name
69 d: dump date
70 l: backup level
71 p: dump part
72 b: tape label
73 An uppercase letter reverses the sort order for that key. The
75 default sort order is hkdlpb.
76 delete [ hostname [ disks ]* ]+
78 Delete the specified disks on hostname from the Amanda database.
79 Note
81 If you do not also remove the disk from the disklist file, Amanda
82 will treat it as a new disk during the next run.
83 tape
85 Display the tape(s) Amanda expects to write to during the next run.
86 See also amcheck(8).
87 bumpsize
89 Display the current bump threshold parameters, calculated for all
90 backup levels.
91 balance [ --days <num> ]
93 Display the distribution of full backups throughout the dump
94 schedule.
95 export [ hostname [ disks ]* ]*
97 Convert records from the Amanda database to a text format that may
98 be transmitted to another Amanda machine and imported.
99 import
101 Convert exported records read from standard input to a form Amanda
102 uses and insert them into the database on this machine.
103 disklist [ hostname [ disks ]* ]*
105 Display the disklist information for each of the disks on hostname
106 (or all hosts). Mostly used for debugging.
107 info [ hostname [ disks ]* ]*
109 Display the database record for each of the disks on hostname (or
110 all hosts). Mostly used for debugging.
111 -o configoption
113 See the "CONFIGURATION OVERWRITE" section in amanda(8).
114
116 Request three specific file systems on machine-a get a full level 0
117 backup during the next Amanda run.
118 $ amadmin daily force machine-a / /var /usr
120 amadmin: machine-a:/ is set to a forced level 0 tonight.
121 amadmin: machine-a:/var is set to a forced level 0 tonight.
122 amadmin: machine-a:/usr is set to a forced level 0 tonight.
123 Request all file systems on machine-b get a full level 0 backup during
125 the next Amanda run.
126 $ amadmin daily force machine-b
128 amadmin: machine-b:/ is set to a forced level 0 tonight.
129 amadmin: machine-b:/var is set to a forced level 0 tonight.
130 amadmin: machine-b:/usr is set to a forced level 0 tonight.
131 amadmin: machine-b:/home is set to a forced level 0 tonight.
132 Undo the previous force request for /home on machine-b. The other file
134 systems will still get a full level 0 backup.
135 $ amadmin daily unforce machine-b /home
137 amadmin: force command for machine-b:/home cleared.
138 Locate backup images of /var from machine-c. The tape or file column
140 displays either a tape label or a filename depending on whether the
141 image is on tape or is still in the holding disk. If the image is on
142 tape, the file column tells you which file on the tape has the image
143 (file number zero is a tape label). This column shows zero and is not
144 meaningful if the image is still in the holding disk. The status column
145 tells you whether the backup was successful or had some type of error.
146 $ amadmin daily find machine-c /var
148 date host disk lv tape or file file part status
149 2000-11-09 machine-c /var 0 000110 9 -- OK
150 2000-11-08 machine-c /var 2 000109 2 -- OK
151 2000-11-07 machine-c /var 2 /amanda/20001107/machine-c._var.2 0 OK
152 2000-11-06 machine-c /var 2 000107 2 -- OK
153 2000-11-05 machine-c /var 2 000106 3 -- OK
154 2000-11-04 machine-c /var 2 000105 2 -- OK
155 2000-11-03 machine-c /var 2 000104 2 -- OK
156 2000-11-02 machine-c /var 2 000103 2 -- OK
157 2000-11-01 machine-c /var 1 000102 5 -- OK
158 2000-10-31 machine-c /var 1 000101 3 -- OK
159 Forget about the /workspace disk on machine-d. If you do not also
161 remove the disk from the disklist file, Amanda will treat it as a new
162 disk during the next run.
163 $ amadmin daily delete machine-d /workspace
165 amadmin: machine-d:/workspace deleted from database.
166 amadmin: NOTE: you'll have to remove these from the disklist yourself.
167 Find the next tape Amanda will use (in this case, 123456).
169 $ amadmin daily tape
171 The next Amanda run should go onto tape 123456 or a new tape.
172 Show how well full backups are balanced across the dump cycle. The
174 due-date column is the day the backups are due for a full backup. #fs
175 shows the number of filesystems doing full backups that night, and orig
176 KB and out KB show the estimated total size of the backups before and
177 after any compression, respectively.
178 The balance column shows how far off that night's backups are from the
180 average size (shown at the bottom of the balance column). Amanda tries
181 to keep the backups within +/- 5%, but since the amount of data on each
182 filesystem is always changing, and Amanda will never delay backups just
183 to rebalance the schedule, it is common for the schedule to fluctuate
184 by larger percentages. In particular, in the case of a tape or backup
185 failure, a bump will occur the following night, which will not be
186 smoothed out until the next pass through the schedule.
187 The last line also shows an estimate of how many Amanda runs will be
189 made between full backups for a file system. In the example, a file
190 system will probably have a full backup done every eight times Amanda
191 is run (e.g. every eight days).
192 $ amadmin daily balance
194 due-date #fs orig KB out KB balance
195 -------------------------------------------
196 11/10 Mon 21 930389 768753 +5.1%
197 11/11 Tue 29 1236272 733211 +0.2%
198 11/12 Wed 31 1552381 735796 +0.6%
199 11/13 Thu 23 1368447 684552 -6.4%
200 11/14 Fri 32 1065603 758155 +3.6%
201 11/15 Sat 14 1300535 738430 +0.9%
202 11/16 Sun 31 1362696 740365 +1.2%
203 11/17 Mon 30 1427936 773397 +5.7%
204 11/18 Tue 11 1059191 721786 -1.3%
205 11/19 Wed 19 1108737 661867 -9.5%
206 -------------------------------------------
207 TOTAL 241 12412187 7316312 731631 (estimated 8 runs per dumpcycle)
208
210 /usr/local/etc/amanda/config/amanda.conf
211
213 James da Silva, <jds@amanda.org> : Original text
214 Stefan G. Weichinger, <sgw@amanda.org>, maintainer of the
216 Amanda-documentation: XML-conversion
217
219 amanda(8), amcheck(8), amdump(8), amrestore(8), amfetchdump(8)
220 02/07/2007 AMADMIN(8)