I am running an evaluation of Vault 5.0.1. For my evaluation I have made two repositories, each of which are "hand-offs" of Source Safe vaults. It turns out that the test server has a pretty small system drive hard disk, and the system drive is filling up very quickly. The first time that I looked into this, the system drive was down to 4MB free. I found over 11,000 folders in the Windows TEMP folder with names having the form "VaultTemp.<guid>" (ie. VaultTemp.6e289217-0938-48e0-aaca-c5f538dff737). When I deleted most of these temp folders I got back 1.1GB of storage space (even though most of the folders I've looked in are empty).
These folders had various dates, so I know that they are not from the actual hand-off process, but instead have got to be from some normal source code operation that my engineers are trying during testing.
Any idea why these folders would build up?
Vault temporary files building up
Moderator: SourceGear
Re: Vault temporary files building up
We do try to clean those up. Can you verify is they are left around only from hand-offs or from normal use? Stop the Vault website, remove those folders and then start Vault again. Have your users just use Vault normally instead of hand-offs. You shouldn't see files hanging around.
Do you have antivirus on the server that could be holding onto the temporary files to scan them when we are trying to clean up?
Do you have antivirus on the server that could be holding onto the temporary files to scan them when we are trying to clean up?
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: Vault temporary files building up
I'm not sure exactly how I would stop the Vault website, but I did clean up most of the 11K folders as part of clearing up the out of storage space condition on the server. Since then, there are 64, maybe a dozen of which were left from the previous cleanup. There are 42 from yesterday, when I had a number of people trying out the server, and 4 from today. There haven't been any handoffs for over a week.
However if by what you mean by "Have your users just use Vault normally instead of hand-offs" is that you want them to try using non-hand-off repositories, I can't really do that because there aren't any. There will be if we go with Vault, but at the moment only the initial repository is a native, non-hand-off repository.
Yes, of course we have anti-virus running. That's not really an option (not to). But perhaps I can make an exclusion for any Vault folders in the Temp folder.
However if by what you mean by "Have your users just use Vault normally instead of hand-offs" is that you want them to try using non-hand-off repositories, I can't really do that because there aren't any. There will be if we go with Vault, but at the moment only the initial repository is a native, non-hand-off repository.
Yes, of course we have anti-virus running. That's not really an option (not to). But perhaps I can make an exclusion for any Vault folders in the Temp folder.
Re: Vault temporary files building up
You might try just for a short while excluding the temp folder to see if that makes a difference.
In all the folders, are there files present in them, or are they empty folders?
In all the folders, are there files present in them, or are they empty folders?
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support