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] [--latest-fulls] [--incrs-only] [--exact-match]
11 [--export] [--no-interactivity] [--src-timestamp src-timestamp]
12 [--src-storage src-storage] [--dest-storage dest-storage]
13 config
14 [hostname [ disk [ date [ level [ hostname [dumpspec...] ] ] ] ]]
15
17 This application is not yet in its final form, and is subject to major
18 revision in subsequent versions of Amanda. Backward compatibility is
19 not guaranteed.
20 Note that Amanda restore/recover operations will request tertiary media
22 by label when dumpfiles are not found on secondary media, but there is
23 no provision to automatically fetch such media from a different changer
24 Feedback on and patches to this application are invited and encouraged!
26
28 Amvault is conceptually equivalent to "amfetchdump | taper". That is,
29 it reads specified dumps from secondary media and re-writes them on
30 tertiary media.
31 Amvault Copies dumps selected by the specified filters onto volumes on
33 the storage dest-storage.
34 Secondary Media
36 The dumps to be read from secondary media can be specified by any
37 combination of dump specifications, --fulls-only, --latest-fulls,
38 --incrs-only, and --src-timestamp. At least one must be specified, lest
39 amvault attempt to vault all dumps in the catalog. See amanda-match(7)
40 for more information on dump specifications.
41 Note that the datestamp given in the dumpspec is the dump datestamp -
43 the run in which the backup was taken on the Amanda client. The
44 --src-timestamp, on the other hand, is the write timestamp - the run in
45 which the dump was written to secondary media. The latter option
46 facilitates duplicating the results of an entire backup run, including
47 any dumps that might have been flushed from holding disk.
48 Tertiary Media
50 The amvault-storage is the default destination storage.
51 If amanda.conf(5) contains the new part-size splitting parameters, then
53 amvault will use them without any additional configuration. However, if
54 the configuration still uses the old splitting parameters
55 (tape_splitsize, split_diskbuffer, and fallback_splitsize), then
56 amvault will need some additional configuration in order to properly
57 split dumps to tertiary media. To do so, specify a new tapetype in
58 amanda.conf(5), say "TERTIARY", and set the part-size and other
59 appropriate parameters there. Then reference that tapetype in the
60 amvault invocation:
61 amvault -otapetype=TERTIARY ...
63
65 --dest-storage dest-storage
66 The vaulted dumps are written to the specified storage.
67 If the vault-storage option is specified in amanda.conf(5), amvault
69 will use that storage as the default destination. If not, a
70 destination storage must be specified on the amvault command line.
71 --dry-run, -n
73 Cause amvault to print the dumps it would vault, but not actually
74 perform any vaulting operations.
75 --exact-match
77 The host and disk names in the dumpspecs are parsed as exact
78 values.
79 --export
81 Cause amvault to attempt to move completed tertiary volumes to
82 import/export slots, where they can be more easily removed by an
83 operator.
84 --fulls-only
86 Only full (level-0) dumps are copied.
87 --incrs-only
89 Only incremental (level > 0) dumps are copied.
90 --latest-fulls
92 The latest full of every DLE in the disklist that do not have the
93 skipstrategy.
94 --no-interactivity
96 Disable interactivity if a source or destination volume is not
97 found.
98 --quiet, -q
100 Suppress the progress messages normally printed to the terminal as
101 dumps are being copied.
102 --src-labelstr labelstr
104 Only dumps from volumes matching labelstr are copied.
105 labelstr is a Perl regular expression, and will be matched as a
107 substring of the volume labels -- it may be necessary to anchor the
108 labelstr with "^" and/or "$" in order to prevent undesired partial
109 matches.
110 Also note that if a dump is split across multiple volumes and
112 labelstr matches only one of those volumes, amvault will not select
113 that dump for copying. For this reason, it is generally safer to to
114 select dumps directly using other filters, in which case amvault
115 will be able to retrieve parts of split dumps from whatever volume
116 they were originally written to.
117 --src-storage src-storage
119 Only dumps found on the specified storage are copied. (If this
120 option is not given, all available source storages will be
121 searched.)
122 --src-timestamps src-timestamps
124 Specifies the timestamps in the format 'YYYYMMDDHHMMSS' of the run
125 to vault, can be "latest", then the most recent amdump or amflush
126 run will be used.
127 -o configoption
129 See the "CONFIGURATION OVERRIDE" section in amanda(8).
130
132 Vault all dump written to tape in the latest amdump or amflush run:
133 $ amvault --src-timestamps latest CONF
134 Vault all dump written on the run of December 7 2011 12:13:14 :
136 $ amvault --src-timestamps 20111207121314 CONF
137 Vault all dump dumped on any run of December 7 2011:
139 $ amvault CONF \* \* 20111207
140
142 amanda(8), amanda-changers(7), amfetchdump(8)
143 The Amanda Wiki: : http://wiki.zmanda.com/
145
147 Dustin J. Mitchell <dustin@zmanda.com>
148 Zmanda, Inc. (http://www.zmanda.com)
149Amanda 3.5.1 12/01/2017 AMVAULT(8)