Chuck,

I would say these files are very good candidates for exclude as any other
temporary file. If they are existing for a very limited period and even
now you are not backuing up those files without any harm, then I would
classify them as temporary.
IMO this is not a limitation of the product but poor implementation of its
features.

Zlatko Krastev
IT Consultant






Chuck Mattern <Chuck_Mattern AT HOMEDEPOT DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
23.06.2003 14:55
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Work arounds for files deleted in flight?


Ever since we transitioned from adsm v3 to adsm v4 we have encountered an
extremely high "failure rate".  Essentially when adsm went from backing up
Unix filesystems like tar (see a file; get a file) to doing ti like dump
(build a list of files; go back and backup the list) we began taking what
I
do not consider true failures.  Since we do not have the ability to
quiesce
our systems for backup many files that adsm identifies as backup
candidates
are deleted before they can be backed.  To avoid wasting many hours of
engineer time logging into several hundred servers to investigate this I
am
writing a Perl utility to parse the logs, totalling the "file not found"
failures and only reporting a failure back to us if there are more errors
than the total number of "file not found" errors.  I took the issue up
with
ADSM support and essentially got "that's the way it is now, sorry"  Is
anyone else having problem like this and if so can you offer any better
solutions than the one I am working on?

Thanks,
Chuck

Chuck Mattern
The Home Depot
Phone: 770-433-8211 x11919
Email: chuck_mattern AT homedepot DOT com
Pager: 770-201-1626