3 Prev Chapter 35. The AMANDA Manual Pages. Next
5 -------------------------------------------------------------------------------
9 amadmin
\14 administrative interface to control AMANDA backups
13 amadmin config command [ command options ]
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 hkdlb ] [ 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:
69 hhost name kdisk name ddump date lbackup level btape label
70 An uppercase letter reverses the sort order for that key. The default
73 delete [ hostname [ disks ]* ]+
74 Delete the specified disks on hostname from the AMANDA database.
78 If you do not also remove the disk from the disklist file, AMANDA will
79 treat it as a new disk during the next run.
82 Display the tape(s) AMANDA expects to write to during the next run. See
86 Display the current bump threshold parameters, calculated for all backup
89 balance [ --days <num> ]
90 Display the distribution of full backups throughout the dump schedule.
92 export [ hostname [ disks ]* ]*
93 Convert records from the AMANDA database to a text format that may be
94 transmitted to another AMANDA machine and imported.
97 Convert exported records read from standard input to a form AMANDA uses
98 and insert them into the database on this machine.
100 disklist [ hostname [ disks ]* ]*
101 Display the disklist information for each of the disks on hostname (or
102 all hosts). Mostly used for debugging.
104 info [ hostname [ disks ]* ]*
105 Display the database record for each of the disks on hostname (or all
106 hosts). Mostly used for debugging.
111 Request three specific file systems on machine-a get a full level 0 backup
112 during the next AMANDA run.
114 $ amadmin daily force machine-a / /var /usr
115 amadmin: machine-a:/ is set to a forced level 0 tonight.
116 amadmin: machine-a:/var is set to a forced level 0 tonight.
117 amadmin: machine-a:/usr is set to a forced level 0 tonight.
119 Request all file systems on machine-b get a full level 0 backup during the next
122 $ amadmin daily force machine-b
123 amadmin: machine-b:/ is set to a forced level 0 tonight.
124 amadmin: machine-b:/var is set to a forced level 0 tonight.
125 amadmin: machine-b:/usr is set to a forced level 0 tonight.
126 amadmin: machine-b:/home is set to a forced level 0 tonight.
128 Undo the previous force request for /home on machine-b. The other file systems
129 will still get a full level 0 backup.
131 $ amadmin daily unforce machine-b /home
132 amadmin: force command for machine-b:/home cleared.
134 Locate backup images of /var from machine-c. The tape or file column displays
135 either a tape label or a filename depending on whether the image is on tape or
136 is still in the holding disk. If the image is on tape, the file column tells
137 you which file on the tape has the image (file number zero is a tape label).
138 This column shows zero and is not meaningful if the image is still in the
139 holding disk. The status column tells you whether the backup was successful or
140 had some type of error.
142 $ amadmin daily find machine-c /var
143 date host disk lv tape or file file status
144 2000-11-09 machine-c /var 0 000110 9 OK
145 2000-11-08 machine-c /var 2 000109 2 OK
146 2000-11-07 machine-c /var 2 /amanda/20001107/machine-c._var.2 0 OK
147 2000-11-06 machine-c /var 2 000107 2 OK
148 2000-11-05 machine-c /var 2 000106 3 OK
149 2000-11-04 machine-c /var 2 000105 2 OK
150 2000-11-03 machine-c /var 2 000104 2 OK
151 2000-11-02 machine-c /var 2 000103 2 OK
152 2000-11-01 machine-c /var 1 000102 5 OK
153 2000-10-31 machine-c /var 1 000101 3 OK
155 Forget about the /workspace disk on machine-d. If you do not also remove the
156 disk from the disklist file, AMANDA will treat it as a new disk during the next
159 $ amadmin daily delete machine-d /workspace
160 amadmin: machine-d:/workspace deleted from database.
161 amadmin: NOTE: you'll have to remove these from the disklist yourself.
163 Find the next tape AMANDA will use (in this case, 123456).
166 The next AMANDA run should go onto tape 123456 or a new tape.
168 Show how well full backups are balanced across the dump cycle. The due-date
169 column is the day the backups are due for a full backup. #fs shows the number
170 of filesystems doing full backups that night, and orig KB and out KB show the
171 estimated total size of the backups before and after any compression,
173 The balance column shows how far off that night's backups are from the average
174 size (shown at the bottom of the balance column). AMANDA tries to keep the
175 backups within +/- 5%, but since the amount of data on each filesystem is
176 always changing, and AMANDA will never delay backups just to rebalance the
177 schedule, it is common for the schedule to fluctuate by larger percentages. In
178 particular, in the case of a tape or backup failure, a bump will occur the
179 following night, which will not be smoothed out until the next pass through the
181 The last line also shows an estimate of how many AMANDA runs will be made
182 between full backups for a file system. In the example, a file system will
183 probably have a full backup done every eight times AMANDA is run (e.g. every
186 $ amadmin daily balance
187 due-date #fs orig KB out KB balance
188 -------------------------------------------
189 11/10 Mon 21 930389 768753 +5.1%
190 11/11 Tue 29 1236272 733211 +0.2%
191 11/12 Wed 31 1552381 735796 +0.6%
192 11/13 Thu 23 1368447 684552 -6.4%
193 11/14 Fri 32 1065603 758155 +3.6%
194 11/15 Sat 14 1300535 738430 +0.9%
195 11/16 Sun 31 1362696 740365 +1.2%
196 11/17 Mon 30 1427936 773397 +5.7%
197 11/18 Tue 11 1059191 721786 -1.3%
198 11/19 Wed 19 1108737 661867 -9.5%
199 -------------------------------------------
200 TOTAL 241 12412187 7316312 731631 (estimated 8 runs per dumpcycle)
205 /usr/local/etc/amanda/config/amanda.conf
209 James da Silva, <jds@amanda.org> : Original text
210 Stefan G. Weichinger, <sgw@amanda.org>, maintainer of the AMANDA-documentation:
215 amanda(8), amcheck(8), amdump(8), amrestore(8)
216 -------------------------------------------------------------------------------
219 Chapter 35. The AMANDA Manual Pages. Home amanda