[Veritas-bu] File Exclusions
Unfortunately, my "*.dbf" exclusion has become (for my server that does my
centralized backups of our many filers and they're many strange
...and so forth to about 8 layers deep. I don't see how processing this
ugly list of exclusions could be more efficient than "*.dbf".
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Darren
Sent: Tuesday, September 21, 2004 2:24 PM
To: Veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] File Exclusions
> For example, I have changed traditional status code 1 backups to 0's
> just be excluding the (Netscape) "parent.lock" file (on Windows
> desktops). Finding the path to "parent.lock" is MUCH more difficult, as
> it varies from client to client.
Yes, but can't you just specify it as /*/parent.lock ? That's how I'm
interpreting the support document.
> This isn't a new feature, ladies and gentlemen; it's a (documented after
> the fact) bug. :-(
It's a bug if they didn't intend it to happen and are working to remove
it. There's no sign that they're working to change this.
> If Veritas refuses to correct this, shouldn't we have a tool to help
> find the entries that no longer work? A fairly simple server script
> using bpgetconfig should do the trick.
It seems to me that not only finding them, a simple translation by
adding /* could be done also.
Of course if that were possible, you'd presume that the NBU process
could do the same thing after reading the file into memory before acting
Darren Dunham ddunham AT taos DOT com
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu