How To:Using removable hard disk changers as Virtual tapes: Difference between revisions

From wiki.zmanda.com
Jump to navigation Jump to search
No edit summary
(Grammar cleanup.)
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
New feature in amanda-3.3
This feature is available from Amanda 3.3


Amanda can easily use removable hard disk as virtual tapes, the user only needs to mount/umount the hard disk.
Amanda can back up to removable hard disk changers by treating them as virtual tapes. The user has to load and unload hard disks. Here is the amanda.conf configuration for removable hard disk changers.


   autolabel "AMANDA-%%%" any
   autolabel "$m-%%%" any
   meta-autolabel "META-%%%"
   meta-autolabel "$c-%%%"
   define changer removable-disk {
   define changer removable-disk {
     tpchanger "chg-disk:/amanda/diskchanger"
     tpchanger "chg-disk:/amanda/diskchanger"
Line 10: Line 10:
     property "AUTO-CREATE-SLOT" "yes"
     property "AUTO-CREATE-SLOT" "yes"
     property "REMOVABLE" "yes"
     property "REMOVABLE" "yes"
    property "MOUNT" "yes"
    property "UMOUNT" "yes"
    property "UMOUNT-LOCKFILE" "/etc/amanda/CONF/disk.lock"
    property "UMOUNT-DELAY" "1"
   }
   }
   tpchanger "removable-disk"
   tpchanger "removable-disk"


* Four slots (NUM-SLOT) is automatically created (AUTO-CREATE-SLOT) on each mounted disk.
* Four slots (NUM-SLOT) are automatically created (AUTO-CREATE-SLOT) on each mounted disk.
* Each slot (autolabel) is labelled with a distinct label.
* Each slot (autolabel) is labelled with a distinct label.
* The REMOVABLE property check that something is mounted.
* The REMOVABLE property requires amanda to check that something is mounted.
* Each hard disk get a meta label. In the future, amanda will be able to ask to mount the disk with the meta label when it require a specific label.
* Each hard disk get a [[meta label]]. In the future, amanda will be able to ask to mount the disk with the meta label when it require a specific label.
 
* Mount (MOUNT) the disk if it is not already mounted. The system must be configured to allow the amanda user to do it.
= Assigning meta label to already labelled volumes =
* Umount (UMOUNT) the disk when the program exit.
If you already use removable hard disk, these disk don't have a meta label, you can easily assign a meta label to each label with the amlabel command
* Amanda needs a lock file (UMOUNT-LOCKFILE) to do safe umount.
  amlabel <conf> <label> --meta <meta-label> --assign
* Umount the disk after (UMOUNT-DELAY) second(s) when the disk is not in use. A value of '0' leads to unnecessary umount/mount.
You must assign the same meta label to all label on the same removable hard disk.

Latest revision as of 17:03, 1 April 2011

This feature is available from Amanda 3.3

Amanda can back up to removable hard disk changers by treating them as virtual tapes. The user has to load and unload hard disks. Here is the amanda.conf configuration for removable hard disk changers.

 autolabel "$m-%%%" any
 meta-autolabel "$c-%%%"
 define changer removable-disk {
    tpchanger "chg-disk:/amanda/diskchanger"
    property "NUM-SLOT" "4"
    property "AUTO-CREATE-SLOT" "yes"
    property "REMOVABLE" "yes"
    property "MOUNT" "yes"
    property "UMOUNT" "yes"
    property "UMOUNT-LOCKFILE" "/etc/amanda/CONF/disk.lock"
    property "UMOUNT-DELAY" "1"
 }
 tpchanger "removable-disk"
  • Four slots (NUM-SLOT) are automatically created (AUTO-CREATE-SLOT) on each mounted disk.
  • Each slot (autolabel) is labelled with a distinct label.
  • The REMOVABLE property requires amanda to check that something is mounted.
  • Each hard disk get a meta label. In the future, amanda will be able to ask to mount the disk with the meta label when it require a specific label.
  • Mount (MOUNT) the disk if it is not already mounted. The system must be configured to allow the amanda user to do it.
  • Umount (UMOUNT) the disk when the program exit.
  • Amanda needs a lock file (UMOUNT-LOCKFILE) to do safe umount.
  • Umount the disk after (UMOUNT-DELAY) second(s) when the disk is not in use. A value of '0' leads to unnecessary umount/mount.