X-Git-Url: https://git.gag.com/?a=blobdiff_plain;f=man%2Fxml-source%2Famvault.8.xml;h=510b2cb0e8fd448aaff2a5e38289429883b5dd1a;hb=refs%2Ftags%2Fupstream%2F3.3.3;hp=fd337ea8ae032c02411a625903ceca66468a1082;hpb=2627875b7d18858bc1f9f7652811e4d8c15a23eb;p=debian%2Famanda diff --git a/man/xml-source/amvault.8.xml b/man/xml-source/amvault.8.xml index fd337ea..510b2cb 100644 --- a/man/xml-source/amvault.8.xml +++ b/man/xml-source/amvault.8.xml @@ -3,7 +3,7 @@ "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [ - + %global_entities; ]> @@ -17,7 +17,7 @@ amvault -Copy &A; dumps from one volume to another +Copy Amanda dumps from one volume to another &author.dustin; @@ -26,26 +26,50 @@ amvault - -o configoption + &configoverride.synopsis; + --dry-run-n + --quiet-q + --fulls-only + --exact-match + --export + + src-timestamp + + + label-template + + dst-changer + + autolabel-arg + config - src-run-timestamp - dst-changer - label-template + + hostname + + disk + + date + + level + + hostname + ... + + + + + WARNING + This application is not yet in its final form, and is subject to major revision in subsequent versions of Amanda. Backward compatibility is not guaranteed. -The significant limitations of this version of amvault are: tapetypes for -secondary and tertiary volumes much match (including length and -device_properties); tertiary volumes must be blank (manual erasure is required -to re-use tertiary media; restore/recover operations will request tertiary -media by label when dumpfiles are not found on secondary media, but there is no -provision to automatically fetch such media from a different changer; and all -dumpfiles on a secondary volume are moved to tertiary media - there is no -provision to filter dumps. +Note that Amanda restore/recover operations will request tertiary media +by label when dumpfiles are not found on secondary media, but there is no +provision to automatically fetch such media from a different changer Feedback on and patches to this application are invited and encouraged! @@ -54,21 +78,80 @@ encouraged! DESCRIPTION +Amvault is conceptually equivalent to "amfetchdump | taper". That is, it reads +specified dumps from secondary media and re-writes them on tertiary media. + Amvault Copies data from the run with -timestamp src-run-timestamp onto volumes using -the changer dst-changer, labeling new volumes -with label-template. If src-run-timestamp is "latest", then the most recent amdump -or amflush run will be used. +timestamp onto volumes using the changer +, and labeling new volumes with +. + +Secondary Media + +The dumps to be read from secondary media can be specified by any +combination of dump specifications, , and +. At least one must be specified, lest +amvault attempt to vault all dumps in the catalog. See for more information on dump +specifications. + +Note that the datestamp given in the dumpspec is the +dump datestamp - the run in which the backup was taken +on the Amanda client. The , on the other +hand, is the write timestamp - the run in which the +dump was written to secondary media. The latter option facilitates +duplicating the results of an entire backup run, including any dumps that +might have been flushed from holding disk. + + + +Tertiary Media + +The must be specified, and names the +changer in which tertiary media are stored. -In a vaulting operation, the source media is referred to as "secondary -media", while the destination is referred to as "tertiary media". +If &amconf; contains the new part-size +splitting parameters, then amvault will use them without any additional configuration. +However, if the configuration still uses the old splitting parameters +(tape_splitsize, +split_diskbuffer, and +fallback_splitsize), then amvault will need some +additional configuration in order to properly split dumps to tertiary +media. To do so, specify a new tapetype in &amconf;, say "TERTIARY", +and set the part-size and other appropriate +parameters there. Then reference that tapetype in the amvault invocation: + + amvault -otapetype=TERTIARY ... + + + + + + +OPTIONS + + + any + other-config + non-amanda + volume-error + empty + +Works just like the +autolabel parameter in &amconf;, and can be +specified multiple times if necessary. The default is 'empty'. + + -Each source volume will be copied to a new destination volume; no -re-assembly or splitting will be performed. Destination volumes must be at -least as large as the source volumes. + + dst-changer + +Specifies the changer +in which tertiary media are stored. In general, this should be different +from the secondary changer, to eliminate the possibility of overwriting +secondary media with tertiary data. -The changer parameter should specify the name of a changer defined in +The dst-changer parameter should specify the name of a changer defined in &amconf;. For example: define changer vaulting_tape { @@ -78,14 +161,101 @@ define changer vaulting_tape { changerfile "vaulting-changer.conf" } + + + + + + +Cause amvault to print the dumps it would vault, but not actually +perform any vaulting operations. + + + + + + +The host and disk are parsed as exact values + + + + + + +Cause amvault to attempt to move completed tertiary volumes to +import/export slots, where they can be more easily removed by an operator. + + + + + + + +Only full (level-0) dumps are copied. + + + + + label-template + +Specifies a label template which is used to generate new labels for +tertiary volumes. + + + + + + +Eliminate non-error messages, and is useful when running amvault from +cron. + + + + + src-timestamps + +Specifies the timestamps in the format 'YYYYMMDDHHMMSS' of the run to +vault, can be "latest", then the most recent amdump or amflush run will be +used. + + + + + configoption + +See the "CONFIGURATION OVERRIDE" + section in . + + + + -The label template functions identically to the label-new-tapes parameter in &amconf;. -SEE ALSO -amanda8 +EXAMPLES + +Vault all dump written to tape in the latest amdump or amflush run: + +$ amvault --src-timestamps latest --label-template "CONF-%%%" --dst-changer vault-changer CONF + + +Vault all dump written on the run of December 7 2011 12:13:14 : + +$ amvault --src-timestamps 20111207121314 --label-template "CONF-%%%" --dst-changer vault-changer CONF + + +Vault all dump dumped on any run of December 7 2011: + +$ amvault --label-template "CONF-%%%" --dst-changer vault-changer CONF \* \* 20111207 + + + + + + + +