Man Linux: Main Page and Category List


       amvault - Copy Amanda dumps from one volume to another


       amvault [{-o configoption}...] [-q|--quiet] config src-run-timestamp
               dst-changer label-template


       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.

       Feedback on and patches to this application are invited and encouraged!


       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.

       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.

       The changer parameter should specify the name of a changer defined in
       amanda.conf(5). For example:

       define changer vaulting_tape {
           tapedev "/dev/rmt/1n"
           tpchanger "chg-zd-mtx"
           changerdev "/dev/sg0"
           changerfile "vaulting-changer.conf"

       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 amanda.conf(5), 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.


       amanda(8), amanda-changers(7)

       The Amanda Wiki: :


       Dustin J. Mitchell <>
           Zmanda, Inc. (