NetBackup and _vxfiVspCacheFile
I've used various backup tools and one of the STRANGEST is Veritas/Symantec Netbackup. This software is strange for a variety of reasons that I may go into one day but for now I'll concentrate on one issue and that's the way it backs up files that are in use.
NetBackup has an add on called 'OTM' this stands for Open Transaction Manager and it backs up open files by copying them byte for byte into a special file called _vxfiVspCacheFile. Sometimes NetBackup does not do the decent thing and delete this file when it's done and on several occasions I have seen this file grow to some horrendous sizes. Recently I saw this file hit 91GB in size and eat nearly a third of the disk space of a server.
The simple fact that BACKUP SOFTWARE has the potential to seriously ruin your day by eating up so much disk space would seem to indicate that NetBackup has some issues to overcome. There are various ways of limiting the size of this file but I would have expected some internal logic to work out the best place to put such a file and to ensure that it cleans up after itself.
The worst situation is where the _vxfiVspCacheFile is locked in use by system and so cannot be deleted, because it's locked by system there is no service or application that can be killed to remove the handle on the file fortunately sys internals provide a solution for this problem.
On their website is a wonderful tool called process explorer. This tool will run just by double-clicking the .exe file and will show every file, directory, token and other resource in use by the system.
To kill _vxfiVspCacheFile its just a matter of running process explorer, clicking on SYSTEM then finding the file handle, right-clicking and selecting CLOSE FILE HANDLE. This allows the file to be deleted and thus gain back all that disk space until NetBackup goes and does it again......!
NetBackup has an add on called 'OTM' this stands for Open Transaction Manager and it backs up open files by copying them byte for byte into a special file called _vxfiVspCacheFile. Sometimes NetBackup does not do the decent thing and delete this file when it's done and on several occasions I have seen this file grow to some horrendous sizes. Recently I saw this file hit 91GB in size and eat nearly a third of the disk space of a server.
The simple fact that BACKUP SOFTWARE has the potential to seriously ruin your day by eating up so much disk space would seem to indicate that NetBackup has some issues to overcome. There are various ways of limiting the size of this file but I would have expected some internal logic to work out the best place to put such a file and to ensure that it cleans up after itself.
The worst situation is where the _vxfiVspCacheFile is locked in use by system and so cannot be deleted, because it's locked by system there is no service or application that can be killed to remove the handle on the file fortunately sys internals provide a solution for this problem.
On their website is a wonderful tool called process explorer. This tool will run just by double-clicking the .exe file and will show every file, directory, token and other resource in use by the system.
To kill _vxfiVspCacheFile its just a matter of running process explorer, clicking on SYSTEM then finding the file handle, right-clicking and selecting CLOSE FILE HANDLE. This allows the file to be deleted and thus gain back all that disk space until NetBackup goes and does it again......!
Labels: Technical

5 Comments:
Hi Gary,
Great job, it saved me a lot of time this post. I did not had to go over the long Symantec support call ...:-).
Chris P.
By
Anonymous, At
Monday, December 04, 2006
Hi Gary,
Great job, it saved me a lot of time this post. I did not had to go over the long Symantec support call ...:-).
Chris P.
By
Anonymous, At
Tuesday, December 05, 2006
Good information, especially since Veritas/Symantec say you have to reboot.
-Keith
My blog
By
Keith, At
Thursday, December 28, 2006
Gary,
We've found this solution already a long time ago but got now an other problem with it. Do you have any idea wich process (within proces explorer) blocks these files? Our PE is "hanging" when i search for the file but i'm still capable to see the processes in their handles. SO if you now the process I can go to it and kill it.
Thanks in advance.
Erik.Peters@staff.telenet.be
By
Anonymous, At
Thursday, May 03, 2007
Hi Erik,
It's the system process that holds the file open. If process explorer is hanging then you need to manually find the file handles underneath the system process.
By
Gary Williams, At
Thursday, May 03, 2007
Post a Comment
Subscribe to Post Comments [Atom]
<$I18N$LinksToThisPost>:
Create a Link
<< Home