On Friday 11 October 2002 06:22, O-Zone wrote:
>Hi All,
>i'm a new user Amanda user. I've got installed 2.4.3 and i'm
> unable to get it working correctly. I've got a SCSI TAPE STREAMER
> Sony SDT-9000 with Sequential-Access attacched to scsi tape
> device st0. There's no disk tape changer. So i'll try to
> configure Amanda,removing all unused files in
> /usr/local/etc/amanda/Daily, in that way:
>
>-------------------------------------- amanda.conf
># MOON.TDSIENA.IT
>org "Daily"            # your organization name for reports
>mailto "[EMAIL PROTECTED]"          # space separated list of operators
> at your site
>dumpuser "backup"      # the user to run dumps under
>
>inparallel 4           # maximum dumpers that will run in parallel (max 63)
>                       # this maximum can be increased at compile-time,
>                       # modifying MAX_DUMPERS in server-src/driverio.h
>dumporder "sssS"       # specify the priority order of each dumper
>                       #   s -> smallest size
>                       #   S -> biggest size
>                       #   t -> smallest time
>                       #   T -> biggest time
>                       #   b -> smallest bandwitdh
>                       #   B -> biggest bandwitdh
>                       # try "BTBTBTBTBTBT" if you are not holding
>                       # disk constrained
>netusage  600 Kbps     # maximum net bandwidth for Amanda, in KB per
> sec
############################################
>
>dumpcycle 1 weeks      # the number of days in the normal dump cycle
>runspercycle 5          # the number of amdump runs in dumpcycle
> days # (4 weeks * 5 amdump runs per week -- just weekdays)
>tapecycle 5 tapes      # the number of tapes in rotation
>                       # 4 weeks (dumpcycle) times 5 tapes per week (just
>                       # the weekdays) plus a few to handle errors that
>                       # need amflush and so we do not overwrite the full
>                       # backups performed at the beginning of the previous
>                       # cycle
###########################################
The above setup, while it will work, is considered to be dangerous 
to your data because you will at any one time, be over-writing your 
only copy of last weeks work with the current work.  If you were to 
have a power outage in the middle of writing a tape, the whole 
thing is blown.  Its considered to be good practice to have at 
least 2x or more runspercycle tapes in tapecycle.  These tapes are 
quite inexpensive so get another 10 pack so you'll have spares, 
putting say 7 or 8 of them into the tapecycle.  By doing this, you 
are assured of haveing a full backup of the system at least 2 
dumpcycles deep.

>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)
>etimeout 300           # number of seconds per filesystem for estimates.
>dtimeout 1800          # number of idle seconds before a dump is aborted.
>ctimeout 30            # maximum number of seconds that amcheck waits
>                       # for each client host
>tapebufs 20
^^^^^^^^^^^^^^^^
This can be run up a ways if you have plenty of ram, I use 60 here 
with half a gig of ram.

>runtapes 1             # number of tapes to be used in a single run of amdump
Your tapetype is only a 2gigger, is this big enough?

>tpchanger "chg-manual" # the tape-changer glue script
^^^^^^^^^^^^^^^^^^^^
if runtapes is 1 then comment the above line out, else if it needs 
more than one tape in runtapes, use chg-manual but that will 
require your presence at change time.

>tapedev "/dev/st0"             # the no-rewind tape device to be used
But you have specified the rewinding device here, it should be 
/dev/nst0.  Using st0 is a big non-no.
-----------------------------
you don't need any of this from here
>rawtapedev "/dev/nftape"       # the raw device to be used (ftape only)
>changerfile "/usr/local/etc/amanda/Daily/changer.conf"
>changerdev "/dev/null"
to here
------------------------------
>
>tapetype HP-DDS                # what kind of tape it is (see tapetypes below)
>labelstr "^Daily[0-9][0-9]*$"  # label constraint regex: all tapes
> must match
>
>holdingdisk hd1 {
>    comment "main holding disk"
>    directory "/home/amanda"   # where the holding disk is
>    use 640 Mb         # how much space can we use on it
>                       # a non-positive value means:
>                       #        use all space but that value
>    chunksize 1Gb      # size of chunk if you want big dump to be
>                       # dumped on multiple files on holding disks
>                       #  N Kb/Mb/Gb split images in chunks of size N
>                       #             The maximum value should be
>                       #             (MAX_FILE_SIZE - 1Mb)
>                       #  0          same as INT_MAX bytes
>    }
>
>reserve 30 # percent
># This means save at least 30% of the holding disk space for
> degraded # mode backups.
>
>autoflush no #
>infofile "/usr/adm/amanda/Daily/curinfo"       # database DIRECTORY
>logdir   "/usr/adm/amanda/Daily"               # log directory
>indexdir "/usr/adm/amanda/Daily/index" # index directory
>
>define tapetype HP-DDS {
>    comment "DAT HP-DDS tape drives"
>    length 11700 mbytes
>    filemark 230 kbytes
>    speed 1024 kbytes
>}

