Getting a file called _vxfiVspCacheFile_0.tmp on different Servers that are sometimes up to 40 GB. Read through some Netbackup Forums and saw that this is related to VSP in Netbackup. I am not using Snapshot Provider on any of these clients. I have to reboot the Server to be able to delete the file. I have contacted Veritas but wanted to see if anyone else has ran into this problem and if they know of a fix to keep this file from coming back. I am using Netbackup 5.1 Enterprise on Windows Server 2003. This file has shown up on 3 different Servers and all Windows Server 2003 and none are using Vsp.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
_vxfiVspCacheFile_0.tmp 1
- Thread starter tech2004
- Start date
On NetBackup 5.x, VSP is enabled by default unless you go into Host Properties of the master > Client Attributes and add the client hostnames, then click on 'Windows Open File Backup' tab and deselect the 'Enable...' checkbox....Apply > Ok. No need to restart NBU svcs. Also VSP is installed by default on servers/clients unless you chose a 'Custom' install of the NBU software and de-selected VSP from being installed.
Lata
Lata
I have had this issue before and it was caused by enabling a temporary license key from Veritas which then enables all of your licenses. I was not using VSP for any of my backups but as Qdog stated by default it is enabled so when my license for the option enabled I saw the .tmp files on various systems. From the little bit of reading I performed on this matter the .tmp files are supposed to be automatically removed from the client after the backup has completed. If your backup ended with a status of 1 which I personally consider successfull it DOES NOT remove the .tmp file. I ended up cutting my temporary license key off early to avoid this from happening again. Did the
backup(s) in question exit with a 1 status?? Did you activate and new keys recently like the one mentioned above??
backup(s) in question exit with a 1 status?? Did you activate and new keys recently like the one mentioned above??
-
1
- #4
We had the same thing happen with some of the older Window's client's that are using OTM instead of VSP- If enabled it will create a large temp file for the snapshot.
You should be able to got to host properties>client's.click on the client in question>Windows Client>click VSP
If you don't set the max size cache file or leve it blank the system will determine the size of the file needed and use the space.
What we are doing is setting the max size of the file to 500mb max for problem client's
Ryan
You should be able to got to host properties>client's.click on the client in question>Windows Client>click VSP
If you don't set the max size cache file or leve it blank the system will determine the size of the file needed and use the space.
What we are doing is setting the max size of the file to 500mb max for problem client's
Ryan
- Thread starter
- #5
Thanks for the advice. I went into Host Properties of the master > Client Attributes and added the client hostnames, then clicked on 'Windows Open File Backup' tab and deselected the 'Enable...' checkbox....Apply. This did not work. A couple of days later I got the same problem with the tmp file. I put in a call to Veritas and they had me to go back and modify the installation and deselect the VSP option during the install.
there's this veritas tech note that gives instructions on how to kill the handles on the files so that you can unlock and delete them. you would use process explorer from sysinternals to search for vsp and kill whatever comes up. it's been successful for me so far.
- Status
Similar threads
