> > I did "solve" my previous problem where one 16Gb disk was
> > getting a full dump every singe day, by deleting it from
> > my disklist. :( I never figured out why it was being dumped
> > every day.
>
> Do you have "record yes" set in your dumptype(s)? What are
> dumpcycle, tapecycle, runspercycle, and runtapes set to?
dumpcycle 2 weeks
runspercycle 10
tapecycle 22 tapes
"record yes" is on in my dumptype global, and not over-ridden anywhere.
I should mention that I have 3 configurations for amanda: Daily, archive,
and mirror. Daily is what you expect, archive is a full dump for off-site
storage, and mirror is a full dump for off-site of just that one server (a
linux box that rsync's the local Win2K boxes once a day). The full dump
set-ups have "record no", following advice I found on this list. Could they
be interfering?
> > Is there a way I can get amanda to tell me how many tapes I
> > need? She should be able to report how many Gbs of each
> > level there were to be dumped each day.
> The command "amadmin yourconfig balance" informs you about the
> size of full backups it did (or will do) on each day in your
> cycle.
%amadmin Daily balance
new disk server:/usr/local ignored.
new disk server:/var/mail ignored.
new disk server:/etc ignored.
new disk server:/data/pnw ignored.
new disk server:/data/usgs ignored.
...many more like this -- lots never got dumped...
due-date #fs orig KB out KB balance
-------------------------------------------
7/17 Wed 29 18968010 18968448 +50.8%
7/18 Thu 0 0 0 ---
7/19 Fri 2 20302290 20302336 +61.5%
7/20 Sat 0 0 0 ---
7/21 Sun 0 0 0 ---
7/22 Mon 3 14186670 14186688 +12.8%
7/23 Tue 2 1014600 1014624 -91.9%
7/24 Wed 2 172740 172768 -98.6%
7/25 Thu 6 989530 989632 -92.1%
7/26 Fri 4 29481800 29481856 +134.4%
7/27 Sat 0 0 0 ---
7/28 Sun 0 0 0 ---
7/29 Mon 2 7050580 7050624 -43.9%
7/30 Tue 6 16981300 16981408 +35.0%
7/31 Wed 1 16601290 16601312 +32.0%
-------------------------------------------
TOTAL 57 125748810 125749696 12574969 (estimated 10 runs per
dumpcycle)
(8 filesystems overdue, the most being overdue 34 days)
Ok, so she's very much out of balance. And she dumped 126Gb during my
2-week dumpcycle. 22 tapes * 40Gb per tape (about) is 880Gb, definitely
enough. But this does not really say how much data was level 0, and how
much was level 1, etc.
I run "amoverview Daily" and noticed (in addition to lots of strings of E's
for other disks)
date 06 06 06 07 07 07 07 07 07 07 07 07 07 07 07
07 07 07 07
host disk 28 29 30 01 02 03 04 05 06 07 08 09 10 11 12
13 14 15 16
server /data/ds353.4_upa 1 1 1 1 1 1 1 1 1
1 1
So it looks like this disk is getting an incremental dump nearly everyday.
These files are static, and haven't changed in >6 months. This disk
contains only 302Mb, but perhaps this is a symptom of a larger problem?
> > I have about 170Gb of data to be backed up right now, and
> > 22 40Gb DLT8000 tapes in my tape cycle (2 weeks; 2 tapes
> > per day). How can I figure out if that's enough?
>
> How are you doing the 2 tapes per day?
I lie to amanda, and tell here there's one tape of size 80Gb, and run
amflush manually each day when I get in to the office. If I were running 1
tape per day with a 4 week tape cycle, and I'm actually generating more than
40Gb per day of level 1, then there will be no space left ever to do the
level 0 dumps, right?
runtapes 1
tapetype DLT8000x2
define tapetype DLT8000x2 {
comment "Two tapes on DLT8000 40 Gb Hardware Compression"
length 78000 mbytes
filemark 2362 kbytes
speed 20000 kps
}
Bart
--
Bart Brashers MFG Inc.
Air Quality Meteorologist 19203 36th Ave W Suite 101
[EMAIL PROTECTED] Lynnwood WA 98036-5707
http://www.mfgenv.com 425.921.4000 Fax: 425.921.4040
