1AMVAULT(8) System Administration Commands AMVAULT(8)
2
6 amvault - Copy Amanda dumps from one volume to another
7
9 amvault [-o configoption...] [--dry-run | -n] [--quiet | -q]
10 [--fulls-only] [--exact-match] [--export]
11 [--src-timestamp src-timestamp]
12 --label-template label-template --dst-changer dst-changer
13 [--autolabel autolabel-arg...]
14 config
15 [hostname [ disk [ date [ level [ hostname [...] ] ] ] ]]
16
18 This application is not yet in its final form, and is subject to major
19 revision in subsequent versions of Amanda. Backward compatibility is
20 not guaranteed.
21 Note that Amanda restore/recover operations will request tertiary media
23 by label when dumpfiles are not found on secondary media, but there is
24 no provision to automatically fetch such media from a different changer
25 Feedback on and patches to this application are invited and encouraged!
27
29 Amvault is conceptually equivalent to "amfetchdump | taper". That is,
30 it reads specified dumps from secondary media and re-writes them on
31 tertiary media.
32 Amvault Copies data from the run with timestamp src-timestamp onto
34 volumes using the changer dst-changer, and labeling new volumes with
35 label-template.
36 Secondary Media
38 The dumps to be read from secondary media can be specified by any
39 combination of dump specifications, --fulls-only, and --src-timestamp.
40 At least one must be specified, lest amvault attempt to vault all dumps
41 in the catalog. See amanda-match(7) for more information on dump
42 specifications.
43 Note that the datestamp given in the dumpspec is the dump datestamp -
45 the run in which the backup was taken on the Amanda client. The
46 --src-timestamp, on the other hand, is the write timestamp - the run in
47 which the dump was written to secondary media. The latter option
48 facilitates duplicating the results of an entire backup run, including
49 any dumps that might have been flushed from holding disk.
50 Tertiary Media
52 The --dst-changer must be specified, and names the changer in which
53 tertiary media are stored.
54 If amanda.conf(5) contains the new part-size splitting parameters, then
56 amvault will use them without any additional configuration. However, if
57 the configuration still uses the old splitting parameters
58 (tape_splitsize, split_diskbuffer, and fallback_splitsize), then
59 amvault will need some additional configuration in order to properly
60 split dumps to tertiary media. To do so, specify a new tapetype in
61 amanda.conf(5), say "TERTIARY", and set the part-size and other
62 appropriate parameters there. Then reference that tapetype in the
63 amvault invocation:
64 amvault -otapetype=TERTIARY ...
66
68 --autolabel [any] [other-config] [non-amanda] [volume-error] [empty]
69 Works just like the autolabel parameter in amanda.conf(5), and can
70 be specified multiple times if necessary. The default is 'empty'.
71 --dst-changer dst-changer
73 Specifies the changer in which tertiary media are stored. In
74 general, this should be different from the secondary changer, to
75 eliminate the possibility of overwriting secondary media with
76 tertiary data.
77 The dst-changer parameter should specify the name of a changer
79 defined in amanda.conf(5). For example:
80 define changer vaulting_tape {
82 tapedev "/dev/rmt/1n"
83 tpchanger "chg-zd-mtx"
84 changerdev "/dev/sg0"
85 changerfile "vaulting-changer.conf"
86 }
87 --dry-run, -n
89 Cause amvault to print the dumps it would vault, but not actually
90 perform any vaulting operations.
91 --exact-match
93 The host and disk are parsed as exact values
94 --export
96 Cause amvault to attempt to move completed tertiary volumes to
97 import/export slots, where they can be more easily removed by an
98 operator.
99 ---fulls-only
101 Only full (level-0) dumps are copied.
102 --label-template label-template
104 Specifies a label template which is used to generate new labels for
105 tertiary volumes.
106 --quiet, -q
108 Eliminate non-error messages, and is useful when running amvault
109 from cron.
110 --src-timestamps src-timestamps
112 Specifies the timestamps in the format 'YYYYMMDDHHMMSS' of the run
113 to vault, can be "latest", then the most recent amdump or amflush
114 run will be used.
115 -o configoption
117 See the "CONFIGURATION OVERRIDE" section in amanda(8).
118
120 Vault all dump written to tape in the latest amdump or amflush run:
121 $ amvault --src-timestamps latest --label-template "CONF-%%%" --dst-changer vault-changer CONF
122 Vault all dump written on the run of December 7 2011 12:13:14 :
124 $ amvault --src-timestamps 20111207121314 --label-template "CONF-%%%" --dst-changer vault-changer CONF
125 Vault all dump dumped on any run of December 7 2011:
127 $ amvault --label-template "CONF-%%%" --dst-changer vault-changer CONF \* \* 20111207
128
130 amanda(8), amanda-changers(7), amfetchdump(8)
131 The Amanda Wiki: : http://wiki.zmanda.com/
133
135 Dustin J. Mitchell <dustin@zmanda.com>
136 Zmanda, Inc. (http://www.zmanda.com)
137Amanda 3.3.3 01/10/2013 AMVAULT(8)