X-Git-Url: https://git.gag.com/?a=blobdiff_plain;ds=sidebyside;f=man%2Fxml-source%2Famvault.8.xml;h=eed3375a334dcf923cb45e078700f3ea50775c8c;hb=b116e9366c7b2ea2c2eb53b0a13df4090e176235;hp=3f83662d8f7ba80882fd72a610e6aa776a0258a6;hpb=fd48f3e498442f0cbff5f3606c7c403d0566150e;p=debian%2Famanda diff --git a/man/xml-source/amvault.8.xml b/man/xml-source/amvault.8.xml index 3f83662..eed3375 100644 --- a/man/xml-source/amvault.8.xml +++ b/man/xml-source/amvault.8.xml @@ -27,26 +27,48 @@ amvault &configoverride.synopsis; - -q|--quiet + -q --quiet + -n --dry-run + --fulls-only + --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! @@ -55,19 +77,48 @@ 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 +. If is +"latest", then the most recent amdump or amflush run will be used. If + is given, then only full (level-0) dumps are +copied. + +The () option will +eliminate non-error messages, and is useful when running amvault from +cron. The () option will +cause amvault to print the dumps it would vault, but not actually perform +any vaulting operations. + +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. -In a vaulting operation, the source media is referred to as "secondary -media", while the destination is referred to as "tertiary media". + -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. +Tertiary Media + +The must be specified, and names 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 &amconf;. For example: @@ -80,21 +131,37 @@ define changer vaulting_tape { } -The --quiet option reduces the verbosity of the -utility; this can be useful for volumes containing many split parts. The ---autolabel option defines which tertiary volumes -amlabel will overwrite. It can have any of the values defined for -autolabel in , -with the addition of "this_config", meaning volumes matching the labelstr -for this configuration. The option defaults to "empty". Multiple -values can be separated with commas. The label template functions -identically to the template for teh autolabel -parameter. +The option is required, and specifies a +label template which is used to generate new labels for tertiary volumes. +The option works just like the +autolabel parameter in &amconf;, and can be +specified multiple times if necessary. The default is 'empty'. + +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 ... + + +The option will cause amvault to attempt to move +completed tertiary volumes to import/export slots, where they can be +more easily removed by an operator. + + +