3 Prev Chapter 36. The Amanda Manual Pages. Next
5 -------------------------------------------------------------------------------
9 amadmin
\14 administrative interface to control Amanda backups
13 amadmin config command [command_options...] [-oconfigoption]...
17 Amadmin performs various administrative tasks on the config Amanda
19 See the amanda(8) man page for more details about Amanda.
23 Commands that take a hostname [ disks ] parameter pair operate on all disks in
24 the disklist for that hostname if no disks are specified. Where hostname is
25 also marked as being optional, the command operates on all hosts and disks in
26 the disklist. Both hostname and disks are special expressions, see the "HOST &
27 DISK EXPRESSION" section of amanda(8) for a description.
31 Show the current version and some compile time and runtime parameters.
32 The config parameter must be present but is ignored.
34 force-bump [ hostname [ disks ]* ]+
35 Force the disks on hostname to bump to a new incremental level during the
38 force-no-bump [ hostname [ disks ]* ]+
39 Force the disks on hostname to not bump to a new incremental level during
42 unforce-bump [ hostname [ disks ]* ]+
43 Undo a previous force-bump or force-no-bump command.
45 force [ hostname [ disks ]* ]+
46 Force the disks on hostname to do a full (level 0) backup during the next
49 unforce [ hostname [ disks ]* ]+
50 Undo a previous force command.
52 reuse tapelabel [ ... ]
53 The tapes listed will be available for reuse at their point in the tape
56 no-reuse tapelabel [ ... ]
57 The tapes listed will not be reused when their turn comes up again in the
58 tape cycle. Note that if this causes the number of reusable tapes to drop
59 below the amanda.conf tapecycle value, Amanda will request new tapes
60 until the count is satisfied again.
62 due [ hostname [ disks ]* ]*
63 Show when the next full dump is due.
65 find [ --sort hkdlpb ] [ hostname [ disks ]* ]*
66 Display all backups currently on tape or in the holding disk. The tape
67 label or holding disk filename, file number, and status are displayed.
68 The --sort option changes the sort order using the following flags:
77 An uppercase letter reverses the sort order for that key. The default
80 delete [ hostname [ disks ]* ]+
81 Delete the specified disks on hostname from the Amanda database.
85 If you do not also remove the disk from the disklist file, Amanda will
86 treat it as a new disk during the next run.
89 Display the tape(s) Amanda expects to write to during the next run. See
93 Display the current bump threshold parameters, calculated for all backup
96 balance [ --days <num> ]
97 Display the distribution of full backups throughout the dump schedule.
99 export [ hostname [ disks ]* ]*
100 Convert records from the Amanda database to a text format that may be
101 transmitted to another Amanda machine and imported.
104 Convert exported records read from standard input to a form Amanda uses
105 and insert them into the database on this machine.
107 disklist [ hostname [ disks ]* ]*
108 Display the disklist information for each of the disks on hostname (or
109 all hosts). Mostly used for debugging.
111 info [ hostname [ disks ]* ]*
112 Display the database record for each of the disks on hostname (or all
113 hosts). Mostly used for debugging.
116 See the "CONFIGURATION OVERWRITE" section in amanda(8).
121 Request three specific file systems on machine-a get a full level 0 backup
122 during the next Amanda run.
124 $ amadmin daily force machine-a / /var /usr
125 amadmin: machine-a:/ is set to a forced level 0 tonight.
126 amadmin: machine-a:/var is set to a forced level 0 tonight.
127 amadmin: machine-a:/usr is set to a forced level 0 tonight.
129 Request all file systems on machine-b get a full level 0 backup during the next
132 $ amadmin daily force machine-b
133 amadmin: machine-b:/ is set to a forced level 0 tonight.
134 amadmin: machine-b:/var is set to a forced level 0 tonight.
135 amadmin: machine-b:/usr is set to a forced level 0 tonight.
136 amadmin: machine-b:/home is set to a forced level 0 tonight.
138 Undo the previous force request for /home on machine-b. The other file systems
139 will still get a full level 0 backup.
141 $ amadmin daily unforce machine-b /home
142 amadmin: force command for machine-b:/home cleared.
144 Locate backup images of /var from machine-c. The tape or file column displays
145 either a tape label or a filename depending on whether the image is on tape or
146 is still in the holding disk. If the image is on tape, the file column tells
147 you which file on the tape has the image (file number zero is a tape label).
148 This column shows zero and is not meaningful if the image is still in the
149 holding disk. The status column tells you whether the backup was successful or
150 had some type of error.
152 $ amadmin daily find machine-c /var
153 date host disk lv tape or file file part status
154 2000-11-09 machine-c /var 0 000110 9 -- OK
155 2000-11-08 machine-c /var 2 000109 2 -- OK
156 2000-11-07 machine-c /var 2 /amanda/20001107/machine-c._var.2 0 OK
157 2000-11-06 machine-c /var 2 000107 2 -- OK
158 2000-11-05 machine-c /var 2 000106 3 -- OK
159 2000-11-04 machine-c /var 2 000105 2 -- OK
160 2000-11-03 machine-c /var 2 000104 2 -- OK
161 2000-11-02 machine-c /var 2 000103 2 -- OK
162 2000-11-01 machine-c /var 1 000102 5 -- OK
163 2000-10-31 machine-c /var 1 000101 3 -- OK
165 Forget about the /workspace disk on machine-d. If you do not also remove the
166 disk from the disklist file, Amanda will treat it as a new disk during the next
169 $ amadmin daily delete machine-d /workspace
170 amadmin: machine-d:/workspace deleted from database.
171 amadmin: NOTE: you'll have to remove these from the disklist yourself.
173 Find the next tape Amanda will use (in this case, 123456).
176 The next Amanda run should go onto tape 123456 or a new tape.
178 Show how well full backups are balanced across the dump cycle. The due-date
179 column is the day the backups are due for a full backup. #fs shows the number
180 of filesystems doing full backups that night, and orig KB and out KB show the
181 estimated total size of the backups before and after any compression,
183 The balance column shows how far off that night's backups are from the average
184 size (shown at the bottom of the balance column). Amanda tries to keep the
185 backups within +/- 5%, but since the amount of data on each filesystem is
186 always changing, and Amanda will never delay backups just to rebalance the
187 schedule, it is common for the schedule to fluctuate by larger percentages. In
188 particular, in the case of a tape or backup failure, a bump will occur the
189 following night, which will not be smoothed out until the next pass through the
191 The last line also shows an estimate of how many Amanda runs will be made
192 between full backups for a file system. In the example, a file system will
193 probably have a full backup done every eight times Amanda is run (e.g. every
196 $ amadmin daily balance
197 due-date #fs orig KB out KB balance
198 -------------------------------------------
199 11/10 Mon 21 930389 768753 +5.1%
200 11/11 Tue 29 1236272 733211 +0.2%
201 11/12 Wed 31 1552381 735796 +0.6%
202 11/13 Thu 23 1368447 684552 -6.4%
203 11/14 Fri 32 1065603 758155 +3.6%
204 11/15 Sat 14 1300535 738430 +0.9%
205 11/16 Sun 31 1362696 740365 +1.2%
206 11/17 Mon 30 1427936 773397 +5.7%
207 11/18 Tue 11 1059191 721786 -1.3%
208 11/19 Wed 19 1108737 661867 -9.5%
209 -------------------------------------------
210 TOTAL 241 12412187 7316312 731631 (estimated 8 runs per dumpcycle)
215 /usr/local/etc/amanda/config/amanda.conf
219 James da Silva, <jds@amanda.org> : Original text
220 Stefan G. Weichinger, <sgw@amanda.org>, maintainer of the Amanda-documentation:
225 amanda(8), amcheck(8), amdump(8), amrestore(8), amfetchdump(8)
226 -------------------------------------------------------------------------------
229 Chapter 36. The Amanda Manual Pages. Home amaespipe