|
very large dumps in holding area
2005-04-21 10:36:23
I am having a problem with amanda leaving very large dumps in the
holding area and not writing them to tape. The tapes are 20/40GB tapes,
but a 23GB dump doesn't get written even though there is a blank tape
available. Even if I try to flush this dump, it runs for a long time and
then errors again with "No space left on device."
Here is the log that I got.
--------------------------------------------------------
The dumps were flushed to tapes Progeny01-0043, Progeny01-0044.
*** A TAPE ERROR OCCURRED: [[writing file: No space left on device]].
Some dumps may have been left in the holding disk.
Run amflush again to flush them to tape.
The next 2 tapes Amanda expects to used are: Progeny01-0020, Progeny01-0021.
FAILURE AND STRANGE DUMP SUMMARY:
morimoto /net/morimoto/home lev 5 FAILED [out of tape]
STATISTICS:
Total Full Daily
-------- -------- --------
Estimate Time (hrs:min) 0:00
Run Time (hrs:min) 3:39
Dump Time (hrs:min) 0:00 0:00 0:00
Output Size (meg) 0.0 0.0 0.0
Original Size (meg) 0.0 0.0 0.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped 0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min) 0:03 0:00 0:03
Tape Size (meg) 361.2 0.0 361.2
Tape Used (%) 2.2 0.0 2.2 (level:#disks ...)
Filesystems Taped 14 0 14 (1:13 3:1)
Avg Tp Write Rate (k/s) 2408.5 -- 2408.5
USAGE BY TAPE:
Label Time Size % Nb
Progeny01-0043 0:03 361.2 2.2 14
Progeny01-0044 0:00 0.0 0.0 0
----------------------------------------------------------------------------------------
There are two amanda directories in my holding area:
20050420 is 28G
20050421 is 3.2G
How do I get amanda to readjust what gets backed up when to make it more
even over the full tape cycle? Is it possible with amadmin? When I do an
amadmin balance, I get this:
due-date #fs orig KB out KB balance
----------------------------------------------
4/21 Thu 3 37603890 26119168 +330.0%
4/24 Sun 1 14116820 14116820 +132.4%
4/25 Mon 1 12436100 11076062 +82.3%
4/26 Tue 1 7464340 7464340 +22.9%
4/30 Sat 2 12133630 11246536 +85.1%
5/01 Sun 3 536890 452308 -92.6%
5/02 Mon 2 5105460 4698652 -22.7%
5/03 Tue 6 12883440 8596350 +41.5%
5/04 Wed 4 10457560 8194571 +34.9%
5/07 Sat 3 24676810 23458226 +286.2%
----------------------------------------------
TOTAL 26 137414940 115423033 6074896
(estimated 19 runs per dumpcycle)
(3 filesystems overdue, the most being overdue 146 days)
which doesn't seem balanced at all.
Vicki
|
|
|
