Amanda-Users

Re: include problems with Amanda-2.4.4-20030428?

2003-11-25 10:48:25
Subject: Re: include problems with Amanda-2.4.4-20030428?
From: Jean-Francois Malouin <Jean-Francois.Malouin AT bic.mni.mcgill DOT ca>
To: amanda-users AT amanda DOT org
Date: Tue, 25 Nov 2003 10:46:33 -0500
* Martin <ammail AT sebastian DOT nl> [20031125 02:48]:
> FWIW, I am doing the same thing (splitting the stuff), my DLEs look
> something like this:
> 
> host /home/all /home {
>     always-full
>     exclude "./hugemap" "./evenhugermap" "./*/.sambarecycle"
> }
> 
> host /home/hugemap /home {
>     always-full
>     include "./hugemap"
> }
> 
> host /home/evenhugermap /home {
>     always-full
>     include "./evenhugermap"
> }

Thanks for you input, Martin. But my situation is a little bit
different than yours. in /.../assembly I have a few thousands
of subdirs, 186 of them starts with a '1'. I just calculated
their total combined size: 11286948 KB or a little less than 11GB.

OK, now look at this amanda report from last night:

---
DUMP SUMMARY:
                                  DUMPER STATS                  TAPER STATS  
HOSTNAME DISK     L    ORIG-KB     OUT-KB COMP% MMM:SS    KB/s MMM:SS    KB/s
------------------- ------------------------------------------ --------------
bullcalf -/nihpd1 2      44220      44220   --   29:04    25.4   0:10  4308.6
bullcalf -embly_0 1     120160     120160   --   22:11    90.3   0:12 10093.6
bullcalf -embly_1 0  100460112  100460112   --  277:34  6032.2 277:34  6032.2

(brought to you by Amanda version 2.4.4p1-20031120)
---

I see that /..../assembly_1 was around 98GB which is actually the
entire content of /data/nihpd/nihpd1/data/assembly.

The disklist for this directory:

bullcalf /data/nihpd/nihpd1/data/assembly_1 /data/nihpd/nihpd1/data/assembly {
include "./1*"
high-tar
} 2

hmmm, seems to me that the include thing does not behave as intended.
Maybe I'm just missing something though.

Any comments anyone? I really have to get this working asap!

thanks a million,
jf

> 
> Martin
> 
> > > > > >
> > > > > > I'm having strange problems with the include thingy in an
> > > > > > entry in my disklist:
> > > > > >
> > > > > > bullcalf /data/nihpd/nihpd1/data/assembly_0
> /data/nihpd/nihpd1/data/assembly {
> > > > > > include "./0*"
> > > > > > exclude "./[1-9]*"
> > > > > > high-tar
> > > > > > } 1
> > > > > >
> > > > > > Looking at what got written to tape (a full backup) I see only
> > > > > > directories (no files at all!), and even from the exclude
> part...ie
> > > > > > just the hierarchy structure of /data/nihpd/nihpd1/data/assembly
> all
> > > > > > the way down...
> > > > > >
> > > > >
> > > > > Don't know about your bad backup, but in your DLE you should not
> > > > > have both the include and THAT exclude.  I.e., the include will
> > > > > automatically drop any toplevel dir that does not match "./0*".
> > > >
> > > > That is want I want!
> > > > All subdirs in there have a pattern [0-9]\{6\} , ie, 6 digits. There
> > > > are other subdirs but there are not to be backed up. You see, my
> > > > problem is that /data/nihpd/nihpd1/data/assembly can contains 100's of
> > > > GB and I'm using 4 LTO tape drives, so I have to split that thing in
> > > > small chuncks...
> > > >
> > > > Eventually I'll have 10 DLE's, those starting with ./0* ./1* ...
> > > > you get the picture.
> > > >
> > > > >
> > > > > I think the only valid exclude usage would be for things under
> > > > > the 0* directories.  For example 'exclude "./0*/tmp"'.  Though
> > > > > I must admit I've never tried that combination.
> > > >
> 

-- 
We see in what we think we fear
The clouding of our thoughts made clear