On Wed, May 23, 2012 at 10:19:02AM -0500, Greg Copeland wrote:
> I'm having a hard time getting a DLE correctly created to archive some
> snapshots. My snapshots are housed in directories like:
> snapshot/monthly.0/
>     a/
>     b/
>     c/
> snapshot/monthly.1/
>     a/
>     b/
>     c/
> snapshot/monthly.2/
>     a/
>     b/
>     c/
> ...so on and so on... For each snapshot, I must create multiple DLEs to
> make the volume of data more manageable. As such, for each snapshot
> directory, I need to create multiple DLEs. The data is very uniform
> within each snapshot directory so I'd love to be able to provide broad
> regexs to snatch everything up within each DLE.
> 
> At this time I either wind up with no data or a backup which ran for
> over 50-hours, which should have finished in less than 19. I had to kill
> it. Frequently I get a nice message saying that something strange
> happened with the backup and the strangeness is always associated with
> these snapshots. Which isn't exactly surprising in that its not backing
> up any data. Obviously I'm not doing something right here.
> 
> What I would like to have is DLEs which grabs something like:
> DLE 1: snapshot/monthly*/a/*
> DLE 2: snapshot/monthly*/b/*
> DLE 3: snapshot/monthly*/c/*
> 
> I've tried many variations of defining my DLE to do this so I'll not
> bother sharing what I have. Honestly, I doubt I can recall all the
> variations I've tried.

I'm not sure this would work, but maybe a combination of includes and
excludes.  First start your DLEs at .../snapshot.  The example below
would be for your "DLE 1".

<hostname> Monthly_A <...>/snapshot {
    <dumptype>
    include list ./monthly.*
    exclude list ./*/[bc]
    <other options>
} < optional spindle etc. >

As noted, I'm not sure this will work, but the manpage description
for exclude does not have the same "single /" restriction as include.


-- 
Jon H. LaBadie                 [email protected]
 11226 South Shore Rd.          (703) 787-0688 (H)
 Reston, VA  20190              (609) 477-8330 (C)

Reply via email to