Chuck, would a missed-files report that grouped them by reason-missed help
you?
eg:
        Files Missed for Nodexxx
Not found:              562
Changing:               2
Locked:         132

Then of course you'd want to be able to click each line, and drill down
to see the actual file names.  If you did that, do you think you'd want
to see (for the Locked list ,say) all 132 files, or just the file NAMES
that differ - that is, cut off the directory part?


-----------------------------
Mr. Lindsay Morris
Lead Architect
www.servergraph.com
512-482-6138 ext 105

> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Chuck Mattern
> Sent: Monday, June 23, 2003 7:55 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> 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
>