On Thu, May 22, 2003 at 07:23:59PM +0200, Per von Zweigbergk wrote:
---cut---
> From what I've understood, Amanda should be run from a cron job, for
> example at at midnight, once a day. I've also understood that you can
> configure Amanda to only run on weekdays.
>
> So, basically, the ideal scenario is to have someone go in to the
> server room every morning, remove the ejected tape from the previous
> day, and store it in a safe. The operator should then put in the next
> tape in the cycle. The operator could even take the tapes home as a
> crude off-site backup.
I do this every weekday (without the take-home part :) The job runs
every weekday morning at 02:03am. When I come in in the morning (which
varies from 6am to 11am :), the job is done, and the first thing I do
is swap the tape (I find that if I don't do it _first_thing_ it doesn't
always get done...)
amanda's crontab:
-----------------
3 2 * * 1-5 /var/lib/amanda/bin/runamanda
runamanda:
----------
#! /bin/bash
PATH=/usr/local/amanda/sbin:/usr/local/bin:/sbin:/bin:/usr/bin
if [ `id -nu` != "amanda" ] ; then
echo""
echo "ERROR: Need to run this as user amanda"
echo""
exit
fi
if [ $1 ] ; then
CONFIG=$1
else
# be sure to change the following line to
# accurately reflect the name of your default
# configuration
CONFIG=<default config name goes here>
fi
amcheck -csm $CONFIG
amdump $CONFIG
amverify $CONFIG >/dev/null 2>&1
amcheck -csm $CONFIG
> However, is it possible to tell Amanda to never ever use more than one
> tape per day, circumventing the lack of a tape changer or tape
> operator? Basically, it might be able to fully dump one filesystem, and
> only do incremental dumps on the rest of them, never performing more
> than one full dump per tape.
This is also exactly my setup. One tape per day, 5 (week)days per
week. We were doing all level zeros, but one of the filesystems has
grown too big to do this, so now we're doing incrementals as well, with
a level zero every other day for each filesystem:
from amanda.conf:
-----------------
dumpcycle 2 days # the number of days in the normal dump cycle -
# 0 = full every day
# runspercycle 5 # the number of amdump runs in dumpcycle days -
# default = same as dumpcycle
tapecycle 5 tapes # the number of tapes in rotation
bumpsize 20 Mb # minimum savings (threshold) to bump level 1 -> 2
bumpdays 1 # minimum days at each level
bumpmult 4 # threshold = bumpsize * bumpmult^(level-1)
runtapes 1 # num tapes to be used in a single run of amdump
define dumptype daily {
global
# program "DUMP" # the default
# record yes # the default
comment "daily"
compress none
priority high
# dumpcycle 2 # should be obtained from dumpcycle above
index yes
}
I'd also _highly_ recommend using a holding disk if you can.
Ours is set up as follows (again, in amanda.conf):
# Amanda by default reserves 100% of the holding disk for
# incremental backups in degraded mode. If you don't want
# those *at all*, set 'reserve 0'.
reserve 10 # percent [default = 100%]
Good luck!
--Steve Lane /"\
Doudna Lab \ / ASCII Ribbon Campaign
U. C. Berkeley X Against HTML Email
/ \
|
