-Chapter 13. How to use the AMANDA file-driver
+Chapter 13. How to use the Amanda file-driver
Prev Part III. HOWTOs Next
-------------------------------------------------------------------------------
-Chapter 13. How to use the AMANDA file-driver
+Chapter 13. How to use the Amanda file-driver
Stefan G. Weichinger
Refer to http://www.amanda.org/docs/howto-filedriver.html for the current
version of this document.
-This document covers the use of the file-driver in AMANDA 2.4.3 and higher.
+This document covers the use of the file-driver in Amanda 2.4.3 and higher.
Examples given here have been taken from a SuSE-Linux-8.2-Pro-environment,
-using AMANDA 2.4.4p1 and the snapshot 2.4.4p1-20031202. Please adjust paths,
+using Amanda 2.4.4p1 and the snapshot 2.4.4p1-20031202. Please adjust paths,
configuration names and other parameters to your system.
Stefan G. Weichinger, November - December, 2003 ; minor updates in April, 2005.
Introduction
-Since release 2.4.3 AMANDA supports the usage of a output driver called "file".
+Since release 2.4.3 Amanda supports the usage of a output driver called "file".
See man amanda, section OUTPUT DRIVERS, for more information on its
implementation. As the name suggests, this driver uses files as virtual (or
file) tapes. Once created and labeled, these file tapes can be selected and
-changed with the standard tape-changer-interface of the AMANDA server.
+changed with the standard tape-changer-interface of the Amanda server.
Possible Uses
* test installations
- You can easily explore the rich features of AMANDA on systems without tape
+ You can easily explore the rich features of Amanda on systems without tape
drives.
* cheap installations
- Without buying a tape drive you can enjoy the benefits of AMANDA and backup
+ Without buying a tape drive you can enjoy the benefits of Amanda and backup
to a bunch of harddisks. You can create CD/DVD-sized backups which you can
burn onto optical disks later.
* disk-based installations
You can use the file-driver to backup onto a set of file tapes hosted on a
- bunch of hard-disks or a RAID-system. Combined with another AMANDA-
+ bunch of hard-disks or a RAID-system. Combined with another Amanda-
configuration that dumps the file tapes to real tapes, you can provide
reliable backup with faster tapeless recovery. This is called "disk-to-disk-
to-tape"-backup by some people today.
Basics
-This guide assumes you have setup the basic AMANDA-services as described in
+This guide assumes you have setup the basic Amanda-services as described in
Amanda_Installation_Notes
The configuration in this HOWTO is called "daily". The file tapes are also
called vtapes in this document, which stands for "virtual tapes".
several file systems and hard disks, I recommend to dedicate at least a
specific partition, better a specific physical harddisk to the task of keeping
your vtapes. The use of a dedicated disk will speed things up definitely.
-The disk space you dedicate for your vtapes should NOT be backed up by AMANDA.
+The disk space you dedicate for your vtapes should NOT be backed up by Amanda.
Also, for performance reasons there should be NO holding disks on the same
partition as the vtapes, preferably not even on the same physical drive.
If you only have one harddisk, it will work out, too, but you will suffer low
(Available Space * 0.9) >= tapelength * tapecycle
This is a very conservative approach to make sure you don´t suffer any
performance drop due to a nearly-full-filesystem.
- As it is uncommon for AMANDA to fill, or almost fill an entire tape you
+ As it is uncommon for Amanda to fill, or almost fill an entire tape you
may also wish to use more space than that.
So you could determine possible combinations of tapelength/tapecycle with
the more general formula:
You don´t have to specify the parameter speed (as it is commonly listed in
- tapetype definitions and reported by the program amtapetype). AMANDA does
+ tapetype definitions and reported by the program amtapetype). Amanda does
not use this parameter right now.
There is also an optional parameter filemark, which indicates the amount
- of space "wasted" after each tape-listitem. Leave it blank and AMANDA uses
+ of space "wasted" after each tape-listitem. Leave it blank and Amanda uses
the default of 1KB.
4. Think about tapechangers.
As you will use a set of vtapes, you have to also use a kind of vtape-
- changer. There are several tape-changer-scripts included in the AMANDA-
- tarball. Read more about tape-changer-scripts in AMANDA_Tape_Changer
+ changer. There are several tape-changer-scripts included in the Amanda-
+ tarball. Read more about tape-changer-scripts in Amanda_Tape_Changer
Support.
Right now there are two scripts that can be used with vtapes. These
scripts take different approaches to the handling of tapes.
chg-multi simulates multiple tape drives with one tape in each drive. chg-
disk simulates one tape-library with multiple tapes in.
As chg-multi exists for a much longer time than chg-disk, it is still used
- in many AMANDA-vtape-installations.
+ in many Amanda-vtape-installations.
chg-disk was introduced with the snapshot 20031202. Contrary to chg-multi,
which is a generic changer-script that must be somewhat adjusted to the
use of the file-driver, chg-disk offers exactly the behavior needed for
handling vtapes
IMHO the approach is much more logical, so I recommend to use chg-disk in
- new AMANDA-vtape-installations.
+ new Amanda-vtape-installations.
Note
This reflects the use of your defined tapetype.
- The parameter tapecycle tells AMANDA how much tapes can be used, Set this
+ The parameter tapecycle tells Amanda how much tapes can be used, Set this
value according to the number of tapes you want to use.
The parameter tapetype , points to the tapetype definition you have
created before.
- The parameter tpchanger tells AMANDA to use the generic tape-changer-
+ The parameter tpchanger tells Amanda to use the generic tape-changer-
script to handle the vtapes. You can think of it as a virtual tape-
changer-device.
The parameter changerfile is used to give chg-disk the "prefix" for the
$ ln -s /amandatapes/daily/slot1 /amandatapes/daily/data
- Make sure the AMANDA-user has write-permissions on these directories:
+ Make sure the Amanda-user has write-permissions on these directories:
$ chown -R amanda_user /amandatapes
$ chgrp -R amanda_group /amandatapes
7. Label the virtual tapes.
- As the virtual tapes are handled just like physical tapes by the AMANDA-
+ As the virtual tapes are handled just like physical tapes by the Amanda-
Server they have to be labeled before use.
Usage: amlabel [-f] <conf> <label> [slot <slot-number>]
amanda.conf. Consult the amlabel-man-page for details.
8. Test your setup with amcheck.
Run amcheck daily (or, more general, amcheck <config>) and look for
- anything AMANDA complains about.
+ anything Amanda complains about.
A proper output looks like:
$ amcheck daily
# /usr/local/amanda/sbin/amrecover woo
AMRECOVER Version 2.4.4p3. Contacting server on backupserver.local ...
- 220 backupserver AMANDA index server (2.4.4p3) ready.
+ 220 backupserver Amanda index server (2.4.4p3) ready.
200 Access OK
Setting restore date to today (2004-10-08)
200 Working date set to 2004-10-08.
200 Good bye.
Nothing spectacular? The trick is this:
-When AMANDA asks you
+When Amanda asks you
Load tape B3_14 now Continue [?/Y/n/s/t]?
-------------------------------------------------------------------------------
Prev Up Next
-Chapter 12. AMANDA on Cygwin HOWTO Home Chapter 14. AFS HOWTO
+Chapter 12. Amanda on Cygwin HOWTO Home Chapter 14. AFS HOWTO
projects / debian / amanda / blobdiff