Kris,

We have a list of files/folders that we set in the exclude list. Here's a few 
of them:
Recycler
i386
found.0*
$NTUninstall*
pagefile.sys
TMP
TEMP
C:\winnt\system32\perflib_perfdata_*

There's more that we exclude on all servers.

When a job fails with a status code 1, we determine what file(s) it missed. We 
then either exclude it, or ask the admin of the system (in the case of SQL, or 
dedicated Application server) if it's safe to skip it. If it's not, then we 
just have to deal with a 1. FYI, we are on 4.5 FP5 and have VSP disabled due to 
it's problems at this level.

Rusty

> -----Original Message-----
> From: WILLIAMS, KRISTOPHER L [mailto:kris.williams AT hp DOT com]
> Sent: Tuesday, June 08, 2004 4:22 PM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] How do you handle status code 1?
> 
> 
> 
> 
> Hello all,
> 
> 
> 
> It's safe to say that we get mostly status code 1's on backups for out
> NT environment. A spot check of the files missed normally shows a NT
> system file that is being missed because it is opened with the
> occasional application file. 
> 
> Three quick questions:
> 
> 1. Does anyone have any good/bad things to say about VSP running on
> Windows 2000 NBU V5.0GA? The clients are a mix of NT 4 and Win2k.
> 
> 
> 2. Does anyone have a good script to show which files are being missed
> on a given server? I know I can get the info in bperror and the NBU
> reports, but the format is awful.
> 
> 3. What does your company do to handle status code 1's? I'm 
> looking for
> both the technical aspect as well as the processes. 
> 
> 
> Thanks,
> 
> 
> Kris
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>