Humm, thats not the stock HP-DDS definition, but one for a DDS3?  
And was it made by the tapetype utility?
Was the drives compressor enabled?

># dumptypes
>
>define dumptype global {
>    comment "Global definitions"
>    # This is quite useful for setting global parameters, so you
> don't have # to type them everywhere.  All dumptype definitions
> in this sample file # do include these definitions, either
> directly or indirectly. # There's nothing special about the name
> `global'; if you create any # dumptype that does not contain the
> word `global' or the name of any # other dumptype that contains
> it, these definitions won't apply. # Note that these definitions
> may be overridden in other # dumptypes, if the redefinitions
> appear *after* the `global' # dumptype name.
>    # You may want to use this for globally enabling or disabling
>    # indexing, recording, etc.  Some examples:
>    # index yes
>    # record no
>}

You should probably uncomment the "index yes" line above as I don't 
believe that a simple "index" below is sufficient to turn it on.  
And you will need it.

>
>define dumptype always-full {
>    global
>    comment "Full dump of this filesystem always"
>    compress none
>    priority high
>    dumpcycle 0
>}
>
>define dumptype root-tar {
>    global
>    program "GNUTAR"
>    comment "root partitions dumped with tar"
>    compress none
>    index
>    exclude list "/usr/local/lib/amanda/exclude.gtar"
>    priority low
>}
>
>define dumptype user-tar {
>    root-tar
>    comment "user partitions dumped with tar"
>    priority medium
>}
>
>define dumptype high-tar {
>    root-tar
>    comment "partitions dumped with tar"
>    priority high
>}
>
>define dumptype comp-root-tar {
>    root-tar
>    comment "Root partitions with compression"
>    compress client fast
>}
>
>define dumptype comp-user-tar {
>    user-tar
>    compress client fast
>}
>
>define dumptype holding-disk {
>    global
>    comment "The master-host holding disk itself"
>    holdingdisk no # do not use the holding disk
>    priority medium
>}
>
>define dumptype comp-user {
>    global
>    comment "Non-root partitions on reasonably fast machines"
>    compress client fast
>    priority medium
>}
>
>define dumptype nocomp-user {
>    comp-user
>    comment "Non-root partitions on slow machines"
>    compress none
>}
>
>define dumptype comp-root {
>    global
>    comment "Root partitions with compression"
>    compress client fast
>    priority low
>}
>
>define dumptype nocomp-root {
>    comp-root
>    comment "Root partitions without compression"
>    compress none
>}
>
>define dumptype comp-high {
>    global
>    comment "very important partitions on fast machines"
>    compress client best
>    priority high
>}
>
>define dumptype nocomp-high {
>    comp-high
>    comment "very important partitions on slow machines"
>    compress none
>}
>
>define dumptype nocomp-test {
>    global
>    comment "test dump without compression, no /etc/dumpdates
> recording" compress none
>    record no
>    priority medium
>}
>
>define dumptype comp-test {
>    nocomp-test
>    comment "test dump with compression, no /etc/dumpdates
> recording" compress client fast
>}
>
>define interface local {
>    comment "a local disk"
>    use 1000 kbps
>}
>
>define interface le0 {
>    comment "10 Mbps ethernet"
>    use 400 kbps
>}
>
>---------------------------
>and the disklist that seems to be correct.
>
>When i try to launch amcheck -m Daily it ask me for "Insert tape
> disk into slot 1 and press RETURN" and i can press return while
> the day end but no other message jumps off !
>
>What's wrong ?

See comments liberally sprinkled about above.

>Tnx !

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.18% setiathome rank, not too shabby for a WV hillbilly

Reply via email to