Results 1 to 2 of 2

Thread: amrecover generating HUGE debug logs

  1. #1

    Angry amrecover generating HUGE debug logs

    Hello all,
    Doing a amrecover with 2.6.1p2.
    Environment Ubuntu 9.10, 16 GB ram 64bit.

    The backup is generating an amindex where each entry (one entry per file restored) is 440K bytes. This backup is 84,000 directories with 6.9 million files. At this rate the debug file alone will be over 3 terabytes. At the current rate it will take the amindex step 100 days to finish. (about 4GB a day).

    There was an old bug report in the 5.x version where the answer was upgrade to the latest as this is fixed there. The original backup was done with 2.5.x updated to 2.6.1 because of the reported fix. Unfortunately, it did not fix the issue.

    An entry looks like (patterns removed)
    1267724873.826535: amindexd: < 201- 2010-01-30-09-49-17 0 VLS317L3:4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19 ,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,3 6,37,38,39,40,41,42,43,44,45,46,47,48,49,
    ...
    40770,40771,40772,40773,40774,40775;VLS318L3:1,2,3 ,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,2 2,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38, 39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,
    ...
    36568,36569,36570,36571,36572,36573,36574,36575,36 576,36577,36578,36579,36580,36581,36582,36583,3658 4,36585,36586,36587,36588,36589,36590,36591,36592 4 /Tickets_Old/name_Pwr/Ticket_2009-08-31_15.15.33/shared/S2100/s2xmgr_java/persist/TapeDrive_19.xml

    Is there a flag to turn the debugging off? There is no way for me to restore this backup with the amrecover under the current implementation.
    disklist layout
    vlstst00 / exclude-mnt
    vlstst00 /mnt/yeast user-span-LTO3
    vlstst00 /mnt/work user-span-LTO3
    vlstst00 /mnt/backup user-span-backup
    vlstst00 /mnt/tickets/cpe user-span-LTO3
    vlstst00 /mnt/tickets/test user-span-LTO3


    amanda.conf layout
    org "supportTics" # your organization name for reports
    mailto "myemail" # space separated list of operators at your site
    dumpuser "amandabackup" # the user to run dumps under
    usetimestamps yes
    inparallel 4 # maximum dumpers that will run in parallel (max 63)
    dumporder "sssS" # specify the priority order of each dumper
    taperalgo first # The algorithm used to choose which dump image to send
    displayunit "m" # Possible values: "k|m|g|t"
    netusage 8000 Kbps # maximum net bandwidth for Amanda, in KB per sec
    dumpcycle 1 weeks # the number of days in the normal dump cycle
    runspercycle 7 # the number of amdump runs in dumpcycle days
    tapecycle 24 tapes # the number of tapes in rotation
    bumpsize 1000 Mb # 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 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
    device_output_buffer_size 1280k
    runtapes 8 # number of tapes to be used in a single run of amdump
    tpchanger "chg-zd-mtx" # the tape-changer glue script
    tapedev "/dev/nst0" # the no-rewind tape device to be used
    changerfile "/etc/amanda/backup/changer.conf"
    changerdev "/dev/sg2"
    maxdumpsize -1 # Maximum number of bytes the planner will schedule
    tapetype LTO3 # what kind of tape it is (see tapetypes below)
    labelstr "^VLS[0-9][0-9][0-9]L3*$" # label constraint regex: all tapes must match
    amrecover_do_fsf yes # amrecover will call amrestore with the
    amrecover_check_label yes # amrecover will call amrestore with the
    amrecover_changer "chg-zd-mtx" # amrecover will use the changer if you restore
    holdingdisk hd1 {
    comment "main holding disk"
    directory "/mnt/amandaTmp/amtemp" # where the holding disk is added one directory down for fix
    use -100 Mb # how much space can we use on it
    chunksize 10Gb # size of chunk if you want big dump to be
    }
    autoflush yes #
    define tapetype LTO3 {
    comment "just produced by tapetype prog (hardware compression off)"
    length 387072 mbytes
    filemark 0 kbytes
    speed 46228 kps
    }

    define tapetype LTO2 {
    comment "just produced by tapetype prog (hardware compression on)"
    length 193024 mbytes
    filemark 0 kbytes
    speed 27063 kps
    }
    define dumptype global {
    comment "Global definitions"
    }

    define dumptype exclude-mnt{
    comment "exclude /mnt from the backup"
    priority high
    program "GNUTAR"
    exclude "/mnt"
    }

    define dumptype comp-user-span-LTO3 {
    global
    tape_splitsize 50 Gb
    comment "Tape-spanning non-root partitions on reasonably fast machines for LTO3"
    compress client fast
    priority medium
    }

    define dumptype user-span-LTO3 {
    global
    tape_splitsize 50 Gb
    comment "Tape-spanning non-root partitions for LTO3"
    compress none
    priority medium
    }
    define interface local {
    comment "a local disk"
    use 1000 kbps
    }

    define interface le0 {
    comment "10 Mbps ethernet"
    use 400 kbps
    }

    And Amanda-client.conf is
    conf "backup" # your config name

    index_server "localhost" # your amindexd server
    tape_server "localhost" # your amidxtaped server
    tapedev "tape:/dev/nst0" # your tape device
    # if not set, Use configure or ask server.
    # if set to empty string "", ask server
    # amrecover will use the changer if set to the value
    # of 'amrecover_changer' in the server amanda.conf.

    # auth - authentication scheme to use between server and client.
    # Valid values are "bsd", "bsdudp", "bsdtcp", "krb5", "local",
    # "rsh" and "ssh".
    # Default: [auth "bsdtcp"]
    auth "bsdtcp"

    ssh_keys "" # your ssh keys file if you use ssh auth

    I will be glad to post any additional data that you think might help. Thanks for your time on this!!

  2. #2
    Join Date
    Nov 2005
    Location
    Canada
    Posts
    1,049

    Default

    logging is reduced in the next release.
    You should increase the tape_splitsize/fallback_splitsize, backup and recovery will be faster.

Tags for this Thread

Posting Permissions

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