Amanda-Users

Re: Backup size doubled

2003-06-25 12:22:11
Subject: Re: Backup size doubled
From: "Internet Support" <help AT compmore DOT net>
To: "Paul Bijnens" <paul.bijnens AT xplanation DOT com>
Date: Wed, 25 Jun 2003 12:17:04 -0400
Here is my config file  disklist and the latest Amanda Report

inparallel 4 # maximum dumpers that will run in parallel
netusage  1000 KB # maximum net bandwidth for Amanda, in KB per sec

dumpcycle 1 week # the number of days in the normal dump cycle
tapecycle 4 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 * (level-1)**bumpmult

#tpchanger "chg-generic" # the tape-changer glue script
 tapedev "/dev/nrsa0" # or use the (no-rewind!) tape device directly

tapetype DAT # what kind of tape it is (see tapetypes below)
labelstr "^VOL[0-9][0-9]*$" # label constraint regex: all tapes must match

diskdir "/usr/amanda" # where the holding disk is
disksize 10000 MB # how much space can we use on it
#diskdir "/dumps/amanda/work" # additionaly holding disks can be specified
#disksize 1200 MB # they are used round-robin


# Amanda needs a few MB of diskspace for the log and debug files,
# as well as a database.  This stuff can grow large, so the conf directory
# isn't usually appropriate.  We use /usr/adm.  Create an amanda directory
# under there.  You need a separate infofile and logfile for each
# configuration, so create subdirectories for each conf and put the files
# there.  Specify the filenames below.

infofile "/var/log/amanda/cm02/curinfo" # database filename
logfile  "/var/log/amanda/cm02/log" # log filename
indexdir "/var/log/amanda/cm02/index"      # index directory

# tapetypes
#
# Define the type of tape you use here, and use it in "tapetype" above.
# Some typical types of tapes are included here.  The tapetype tells amanda
# how many MB will fit on the tape, how big the filemarks are, and how
# fast the tape device is.
#
# For completeness Amanda should calculate the inter-record gaps too, but it
# doesn't.  For EXABYTE and DAT tapes this is ok.  Anyone using 9 tracks for
# amanda and need IRG calculations?  Drop me a note if so.

define tapetype EXB-8500 {
    comment "Exabyte EXB-8500 drive on decent machine"
    length 4200 mbytes
    filemark 48 kbytes
    speed 474 kbytes
}

define tapetype EXB-8200 {
    comment "Exabyte EXB-8200 drive on decent machine"
    length 2200 mbytes
    filemark 2130 kbytes
    speed 240 kbytes
}

define tapetype DAT {
    comment "DAT tape drives"
    length 20000 mbytes # these numbers are not accurate
    filemark 100 kbytes # but you get the idea
    speed 100 kbytes
}

define tapetype MIMSY-MEGATAPE {
    comment "Megatape (Exabyte based) drive through Emulex on Vax 8600"
    length 2200 mbytes
    filemark 2130 kbytes
    speed 170 kbytes # limited by the Emulex bus interface, ugh
}


# dumptypes
#
# These are referred to by the disklist file.  The dumptype specifies
# certain "options" for dumping including:
# compress-fast - (default) compress on the client using fast algorithm
# compress-best - compress using the best (and slowww) algorithm
# no-compress - don't compress the dump output
# record - (default) record the dump in /etc/dumpdates
# no-record - don't record the dump, for testing
# no-hold - don't go to the holding disk, good for dumping
#   the holding disk partition itself.
# skip-full - Skip the disk when a level 0 is due, to allow
#   full backups outside Amanda, eg when the machine
#   is in single-user mode.
# skip-incr - Skip the disk when the level 0 is NOT due.  This
#   is used in archive configurations, where only full
#   dumps are done and the tapes saved.
# no-full - Do a level 1 every night.  This can be used, for
#   example, for small root filesystems that only change
#   slightly relative to a site-wide prototype.  Amanda
#   then backs up just the changes.
#
# Also, the dumptype specifies the priority level, where "low", "medium" and
# "high" are the allowed levels.  These are only really used when Amanda has
# no tape to write to because of some error.  In that "degraded mode", as
# many incrementals as will fit on the holding disk are done, higher
priority
# first, to insure the important disks are dumped first.

