Mario Lobo (sent by Nabble.com) wrote:

Hi;

I have a 400 Gig HD divided into 6 56 Gig virtual tapes. A full dump of all
9 servers on our network, which runs perfectly, fills tape1 and tape2 and
3.8 Gigs of tape3. When the full dump is finished, the changer switches to
tape4 automaticaly for the next dump (incremental).

My question is: Is it possible for amanda not to switch to tape4 and,
instead, use the remainder of tape3, without erasing the 3.8 gig that's
already there ?

Thanks
tk

Another question: Based on the above result, are these settings in my
amanda.conf proper?

dumpuser "amanda"                                                               
      # the user to run dumps under
inparallel 5                                                                    
        # maximum dumpers that will run in parallel (max 63)
dumporder "SSSSS"
taperalgo largestfit
# inparallel 10                                                                 
        # maximum dumpers that will run in parallel (max
63)
# dumporder "tttTTTTTTT"
# taperalgo first                                                               
        # The algorithm used to choose which dump image to
send
displayunit "k"                                                                           
    # Possible values: "k|m|g|t"
netusage 100000                                                                 
        # maximum net bandwidth for Amanda, in KB per sec
maxdumps 1

dumpcycle 7                                                                     
                # the number of days in the normal dump cycle
runspercycle 5                                                                  
# the number of amdump runs in dumpcycle days
tapecycle 6                                                                     
        # the number of tapes in rotation
runtapes 6
tapebufs 30
tapetype HARD-DISK
tpchanger "chg-disk"
changerfile "/amanda/daily/changer"
tapedev  "file:/bck/daily"
maxdumpsize -1                                                                  
        # Maximum number of bytes the planner will schedule
labelstr "^Tape[0-9][0-9]*$"                                          # label 
constraint regex: all tapes must
match
infofile "/amanda/daily/curinfo"                                      # 
database DIRECTORY
logdir   "/amanda/daily"                                                      # 
log directory
indexdir "/amanda/daily/index"                                                # 
index directory
tapelist "/amanda/daily/tapelist"                                     # list of 
used tapes

bumpsize 20                                     # minimum savings (threshold) to 
bump level 1 -> 2
bumppercent 20                                  # minimum savings (threshold) to 
bump level 1 -> 2
bumpdays 1                                              # minimum days at each 
level
bumpmult 4                                              # threshold = bumpsize 
* bumpmult^(level-1)

etimeout 350                                    # number of seconds per 
filesystem for estimates.

#etimeout -600                                  # total number of seconds for 
estimates.
                                                                # a positive 
number will be multiplied by the number of filesystems
on
                                                                # each host; a 
negative number will be taken as an absolute total
time-out.
                                                                # The default 
is 5 minutes per filesystem.

dtimeout 1800                                   # number of idle seconds before 
a dump is aborted.

amrecover_do_fsf yes                    # amrecover will call amrestore with the
                                                                # -f flag for 
faster positioning of the tape.

amrecover_check_label yes               # amrecover will call amrestore with the
                                                                # -l flag to 
check the label.

amrecover_changer "changer"           # amrecover will use the changer if you 
restore
                                                                # from this 
device.
                                                                # It could be a 
string like 'changer' and
                                                                # amrecover 
will use your changer if you
                                                                # set your tape 
with 'settape changer'
ctimeout 40                                             # maximum number of 
seconds that amcheck waits
                                                                # for each 
client host
autoflush yes

reserve 5

holdingdisk ad1s1d {
    comment "main holding disk"
    directory "/amanda/hold"  # where the holding disk is
    use 95000 Mb                                # how much space can we use on 
it
                                                                # a 
non-positive value means:
                                                                #        use 
all space but that value

    chunksize 0                                 # 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
}

define tapetype HARD-DISK {
        comment "Dump onto hard disk"
        length 57344 mbytes             # specified in mbytes to get the exact 
size of 58GB
}

define dumptype global {
    comment "Global definitions"
    index yes
    record yes
    holdingdisk yes
}

define dumptype full-unix {
    global
    program "GNUTAR"
    comment "FULL dump with tar and compression"
    compress server fast
    priority high
    exclude list "/usr/amanda/exclude"
    fallback_splitsize 128m
    # tape_splitsize 7000m
    # split_diskbuffer "/amanda/split"
}

define dumptype full-noex {
    global
    program "GNUTAR"
    comment "FULL dump with tar and compression but no exclusions"
    compress server fast
    priority high
    fallback_splitsize 128m
    # tape_splitsize 7000m
    # split_diskbuffer "/amanda/split"
}

define dumptype full-windows {
        global
        program "GNUTAR"
        comment "FULL Windows dump with tar and no compression"
        options no-compress
        priority high
       fallback_splitsize 128m
       # tape_splitsize 7000m
       # split_diskbuffer "/amanda/split"
}

Thanks

Mario Lobo
--
View this message in context: 
http://www.nabble.com/About-tape-usage-t1725862.html#a4689229
Sent from the Amanda - Users forum at Nabble.com.

--


Ram "TK" Krishnamurthy

Amanda Wiki: http://wiki.zmanda.com
Amanda Forums:http://forums.zmanda.com