disklist(5) [debian man page]
DISKLIST(5) File formats and conventions DISKLIST(5) NAME
disklist - List of partitions to back up for Amanda DESCRIPTION
The disklist file determines which disks will be backed up by Amanda. The file usually contains one line per disk: hostname diskname [diskdevice] dumptype [spindle [interface] ] All pairs [ hostname diskname ] must be unique. Lines starting with # are ignored, as are blank lines. The fields have the following meanings: hostname The name of the host to be backed up. If diskdevice refers to a PC share, this is the host Amanda will run the Samba smbclient program on to back up the share. diskname The name of the disk (a label). In most case, you set your diskname to the diskdevice and you don't set the diskdevice. If you want multiple entries with the same diskdevice, you must set a different diskname for each entry. It's the diskname that you use on the commandline for any Amanda command. Look at the example/disklist file for example. diskdevice Default: same as diskname. The name of the disk device to be backed up. It may be a full device name, a device name without the /dev/ prefix, e.g. sd0a, or a mount point such as /usr. It may also refer to a PC share by starting the name with two (forward) slashes, e.g. //some-pc/home. In this case, the program option in the associated dumptype must be entered as GNUTAR. It is the combination of the double slash disk name and program GNUTAR in the dumptype that triggers the use of Samba. dumptype Refers to a dumptype defined in the amanda.conf file. Dumptypes specify backup related parameters, such as whether to compress the backups, whether to record backup results in /var/lib/dumpdates, the disk's relative priority, etc. spindle Default: -1. A number used to balance backup load on a host. Amanda will not run multiple backups at the same time on the same spindle, unless the spindle number is -1, which means there is no spindle restriction. interface Default: local. The name of a network interface definition in the amanda.conf file, used to balance network load. Instead of naming a dumptype, it is possible to define one in-line, enclosing dumptype options within curly braces, one per line, just like a dumptype definition in amanda.conf. Since pre-existing dumptypes are valid option names, this syntax may be used to customize dumptypes for particular disks. A line break must follow the left curly bracket. For instance, if a dumptype named normal is used for most disks, but use of the holding disk needs to be disabled for the file system that holds it, this would work instead of defining a new dumptype: hostname diskname [ diskdevice ] { normal holdingdisk never } [ spindle [ interface ] ] The { must appear at the end of a line, and the } on its own line possibly followed by the spindle and interface. SEE ALSO
amanda(8), amanda.conf(5) The Amanda Wiki: : http://wiki.zmanda.com/ AUTHORS
James da Silva <jds@amanda.org> Stefan G. Weichinger <sgw@amanda.org> Dustin J. Mitchell <dustin@zmanda.com> Zmanda, Inc. (http://www.zmanda.com) Amanda 3.3.1 02/21/2012 DISKLIST(5)
Check Out this Related Man Page
AMRESTORE(8) System Administration Commands AMRESTORE(8) NAME
amrestore - low-level data-extraction from Amanda volumes SYNOPSIS
amrestore [--config config] [-r | -c | -C] [-b blocksize] [-f filenum] [-l label] [-p] [-h] [-o configoption...] [{changerspec} | {[--holding] holdingfile}] [hostname [ diskname [ datestamp [ hostname [ diskname [ datestamp ... ] ] ] ] ]] Note that this is the only Amanda command which does not take a configuration name as its first argument. DESCRIPTION
Amrestore is a very low-level tool for extracting data from Amanda volumes. It does not consult any catalog information or other metadata, basing its operations only on the headers found on the volume. This makes it an appropriate tool for bare-metal restores of an Amanda server, or other situations where the catalog is not available. See amfetchdump(8) and amrecover(8) for higher-level recoveries. The tool does not reassemble split dumps, but can uncompress compressed dumps. Note that decompression may fail for split parts after the first. If this occurs, extract the parts without decompressing, concatenate them, and decompress the result. Data is restored from the current volume in changerspec, or from the holding file holdingfile. In most cases, changerspec will name a particular device, e.g., tape:/dev/nst0 or s3:mybucket/tape-1. Only dumps matching the dump specification beginning with hostname are extracted. If no specification is given, every file on the volume (or the entire holdingfile) is restored. See the "DUMP SPECIFICATIONS" section of amanda-match(7) for more information. Unless -p is used, candidate backup images are extracted to files in the current directory named: hostname.diskname.datestamp.dumplevel OPTIONS
-b blocksize Use the given blocksize to read the volume. The default is defined by the device. -f filenum Seek to file filenum before beginning the restore operation. -l label Check that the volume has label label. -p Pipe the first matching file to standard output. This is typically used in a shell pipeline to send the data to a process like tar for extraction. -c, -C If the file is not already compressed, compress it using the fastest (-c) or best (-C) compression algorithm. Note that amrestore will not re-compress an already-compressed file. Without either of these options, amrestore will automatically uncompress any compressed files. This option is useful when the destination disk is small. -h Include 32k headers on all output files, similar to a holding file. This header can be read by another application or utility (see Amanda::Header) during the next phase of processing. -r Output raw files. This is similar to -h, but also disables any automatic decompression. Output file names will have a .RAW extension. -o configoption See the "CONFIGURATION OVERRIDE" section in amanda(8). EXAMPLES
The following does an interactive restore of disk rz3g from host seine, to restore particular files. Note the use of the b option to restore, which causes it to read in units of two 512-byte blocks (1 Kbyte) at a time. This helps keep it from complaining about short reads. amrestore -p /dev/nrmt9 seine rz3g | tar -xv The next example extracts all backup images for host seine. This is a typical way to extract all data for a host after a disk crash. amrestore /dev/nrmt9 seine If the backup datestamp in the above example is 20070125 and seine has level 0 backups of disks rz1a and rz1g on the tape, these files will be created in the current directory: seine.rz1a.19910125.0 seine.rz1g.19910125.0 You may also use amrestore to extract a backup image from a holding disk file that has not yet been flushed to tape: amrestore -p /amanda/20001119/seine.rz1a.2 | tar -xv CAVEATS
GNU-tar must be used to restore files from backup images created with the GNUTAR dumptype. Vendor tar programs sometimes fail to read GNU Tar images. SEE ALSO
amanda(8), amanda-match(7), amfetchdump(8), amrecover(8) The Amanda Wiki: : http://wiki.zmanda.com/ AUTHORS
James da Silva <jds@amanda.org> Stefan G. Weichinger <sgw@amanda.org> Dustin J. Mitchell <dustin@zmanda.com> Zmanda, Inc. (http://www.zmanda.com) Amanda 3.3.1 02/21/2012 AMRESTORE(8)