Page 1 of 2 12 LastLast
Results 1 to 10 of 19

Thread: default maxdumpsize is not working ?

  1. #1
    Join Date
    Oct 2008
    Location
    Campinas-SP
    Posts
    34

    Question default maxdumpsize is not working ?

    Hi,

    I am using amanda 2.6.0p2 on a openSuse 10.2 and a 36/72 Seagate DAT tape.
    The problem is the all backup are larger than the tape and some dumps left in the holding disk even I set "runtapes 1" and the tape length is set to "length 34000 mbytes" in /etc/amanda/templates.d/tapetypes for the corresponding tapetype I am using in amanda.conf.

    Looks like the default maxdump (runtapes * tape_length) is not working. In advanced.conf "maxdumpsize is commented, so I hope the default maxdumpsize applies.

    From Amanda Mail Report:
    These dumps were to tape diario-01.
    There are 5681490G of dumps left in the holding disk.
    Run amflush to flush them to tape.

    STATISTICS:
    Total Full Incr.
    -------- -------- --------
    Estimate Time (hrs:min) 0:03
    Run Time (hrs:min) 3:57
    Dump Time (hrs:min) 0:56 0:56 0:00
    Output Size (meg) 48193.2 48070.1 123.1
    Original Size (meg) 48711.0 48446.8 264.3
    Avg Compressed Size (%) 98.3 98.7 46.0 (level:#disks ...)
    Filesystems Dumped 19 4 15 (1:15)
    Avg Dump Rate (k/s) 14656.2 14700.9 6698.6

    Tape Time (hrs:min) 3:18 3:18 0:01
    Tape Size (meg) 35218.2 35095.1 123.1
    Tape Used (%) 103.6 103.2 0.4 (level:#disks ...)
    Filesystems Taped 19 4 15 (1:15)
    (level:#chunks ...)
    Chunks Taped 19 4 15 (1:15)
    Avg Tp Write Rate (k/s) 3033.2 3031.3 3685.2

    USAGE BY TAPE:
    Label Time Size % Nb Nc
    diario-01 3:18 34G 103.6 19 19

    I expect "Output Size 48193.2" would be less or equal to tape "length 34000". Or I missed something ????!?!?

    Must I define "maxdumpsize 35651584" to get this working ?

    PS: By the way, my first attempet was with "maxdumpsize -1" what didn't work, generating a dump bigger than tape and left dumps on holding disk. "# maxdumpsize" was my seconf attempt.
    Last edited by marozsas; November 12th, 2008 at 03:45 AM. Reason: I forgot to mention "maxdumpsize -1" didn't work either.

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

    Default

    First, be sure your config is want you think it is, what's the output of the following command (replace CONF with your config name):
    amgetconf CONF maxdumpsize
    amgetconf CONF tapetype
    amgetconf CONF tapetype:`amgetconf CONF tapetype`:length
    amgetconf CONF runtapes

  3. #3
    Join Date
    Oct 2008
    Location
    Campinas-SP
    Posts
    34

    Default

    Thanks martineau for the reply.

    Sure, you are right. I will do that in any next post. Anyway, here we go:

    Code:
    # amgetconf diario maxdumpsize
    -1
    # amgetconf diario tapetype
    DAT72
    # amgetconf diario tapetype:`amgetconf diario tapetype`:length
    34816000
    # amgetconf diario runtapes
    1
    #
    just to make things clear, the previous report (backup for today) was ran with "#maxdumpsize -1" (commented)
    Code:
    > grep maxdump advanced.conf 
    #maxdumpsize -1		# Maximum number of bytes the planner will schedule
    >

  4. #4
    Join Date
    Oct 2008
    Location
    Campinas-SP
    Posts
    34

    Default

    today, the same problem: lots of dumps on holding disk even with maxdump size set to a number lower than tape length.
    The Output Size (39396.7) is bigger than maxdumpsize.
    Looks like planner is not make the right calculations.....


    Code:
    root@bigslam:~>amgetconf diario maxdumpsize
    35000000
    root@bigslam:~>amgetconf diario tapetype:`amgetconf diario tapetype`:length
    35100000
    root@bigslam:~>amgetconf diario runtapes
    1
    root@bigslam:~>
    from amanda mail report:
    Code:
    ...
    Config  : diario
    Date    : November 13, 2008
    
    These dumps were to tape diario-03.
    There are 5029403G of dumps left in the holding disk.
    Run amflush to flush them to tape.
    STATISTICS:
                              Total       Full      Incr.
                            --------   --------   --------
    Estimate Time (hrs:min)    0:03
    Run Time (hrs:min)         3:41
    Dump Time (hrs:min)        2:13       2:10       0:03
    Output Size (meg)       39396.7    36801.1     2595.6
    Original Size (meg)     66227.4    63025.6     3201.9
    Avg Compressed Size (%)    58.3       58.4       52.1   (level:#disks ...)
    Filesystems Dumped           26          7         19   (1:19)
    Avg Dump Rate (k/s)      5044.1     4834.2    13119.7
    
    Tape Time (hrs:min)        3:19       3:03       0:15
    Tape Size (meg)         35436.8    32841.2     2595.6
    Tape Used (%)             103.4       95.8        7.6   (level:#disks ...)
    Filesystems Taped            26          7         19   (1:19)
       (level:#chunks ...)
    Chunks Taped                 26          7         19   (1:19)
    Avg Tp Write Rate (k/s)  3044.5     3055.8     2908.5
    
    USAGE BY TAPE:
      Label           Time      Size      %    Nb    Nc
      diario-03       3:19       35G  103.4    26    26

    Should I report this to developrs list ?

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

    Default

    Amanda use the estimate to the the backup schedule, if the estimate are a lot smaller then the real size, the the backup will be a lot larger than the estimate size and can be more than maxdumpsize.
    Post the complete email report and the amdump.? log file

  6. #6
    Join Date
    Oct 2008
    Location
    Campinas-SP
    Posts
    34

    Default

    Hi
    The files requested are attached.
    I am sending 3 amdump files and 3 amreport files.
    This new installation started at Tuesday 11.
    I am sending, just in case, amanda.conf advanced.conf, dumptypes, and disklist.

    thanks for the help !
    Attached Files Attached Files

  7. #7
    Join Date
    Oct 2008
    Location
    Campinas-SP
    Posts
    34

    Default

    I just realized the amreport I generated a few minutes ago with "amreport diario -i -l -f " does not show that message there are files left on holding disk.
    If you think this is relevant I can send the original e-mails I received from amanda. They are in my inbox.
    Just let me known.

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

    Default

    What you see is a normal behaviour for a new config. Estimate are too small because your data doesn't compress as the default amanda compress ratio. Amanda will learn the compression ratio of your data after a few full dump of each dle.

  9. #9
    Join Date
    Oct 2008
    Location
    Campinas-SP
    Posts
    34

    Default

    uhmm... so I will set maxdumpsize to 30000000 to compensate the over estimate planner is doing and stop to use 2 tapes per day (a extra tape is needed to flush about 5Gbytes of dumps in holding disk)

    After all DLE were backup I will change maxdumpsize to the default -1 in hope planner can make a better estimative about data to backup.

    However, this is a new behaviour in 2.6.
    I was using 2.5 in the same hardware, same dles,, same tape and I didn't had this problem at beginning. I decided to upgrade to 2.6 because a well known problem in 2.5 with accent chars in name of files/directories.

    Anyway, I appreciate very much your help and I hope you are right.
    I will not close this thread right now. As soon I realize planner is doing the right calculations I post a final conclusion about this issue in hope it can help others.

    thanks again martineau !

    cheers,

  10. #10
    Join Date
    Oct 2008
    Location
    Campinas-SP
    Posts
    34

    Default

    Just an update for what happened today.
    After changing maxdumpsize to 30000000 planner is guessing wrong the size of backups an I have dumps left on holdings disk (3.3G). I will change it to 25000000 ! keep following....
    "displayunit g" is not working too. See bellow: 3452494G were in fact 3452494 bytes or 3.2G.

    Code:
    These dumps were to tape diario-05.
    There are 3452494G of dumps left in the holding disk.
    Run amflush to flush them to tape.
    
    The next tape Amanda expects to use is: 1 new tape.
    The next new tape already labelled is: diario-03.
    
    STATISTICS:
                              Total       Full      Incr.
                            --------   --------   --------
    Estimate Time (hrs:min)    0:03
    Run Time (hrs:min)         3:31
    Dump Time (hrs:min)        1:35       1:29       0:06
    Output Size (meg)       39052.0    34481.0     4570.9
    Original Size (meg)     54553.8    49298.4     5255.4
    Avg Compressed Size (%)    69.4       69.9       50.5   (level:#disks ...)
    Filesystems Dumped           34         17         17   (1:15 2:2)
    ...
    Last edited by marozsas; November 14th, 2008 at 02:48 AM.

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
  •