|
In the UK, we woudl flush a dump down the toilet, but not if it's too big ;-)
-----Original Message-----
From: owner-amanda-users AT amanda DOT org on behalf of KEVIN ZEMBOWER
Sent: Mon 6/21/2004 4:46 PM
To: amanda-users AT amanda DOT org
Cc:
Subject: Dealing with a dump too big
I'm trying to deal with a problem which I've just noticed. I've completely overwritten my level 0 backup of a disk called admin://db/f$. This is a SAMBA share from an NT server. I think I have complete level one backups:
amanda@admin:~ > amadmin DailySet1 find admin //db/ |fgrep //db/f$
2004-05-20 admin //db/f$ 1 DailySet109 8 OK
2004-05-21 admin //db/f$ 1 DailySet111 13 OK
2004-05-24 admin //db/f$ 1 DailySet112 7 OK
2004-05-25 admin //db/f$ 1 DailySet114 8 OK
2004-05-26 admin //db/f$ 1 DailySet115 10 OK
2004-05-27 admin //db/f$ 1 DailySet116 10 OK
2004-05-28 admin //db/f$ 1 DailySet117 8 OK
2004-05-31 admin //db/f$ 1 DailySet118 7 OK
2004-06-01 admin //db/f$ 1 DailySet119 8 OK
2004-06-02 admin //db/f$ 1 DailySet121 8 OK
2004-06-04 admin //db/f$ 1 DailySet123 9 OK
2004-06-07 admin //db/f$ 1 DailySet124 11 OK
2004-06-08 admin //db/f$ 1 DailySet125 9 OK
2004-06-09 admin //db/f$ 1 DailySet126 8 OK
2004-06-10 admin //db/f$ 1 DailySet127 12 OK
2004-06-11 admin //db/f$ 1 DailySet128 10 OK
2004-06-14 admin //db/f$ 1 DailySet101 9 OK
2004-06-15 admin //db/f$ 1 DailySet102 12 OK
2004-06-16 admin //db/f$ 1 DailySet104 10 OK
2004-06-17 admin //db/f$ 1 DailySet105 10 OK
2004-06-18 admin //db/f$ 1 --- 0 FAILED (planner) [dumps way too big, 5679359 KB, must skip incremental dumps]
2004-06-18 admin //db/f$/inetsrv 0 DailySet106 13 OK
amanda@admin:~ >
The last daily report I got, in the planner section, said:
planner: admin //db/f$ 20040618 0 [dump larger than tape, 13855177 KB, full dump delayed]
The disk F: on the NT server is indeed 13G in size, but I didn't think that would be a problem, since I excluded //db/f$/inetsrv, which is 9.1G. This filesystem, which I just backup for the first time last run, backed up at level 0 just fine:
amanda@admin:~ > amadmin DailySet1 info admin //db/
<snip>
Current info for admin //db/f$:
Stats: dump rates (kps), Full: 4221.0, 4333.0, 4412.0
Incremental: 4607.0, 4309.0, 4723.0
compressed size, Full: -100.0%,-100.0%,-100.0%
Incremental: -100.0%,-100.0%,-100.0%
Dumps: lev datestmp tape file origK compK secs
0 20040514 DailySet105 15 4621248 4622030 1095
1 20040617 DailySet105 10 5662420 5662530 1229
Current info for admin //db/f$/inetsrv:
Stats: dump rates (kps), Full: 3642.0, -1.0, -1.0
Incremental: -1.0, -1.0, -1.0
compressed size, Full: -100.0%,-100.0%,-100.0%
Incremental: -100.0%,-100.0%,-100.0%
Dumps: lev datestmp tape file origK compK secs
0 20040618 DailySet106 13 9174403 9193950 2524
amanda@admin:~ >
The pertinent sections of my disklist and amanda.conf files are:
amanda@admin:~ > grep admin /etc/amanda/DailySet1/disklist
admin //db/f$ db-f-nocomp-medpri-tar-exclude-inetsrv #DB server, Drive F: excluding \inetsrv
admin //db/f$/inetsrv nocomp-medpri-tar #DB server, Drive F:\inetsrv\
amanda@admin:~ >
>From amanda.conf:
# Special dumptypes for excluding directories
define dumptype db-f-nocomp-medpri-tar-exclude-inetsrv{
nocomp-medpri-tar
comment "Special for admin//db/f$, excluding /inetsrv/"
exclude "./inetsrv/"
}
My questions are:
1. What's the long term solution to this problem? Have I done something wrong in the amanda.conf or disklist files?
2. Is there anything I can do right now, before the nightly normal run, to get a level 0 backup of just this share?
Thanks for all your help and suggestions.
-Kevin Zembower
-----
E. Kevin Zembower
Unix Administrator
Johns Hopkins University/Center for Communications Programs
111 Market Place, Suite 310
Baltimore, MD 21202
410-659-6139
|