define dumptype comp-user-tar {
    program "GNUTAR"
    comment "partitions dumped with tar"
    options compress
    priority medium
}

define dumptype comp-user {
    comment "Non-root partitions on reasonably fast machines"
    options compress-fast
    priority medium
}

define dumptype nocomp-user {
    comment "Non-root partitions on slow machines"
    options no-compress
    priority medium
}

define dumptype holding-disk {
    comment "The master-host holding disk itself"
    options no-hold
    priority medium
}

define dumptype comp-root {
    comment "Root partitions with compression"
    options compress-fast
    priority low
}

define dumptype nocomp-root {
    comment "Root partitions without compression"
    options no-compress
    priority low
}

define dumptype comp-high {
    comment "very important partitions on fast machines"
    options compress-best
    priority high
}

define dumptype nocomp-high {
    comment "very important partitions on slow machines"
    options no-compress
    priority high
}

define dumptype nocomp-test {
    comment "test dump without compression, no /etc/dumpdates recording"
    options no-compress, no-record
    priority medium
}

define dumptype comp-test {
    comment "test dump with compression, no /etc/dumpdates recording"
    options compress-fast, no-record
    priority medium
}
---------------------------------------------------------------Disklist
# A SPARCstation 1+
host.domain.net ad0s1a nocomp-root
host.domain.net ad0s1f nocomp-user
host.domain.net ad0s1e nocomp-user


# We don't run compression on the master host since it is going to be
# busy enough running amanda.
---------------------------------------------------------------------Amanda
Report

These dumps were to tape VOL004.
*** A TAPE ERROR OCCURRED: [[writing file: short write]].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: VOL005.

FAILURE AND STRANGE DUMP SUMMARY:
 host.domain ad0s1f lev 0 FAILED [out of tape]


STATISTICS:
                          Total       Full      Daily
                        --------   --------   --------
Estimate Time (hrs:min)    0:00
Run Time (hrs:min)         4:11
Dump Time (hrs:min)        0:45       0:45       0:00
Output Size (meg)        8918.2     8918.2        0.0
Original Size (meg)      8918.2     8918.2        0.0
Avg Compressed Size (%)     --         --         -- 
Filesystems Dumped            3          3          0
Avg Dump Rate (k/s)      3354.3     3354.3        -- 

Tape Time (hrs:min)        0:01       0:01       0:00
Tape Size (meg)           100.6      100.6        0.0
Tape Used (%)               0.5        0.5        0.0
Filesystems Taped             2          2          0
Avg Tp Write Rate (k/s)  1407.6     1407.6        -- 


NOTES:
  planner: Forcing full dump of host.domain.net:ad0s1a as directed.
  planner: Forcing full dump of host.domain.net:ad0s1f as directed.
  planner: Forcing full dump of host.domain.net:ad0s1e as directed.
  taper: tape VOL004 kb 7152992 fm 3 writing file: short write
  driver: going into degraded mode because of tape error.


DUMP SUMMARY:
                                     DUMPER STATS            TAPER STATS
HOSTNAME     DISK        L ORIG-KB OUT-KB COMP% MMM:SS  KB/s MMM:SS  KB/s
-------------------------- --------------------------------- ------------
host.domain ad0s1a      0   46950  47008   --    0:163006.5   0:381227.6
host.domain ad0s1e      0   55950  56000   --    0:222499.0   0:351605.1
host.domain ad0s1f      0 90293109029310   --   44:453363.4  FAILED  ----

(brought to you by Amanda version 2.4.3)



<Prev in Thread] Current Thread [Next in Thread>