1AMANDA(8) System Administration Commands AMANDA(8)
2
6 amanda - The Open Source Backup Platform
7
9 This manual page gives an overview of the Amanda commands and
10 configuration files for quick reference.
11 COMMANDS
13 Here are all the Amanda commands. Each one has its own manual page. See
14 them for all the gory details.
15 · amaddclient(8),
17 · amadmin(8),
19 · amaespipe(8),
21 · amcheck(8),
23 · amcheckdb(8),
25 · amcheckdump(8),
27 · amcleanup(8),
29 · amcrypt-ossl-asym(8),
31 · amcrypt-ossl(8),
33 · amcrypt(8),
35 · amcryptsimple(8),
37 · amdd(8),
39 · amdevcheck(8),
41 · amdump(8),
43 · amfetchdump(8),
45 · amflush(8),
47 · amgetconf(8),
49 · amgpgcrypt(8),
51 · amgtar(8),
53 · amlabel(8),
55 · ammt(8),
57 · amoverview(8),
59 · amplot(8),
61 · amrecover(8),
63 · amreport(8),
65 · amrestore(8),
67 · amrmtape(8),
69 · amsamba(8),
71 · amserverconfig(8),
73 · amservice(8),
75 · amstar(8),
77 · amstatus(8),
79 · amtape(8),
81 · amtapetype(8),
83 · amtoc(8),
85 · amvault(8),
87 · amzfs-sendrecv(8),
89 · amzfs-snapshot(8),
91 · script-email(8),
93 CONFIGURATION FILES
95 · amanda.conf(5),
96 · amanda-client.conf(5),
98 · disklist(5),
100 · tapelist(5),
102 DATA FORMATS
104 · amanda-archive-format(5),
105 CONCEPTS
107 · amanda-applications(7),
108 · amanda-auth(7),
110 · amanda-changers(7),
112 · amanda-devices(7),
114 · amanda-scripts(7),
116
118 There are four user-editable files that control the behavior of Amanda.
119 The first two are amanda.conf(5) and amanda-client.conf(5), the main
121 configuration files for the server and client, respectively. They
122 contain parameters to customize Amanda for the site.
123 Next is the disklist(5) file, which lists hosts and disk partitions to
125 back up.
126 Last is the seldom-edited tapelist(5) file, which lists tapes that are
128 currently active. These files are described in more detail in the
129 following sections.
130 All files are stored in individual configuration directories, usually
132 under /etc/amanda/. A site will often have more than one configuration.
133 For example, it might have a normal configuration for everyday backups
134 and an archive configuration for infrequent full archival backups. The
135 configuration files would be stored under directories
136 /etc/amanda/normal/ and /etc/amanda/archive/, respectively. Part of the
137 job of an Amanda administrator is to create, populate and maintain
138 these directories.
139
141 All log and database files generated by Amanda go in corresponding
142 directories somewhere. The exact location is controlled by entries in
143 amanda.conf(5). A typical location would be under /var/adm/amanda. For
144 the above example, the files might go in /var/adm/amanda/normal/ and
145 /var/adm/amanda/archive/.
146 As log files are no longer needed (no longer contain relevant
148 information), Amanda cycles them out in various ways, depending on the
149 type of file.
150 Detailed information about amdump runs are stored in dump logs -- files
152 named amdump.NN where NN is a sequence number, with 1 being the most
153 recent file. Amdump rotates these files each run, keeping roughly the
154 last tapecycle (see below) worth of them.
155 The file used by amreport to generate the mail summary is the trace
157 log. This file constitutes the "catalog" describing the data on the
158 tapes written in a run. It is named log.YYYYMMDDHHMMSS.NN where
159 YYYYMMDDHHMMSS is the datestamp of the start of the amdump or amflush
160 run and NN is a sequence number started at 0. At the end of each amdump
161 run, log files for runs whose tapes have been reused are renamed into a
162 subdirectory of the main log directory (see the logdir parameter below)
163 named oldlog. It is up to the Amanda administrator to remove them from
164 this directory when desired.
165 Index (backup image catalogue) files older than the full dump matching
167 the oldest backup image for a given client and disk are removed by
168 amdump at the end of each run.
169
171 For Samba access, Amanda needs a file on the Samba server (which may or
172 may not also be the tape server) named /etc/amandapass with share
173 names, (clear text) passwords and (optional) domain names, in that
174 order, one per line, whitespace separated. By default, the user used to
175 connect to the PC is the same for all PC´s and is compiled into Amanda.
176 It may be changed on a host by host basis by listing it first in the
177 password field followed by a percent sign and then the password. For
178 instance:
179 //some-pc/home normalpw
180 //another-pc/disk otheruser%otherpw
181 With clear text passwords, this file should obviously be tightly
183 protected. It only needs to be readable by the Amanda-user on the Samba
184 server.
185
187 All host and disk arguments to programs are special expressions. The
188 command applies to all disks that match your arguments. This section
189 describes the matcher.
190 The matcher matches by word, each word is a glob expression, words are
192 separated by the separator ´.´ for host and ´/´ for disk. You can
193 anchor the expression at left with a ´^´. You can anchor the expression
194 at right with a ´$´. The matcher is case insensitive for host but is
195 case sensitive for disk. A match succeeds if all words in your
196 expression match contiguous words in the host or disk.
197 dot (.)
199 word separator for a host
200 /
202 word separator for a disk
203 ^
205 anchor at left
206 $
208 anchor at right
209 ?
211 match exactly one character except the separator
212 *
214 match zero or more characters except the separator
215 **
217 match zero or more characters including the separator
218 Some examples:
220 hosta
222 Will match hosta, foo.hosta.org, and hoSTA.dOMAIna.ORG but not
223 hostb.
224 host
226 Will match host but not hosta.
227 host?
229 Will match hosta and hostb, but not host.
230 ho*na
232 Will match hoina but not ho.aina.org.
233 ho**na
235 Will match hoina and ho.aina.org.
236 ^hosta
238 Will match hosta but not foo.hosta.org.
239 sda*
241 Will match /dev/sda1 and /dev/sda12.
242 /opt
244 Will match the disk opt but not the host opt.
245 (note dots:) .opt.
247 Will match the host opt but not the disk opt.
248 /
250 Will match the disk / but no other disk.
251 /usr
253 Will match the disks /usr and /usr/local.
254 /usr$
256 Will match the disks /usr but not /usr/local.
257
259 A datestamp expression is a range expression where we only match the
260 prefix. Leading ^ is removed. Trailing $ forces an exact match.
261 20001212-14
263 match all dates beginning with 20001212, 20001213 or 20001214
264 20001212-4
266 same as previous
267 20001212-24
269 match all dates between 20001212 and 20001224
270 2000121
272 match all dates that start with 2000121 (20001210-20001219)
273 2
275 match all dates that start with 2 (20000101-29991231)
276 2000-10
278 match all dates between 20000101-20101231
279 200010$
281 match only 200010
282
284 A dump specification selects one or more dumps. It has the form
285 [host][:disk][@datestamp], where each component is a pattern as
286 described above. If a component is missing, it is treated as a
287 wildcard. The characters ´:´, ´@´, and ´\´ may be escaped within any
288 component by preceding them with a ´\´.
289 Some examples:
291 client17
293 all dumps of client17
294 @20080615
296 All dumps on with datestamps matching 20080615
297 webserver:/var/www
299 All dumps of /var/www on host webserver
300 webserver:/var/www@200806150317
302 The dump of webserver with datestamp 200806150317
303 :/var/www
305 All dumps of /var/www on any host
306
308 Most commands allow the override of specific configuration options on
309 the command line, using the -o option. This option has the form
310 -oname=value. An optional space is allowed after the -o. Each
311 configuration option should be specified in a separate command-line
312 option.
313 For global options, name is simply the name of the option, e.g.,
315 amdump -oruntapes=2
317 For options in a named section of the configuration, name has the form
318 SECTION:section_name:name, where SECTION is one of TAPETYPE, DUMPTYPE,
319 HOLDINGDISK, or INTERFACE, and section_name is the name of the
320 tapetype, dumptype, holdingdisk, or interface. Examples:
321 amdump -o TAPETYPE:HP-DAT:length=2000m
323 amdump -o DUMPTYPE:no-compress:compress="server fast"
324 amdump -o HOLDINGDISK:hd1:use="-100 mb"
325 amdump -o INTERFACE:local:use="2000 kbps"
326 When overriding device properties, one must carefully quote the command
328 line to simulate the syntax of real configuration files. The following
329 example should serve as a guide:
330 amdump -o ´device-property="PROPERTY_MAX_VOLUME_USAGE" "100000"´
332 Note that configuration overrides are not effective for tape changers,
334 which supply a tapedev based on their own configuration. In order to
335 override tapedev, you must also disable any changer:
336 amdump -otapedev=/dev/nst1 -otpchanger=´´
338
340 James da Silva <jds@amanda.org>
341 Stefan G. Weichinger <sgw@amanda.org>
343Amanda 2.6.1p2 11/05/2009 AMANDA(8)