Am Mittwoch, 15. März 2006 17:27 schrieb Jon LaBadie:
> On Wed, Mar 15, 2006 at 04:08:05PM +0100, Thomas Widhalm wrote:
> > On Wed, 2006-03-15 at 09:45 -0500, Jon LaBadie wrote:
> > > On Wed, Mar 15, 2006 at 01:03:51PM +0100, Thomas Widhalm wrote:
> > > > Here are the 2 parts of the config:
> > >
>
> > > Amazing how "simple" amanda.conf can become.
> > >
> > > I put two questions inline.
> > >
> > > || Here are the 2 parts of the config:
> > > ||
> > > || first file:
> > > || =====================
> > > ||
> > > || mailto "root"
> > > || dumpuser "amanda"
> > > || netusage 100000 Kbps
> > > || maxdumps 1
> > > ||
> > > || bumpsize 10 Mb
> > > || bumpdays 1
> > > || bumpmult 4
> > > ||
> > > || etimeout 1800
> > > ||
> > > || runtapes 1
> > > || reserve 0
> > > ||
> > > || define tapetype DEC-TZ89 {
> > > || comment "DEC TZ89 (hardware compression on: Xmn)"
> > > || length 29414 mbytes
> > > || filemark 24 kbytes
> > > || speed 1634 kps
> > > || }
> > > ||
> > > || ======================
> > > ||
> > > || and the other:
> > > ||
> > > || ======================
> > > ||
> > > || org "IS"
> > > ||
> > > || inparallel 1
> > > ||
> > > || dumpcycle 8
> > > || runspercycle 0
> > > || tapecycle 4
> > >
> > > Not sure I understand this set of parameters.
> > >
> > > runspercycle == 0 causes all level 0 dumps I believe.
> > > In that case the "length" of the dumpcycle is immaterial.
> > > Each time you run amdump, everything will get full dumps.
> >
> I know you are not using tape now, but whenever you run
> amcheck (you do don't right?) it will complain tapecycle
> less than runspercycle.
I do call amcheck from a script (just su's to amanda and then runs amcheck. It
doesn't complain.
>
> > > Are you saying you plan to run amdump once each 8 days
> > > and that you want only level 0 dumps each run?
> > >
> > > And further, you will rotate 4 tapes totaling 32 days
> > > of backups available?
> >
> > I removed all tapes from the config. I just save to the holding disk. I
> > can live with the daily "tape error", but I want amanda to do less full
> > backups.
>
> The general way to reduce full dump frequency is increase dumpcycle.
I tried this. But it just overloads my harddisks, because there are so many
level 0s.
>
> If that doesn't help then perhaps other factors are coming into play.
> For example, amanda will promote a very active DLE thinking so much
> has changed the savings of a level 1 aren't worth it, lets just do
> another level 0.
>
> Sometimes an activity on your computer will make it seem like things
> have changed when they have not. I believe gnutar relies heavily
> on the ctime parameter of unix files. Some activities affect ctime
> and could make it look like the file changes (ex. moving a file).
Hm, this can't be either. Of course, there are some hosts having a lot of
traffic, but some get level 0 on / where is exactly no traffic and no
cronjob.
>
> Other than that I don't see any reason you are not getting higher
> number levels on your holding disk. I certainly do on a new setup
> I'm testing but not providing any tapes.
A co-worker told me the same. He uses amanda in the same configuration
>
> I don't think this is the problem, but I do not see a "record yes"
> setting. I wonder if that is needed to ensure amanda knows when
> the last full dump was done? It is needed for "dump", but I'm
> uncertain about gnutar.
The docs say, record has default value "yes". I tried to include it, but
amcheck complains, that it's no valid option.
Maybe I found it deep within the comments. There is one line "reserve 0". I
can remember I changed this on the very day I got to use this server, for it
didn't backup anymore. Or maybe it was some similar option. The comments
read, that this just applies to backing up to the holding disk and "reserve
100" means, that there are just incremental backups and that a smaller value
gets amanda to do fullbackups till the holdingdisk is full. So I tried now
and set it to "reserve 50". We are very well beyond that now so amanda should
just do incremental backups by now. I can imagine that when it comes to
deleting old backups there will be enough free space for 1 or 2 level 0 for
every disk. I will test and watch because this could mean that sometimes I
miss a level 0 for a disk. Maybe a mixture of "reserver 50" and a cronjob
doing a forced full every tapecycle like somebody mentioned, will do the job.
I will report the outcome of this.
Regards,
Thomas
>
> > > || holdingdisk hd1 {
> > > || comment "main holding disk for IS"
> > > || directory "/data/amanda/IS"
> > > || use -1
> > > || chunksize 2 Gb
> > > || }
> > > ||
> > > ||
> > > || tapedev "/dev/null"
> > > || tapetype DEC-TZ89
> > >
> > > Is your DEC tapedrive really attached to the null device?
> > > Doesn't work very well that way does it? :))
> >
> > It is disconnected from the server as it produced some driver problems
> > recently. So we switched to backup to the holdingsdisk.
> >
> > > || labelstr "^IS[0-9][0-9]*$"
> > > ||
> > > || infofile "/var/lib/amanda/IS/curinfo"
> > > || logdir "/var/lib/amanda/IS"
> > > || indexdir "/var/lib/amanda/IS/index"
> > > ||
> > > || includefile "/etc/amanda/amanda-shared.conf"
> > > ||
> > > || ===================
> > > ||
> > > || the first file is used by all configs. The second one is one
> > > || specific config.
> >
> > --
> >
> >>> End of included message <<<
--
*****************************************************************
* Thomas Widhalm Unix Administrator *
* University of Salzburg ITServices (ITS) *
* Systems Management Unix Systems *
* Hellbrunnerstr. 34 5020 Salzburg, Austria *
* widhalmt AT unix.sbg.ac DOT at +43/662/8044-6774 *
* gpg: 6265BAE6 *
* http://www.sbg.ac.at/zid/organisation/mitarbeiter/widhalm.htm *
*****************************************************************
pgphIhD01mZsT.pgp
Description: PGP signature
|
