VSP cache files.

They usually linger on the client, if a backup fails (infamous Status
156) due to AV locking, or disk filling, or whatever.
Could happen if Antivirus is scanning the file when Netbackup creates
it, and antivirus has it locked when NBU tries to delete it.

See the following technote:
http://seer.support.veritas.com/docs/269558.htm

Need to reboot the client to release/delete it.
The files can fill the disk and crash the client.......been there, done
that.

Paul

> -----Original Message-----
> From: veritas-bu-admin AT mailman.eng.auburn DOT edu 
> [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of 
> Brooks, Jason
> Sent: February 17, 2006 9:27 AM
> To: Veritas-bu AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] Client Files
> 
> 
> While I was out of the office for a few days, an issue arose 
> that may be
> NBU related.  That is what I am trying to determine.
> 
> On several Windows servers, one of my colleagues saw files in the root
> of C: with a name similar to _vxfiVspCacheFile_0.tmp, 
> *CacheFile_1.tmp,
> etc.  These files are quite large, around 10-15 GB on the 
> server I have
> checked.
> 
> Being Windows, I have no easy way to even start looking at the file -
> more won't do it.  My colleague's hunch was that NBU was 
> doing some sort
> of prestaging.  Does NBU do prestaging of backups on the client?
> Anywhere to verify anything with regard to NBU?
> 
> Thanks,
> Jason
> 
> ------------
> Jason Brooks
> Computer Systems Engineer
> IITS - Longwood University
> voice - (434) 395-2916
> fax - (434) 395-2035
> mailto:<brooksje AT longwood DOT edu> 
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>