Yes, the [A-Ma-m] should work fine, don't forget hidden files, underscores,
etc.  Something that *should* work but I haven't tried yet is make one
[A-Ma-m]* and the other [!A-Ma-m]*.  It works in unix and catches a world
and should catch all the NOT A to M stuff.

Nope - streams run independently, if your [a-m] stream died, the [n-z] would
continue.  The fact that they're in the same policy isn't significant.

-M

-----Original Message-----
From: leareth AT angui DOT sh [mailto:leareth AT angui DOT sh]On Behalf Of 
Matthew
Hall
Sent: Wednesday, September 28, 2005 10:59 AM
To: Mark.Donaldson AT cexp DOT com
Subject: RE: [Veritas-bu] Regex policy backup?


On Tue, 27 Sep 2005 Mark.Donaldson AT cexp DOT com wrote:

> It's limited to the target client's abilty to pattern match for filenames.
> For example, "*a*b*c" works in unix but Windows is too limited to match
> something as complex as this.
>
> So, what you've got will work but you should write it in filesystem
> patterns:
>
> /data/[a-m]*
> /data/[n-z]*

So couldn't I do

/data/[A-Ma-m]*
/data/[N-Zn-z]*

That works nicely under bash.

> You can also do this in one policy:
>
> NEW_STREAM
> /data/[a-m]*
> NEW_STREAM
> /data/[n-z]*

Hmmm. But if something bad happened during the a-m stream,
wouldn't that still abort the whole job, thus not getting
to the n-z stream?

-- 
It's always September somewhere on the 'net. | http://angui.sh
Another proud member of Eep's killfile.      | Unix Sys. Admin.
All projects approach the ghetto, some       |
faster than others.                          | matt AT angui DOT sh