Results 1 to 4 of 4

Thread: amanda 2.6p1 amrecover index not complete?

  1. #1
    Join Date
    Jul 2008
    Location
    Belgium
    Posts
    4

    Default amanda 2.6p1 amrecover index not complete?

    hello
    i just setup amanda to backup 800GB of data on LTO4
    the backup runs for 11 hours and the report seems ok.
    when i try to test the backuped data , i cannot find the backuped files.
    it only shows empty directories. and only one directory is backuped.

    i have 2 partitions setup in disklist / and /data :

    /dev/sda3 46G 2.5G 42G 6% /
    udev 1014M 124K 1014M 1% /dev
    /dev/sda1 99M 12M 83M 13% /boot
    /dev/mapper/data-data01
    3.4T 816G 2.6T 25% /data

    for test purposes i created a disklist with only one 200MB folder (/data/tools) and with this disklist the files are visibles with amrecover.

    the backuped size reported does not match the data on /data
    what is the problem ? (data partition too big for the LTO4)

    thanks for any advices.


    -------------------------------------------------------------------------
    email report
    -------------------------------------------------------------------------

    Hostname: bkplin01
    Org : backup
    Config : fullbackup
    Date : July 15, 2008

    These dumps were to tape FULLBACK-01.
    The next tape Amanda expects to use is: FULLBACK-01.


    STATISTICS:
    Total Full Incr.
    -------- -------- --------
    Estimate Time (hrs:min) 0:03
    Run Time (hrs:min) 11:17
    Dump Time (hrs:min) 11:11 11:11 0:00
    Output Size (meg) 361817.9 361817.9 0.0
    Original Size (meg) 1348679.5 1348679.5 0.0
    Avg Compressed Size (%) 26.8 26.8 --
    Filesystems Dumped 2 2 0
    Avg Dump Rate (k/s) 9196.3 9196.3 --

    Tape Time (hrs:min) 11:09 11:09 0:00
    Tape Size (meg) 361817.9 361817.9 0.0
    Tape Used (%) 46.9 46.9 0.0
    Filesystems Taped 2 2 0

    Chunks Taped 2 2 0
    Avg Tp Write Rate (k/s) 9234.6 9234.6 --

    USAGE BY TAPE:
    Label Time Size % Nb Nc
    FULLBACK-01 11:09 370501512k 46.9 2 2


    NOTES:
    planner: tapecycle (1) <= runspercycle (1)
    planner: Adding new disk nsilbkplin01:/data.
    planner: Adding new disk nsilbkplin01:/.
    big estimate: bkplin01 /data 0
    est: 529244544k out 369666300k
    big estimate: bkplin01 / 0
    est: 1012896k out 835212k


    DUMP SUMMARY:
    DUMPER STATS TAPER STATS
    HOSTNAME DISK L ORIG-kB OUT-kB COMP% MMM:SS KB/s MMM:SS KB/s
    -------------------------- ------------------------------------- -------------
    bkplin01 / 0 2018400 835212 41.4 2:59 4672.2 0:13 62303.5
    bkplin01 /data 0 1379029380 369666300 26.8 668:29 9216.4 668:28 9216.8

    (brought to you by Amanda version 2.6.0p1)
    ------------------------------------------------------------------------
    amanda.conf
    ------------------------------------------------------------------------

    org "backup" # Title of report
    mailto "root " # recipients of report, space separated
    dumpuser "amandabackup" # the user to run dumps under
    inparallel 4 # maximum dumpers that will run in parallel
    netusage 600 # maximum net bandwidth for Amanda, in KB per sec

    # a filesystem is due for a full backup once every day
    dumpcycle 0 days # the number of days in the fullback dump cycle
    tapecycle 1 tapes # the number of tapes in rotation
    runspercycle 1 # daily full backups
    runtapes 1

    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

    tapedev "tape:/dev/nst0" # Linux @ tuck, important: norewinding

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

    holdingdisk hd1 {
    comment "Temporary holding space"
    directory "/var/tmp/amanda"
    use 5000 MB
    }

    # diskdir "/var/tmp/amanda" # where the holding disk is
    # disksize 2000 MB # how much space can we use on it
    infofile "/var/lib/amanda/fullbackup/curinfo" # database filename
    #logfile "/var/log/amanda/fullbackup/log" # log filename

    indexdir "/var/lib/amanda/fullbackup/index"

    define tapetype HP-ULTRIUM4 {
    comment "HP Ultrium 4-SCSI (compression off)"
    length 772096 mbytes
    filemark 0 kbytes
    speed 75283 kps
    }

    define dumptype root-tar {
    program "GNUTAR"
    compress client fast
    comment "root partition dump with tar"
    index
    dumpcycle 0
    exclude list "/etc/amanda/fullbackup/fullbackup.exclude"
    priority high
    auth "bsdtcp"
    }

  2. #2

    Default Need more information.

    From the e-mail output you provided, it looks like Amanda gathered a total of 1.4 GB from /data, and then compressed that down to about 370GB. Is it possible that there was some job going on at the same time that generated a lot of data? There must have been some files to match that quantity of data; can you elaborate on how you know that you "cannot find the backuped files."?

    Also, you are using an exclude list. Please check that the exclude list does not match data that you wanted backed up.

  3. #3
    Join Date
    Jul 2008
    Location
    Belgium
    Posts
    4

    Default

    my exclude list file :

    # more /etc/amanda/fullbackup/fullbackup.exclude
    /proc/

    #

    here's the ls output from amrecover :

    2008-07-16-18-51-54 bacula/
    2008-07-16-18-51-54 amanda/
    2008-07-16-18-51-54 LSI/
    2008-07-16-18-51-54 Docs/
    2008-07-16-18-51-54 .
    lines 1-5/5 (END)

    here's the output of ls :

    # ls -l /data/tools
    total 79992
    drwxr-xr-x 4 root root 4096 Jun 20 19:13 Docs
    -rw-r--r-- 1 root root 8777769 Jun 20 19:18 FSC_ServerViewAgentsLinuxforSuSE_46018_1022234.zip
    -rw-r--r-- 1 root root 13624523 Jun 20 19:12 FSC_ServerViewRAIDManager_3010_1021648.zip
    drwxr-xr-x 3 root root 4096 Jun 23 18:35 LSI
    -rw-r--r-- 1 root root 11668658 Apr 15 00:00 ServerView_RAID-3.00-10.i386.rpm
    drwxr-xr-x 3 root root 4096 Jul 15 16:14 amanda
    drwxr-xr-x 2 root root 4096 Jul 4 17:11 bacula
    -rwxr-xr-x 1 root root 19210126 Jun 20 19:24 jre-6u6-linux-i586-rpm.bin
    -rw-r--r-- 1 root root 19458294 Mar 25 11:42 jre-6u6-linux-i586.rpm
    -rw-r--r-- 1 root root 55179 Apr 30 00:00 readme_V4.60-18.txt
    -rw-r--r-- 1 root root 5313274 Apr 30 00:00 srvmagt-agents-4.60-18.suse.rpm
    -rw-r--r-- 1 root root 3268611 Apr 30 00:00 srvmagt-eecd-4.60-18.suse.rpm
    -rw-r--r-- 1 root root 85685 Apr 30 00:00 srvmagt-mods_src-4.60-18.suse.rpm
    -rw-r--r-- 1 root root 193760 Apr 30 00:00 srvmagt-scs-4.60-18.suse.rpm
    -rw-r--r-- 1 root root 12633 Apr 30 00:00 srvmagt.8.html
    -rw-r--r-- 1 root root 62165 Apr 30 00:00 srvmagt.sh
    bkplin01:~ #

    on another directory (/data/san_backup) from amrecover
    ... some dir
    2008-07-16-18-51-54 UBCD4Win306_MTR_2K3.iso
    2008-07-16-18-51-54 AS2K315/

    these two last item from the directory have been backed up.

    is it possible that the two last item from this list have overwriten the same backup because there isn't enough space left on the tape? (i only setup a 1 tape scheme)

    planner: tapecycle (1) <= runspercycle (1)

    the size of my backup :

    #du -sh /data
    816G /data

    my tapetype definition : length 772096 mbytes

    define tapetype HP-ULTRIUM4 {
    comment "HP Ultrium 4-SCSI (compression off)"
    length 772096 mbytes
    filemark 0 kbytes
    speed 75283 kps
    }

    what do you think?

  4. #4
    Join Date
    Jul 2008
    Location
    Belgium
    Posts
    4

    Default

    i forgot to use manual tape changer and using a tape splitsize.
    but now i added those parameters, the backup seems to be very very slow.
    (3 days for 800 GB on LTO4) and it have yet to finish.

    i setup the holding disk to use all but 5Gigs on my 40 GB disk , but during the backup the used size does not grow.
    i presume amanda isn't using holding disk. and maybe generating the slow speed issue.
    What can be the problem?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •