|
This chapter shows settings that you
need to change to order to use DELL PowerVault 136T. We used LTO2
(200gb/400gb) drives. Daily run Amanda's configuration files are
located at /usr/local/etc/amanda/DailySet1. There are 2 files than
you need to change: changer.conf and amanda.conf
Configuring amanda.conf
Most options are fine by default, but there's a number of options
you must change:
org "Bigsoft
Home"
Put your company's name there.
mailto
"report@domain.com"
Put your email there and reports for each amanda run will be
emailed there. If you have big number of servers, you need to check
your mail server's settings to make sure it will deliver huge email
messages.
inparallel 12
Number of archiving processes running in parallel. We were
able to run 24 processes on two CPU dual core 1.8Ghz. Make sure you
have gige connection to your network because in this case backup
server may use up to 400-500mbps.
netusage
600000 Kbps
Maximum bandwidth that backup system
can use. Actually it's not hard limit. Amanda's planner will estimate
how many processes should be run in order to keep bandwidth under
this value.
etimeout 208000
If you have millions files on your
servers, you need to increase this value from default to give more
time to estimating process to calculate all your files' size.
Configuring tape changer
In this chapter we'll describe how to
confgure your amanda in order to use tape cartridges changer.
First of all, you need to change
amanda.conf as shown below
runtapes 5
Number of tapes to use per run. If this
number is lower than your daily tape usage, you will get error
message from amanda and system will become into degraded mode. You
need to adjust this value by experiencing.
tpchanger
"chg-zd-mtx"
Your tape changer type. For most
cases, chg-zd-mtx should work, and it worked for our Dell PowerVault
136-T library
tapedev
"/dev/nst0"
Path to your tape driver (not changer).
changerfile
"/usr/local/etc/amanda/DailySet1/changer"
Path to file that changer uses for
checking its status
changerdev
"/dev/sg2".
Path to changer device. You need to get
number by doing dmesg and check position that tape changer has. In
our case we had 0 as SCSI RAID, 1st was SCSI controller,
and 2nd was tape changer.
tapetype LTO2
Type of your tape cartridges. See
amanda.conf for other types if you have something different than LTO2
amrecover_changer
"chg-zd-mtx"
This line tell amrecover to use changer
'chg-zd-mtx' while recovering.
Next we need to configure changer.conf,
which is located at /usr/local/etc/amanda/DailySet1 for our
configuration. There're a few PowerVault specific options that you
need to change:
eject
> 1 # Tapedrives need an eject command
Tell changer that our tape drives
require 'eject' command in order to pull tape cartridge off.
sleep
5 # Seconds to wait until the tape gets ready
Give some time to settle tape after
loading it into tape drive
cleanmax 10
How many times we should use cleaning
cartridge. Depending on vendor it may vary so you need to consult
with manual to set correct value.
changerdev
/dev/sg0
Changer device. The same as we
configured at amanda.conf
havebarcode 1
havereader=1
As we decribed in chapter “Labeling
tape cartridges”, PowerVault 136-T has bar code reader. And this
option tells amanda to use barcode reader.
labelfile
/var/log/amanda/labelfile.txt
Path to file where our labels'
information is stored
offline_before_unload=1
offlinestatus=1
OFFLINE_BEFORE_UNLOAD=1
Configuring temporal storage
As you already know, amanda software stores data pulled from slave
servers to its own storage then writes to tape library once it's
getting full or pulling data from slave servers is finished. You need
to specify storage in Amanda's configuration. In order to do that
open amanda.conf and find the following option(s):
holdingdisk hd1
{
comment
"main holding disk"
directory
"/home/amanda" # where the holding disk is
use 300 Gb
# how much space can we use on it
chunksize
1Gb # size of chunk if you need to split huge #
backup files into small pieces.
}
You can configure many storage
subsystems. For example if you have many local hard drives configured
as non-raid.
| 
Eng
Rus
