Vault data under Application Data folder consuming over 6 GB

[eisaacs]

I'm using Vault 3.5.1. The hard drive on my machine filled to capacity today. After a little investigation I determined that Vault's application data was consuming some 6 GB of space on my machine. Specifically, the \Application Data\SourceGear\Vault_1\Client\B5AF116E-0F13-4987-AEE0-F336C8D55AE6\eric\_sgvault folder had almost 4GBs consumed and other projects had some 500 MBs of space consumed.

I searched your forums and found this link from 2003: http://support.sourcegear.com/viewtopic.php?t=6

That post seemed to indicate that the files in application data (\Application Data\SourceGear\Vault_1\Client\B5AF116E-0F13-4987-AEE0-F336C8D55AE6\eric\) could be removed (or at least the config files in that user folder could be removed.) Those config files are only using a few kilobytes each, so removing them won't address the issue. The post didn't specifically address the files under the _sgvault subfolder, however. Those are the files that are using up all the space. I don't want to delete my config settings, I only want to remove anything that's utilizing unneeded space on my hard drive. Can the files in _sgvault be removed without affecting Vault when Vault isn't running?

Thanks!

[eisaacs]

This post seems to indicate that the _sgvault folder is fair game to be deleted:

http://support.sourcegear.com/viewtopic ... a3921fed6e

[lbauer]

The _sgvault folder contains baselines for all the files you have retrieved to the local working directory. One way to keep this file smaller is to only get items you need to work on.

You can also configure the Client to create the _sgvault folder in the local working folder, so when you no longer need those files/folders locally, it's easy to delete the _sgvault folder as well.

The setting is in the GUI Client under Tools->Options->Local Files->Cache/Backup location.

[eisaacs]

Thanks for the reply.

I had one file checked out when I removed that folder and after deleting the folder it said the file needed to be merged. When is it safe to delete the files? Does the newer version of Vault maintain these files more consistently? Shouldn't Vault remove the files when they are no longer needed? It's a lot to ask the user to know when they no longer need the files when the user (me) doesn't even know what the specific files are for.

Another developer in our office was also having hard drive issues and we found 4 gigs of space in one of his project files as well. That's a significant amount of space being consumed that Vault is not managing.

It would be great if Vault would remove the appropriate files on check-in or undo/revert of check-out, or on when it retrieves the latest version from the server, or whenever else it's ok to delete them.

Optionally, if there was tool menu option to purge these unneeded files, that would be acceptable as well. I imagine if the userbase knew how much space these folders could contain unnecessarily that this would be a highly requested improvement. I've been using Vault for a long time and never knew that it didn't clean up after itself properly. Please consider fixing this in the latest version, if it's not already addressed in the latest version.

Thanks again.

[lbauer]

It's best to check in any changes and close your client before you delete the baselines.

The Vault 4.x client does have to option to specify how many baseline files to keep in the _sgvault folder. Baselines are added every time you do a Get from the repository. In Vault 4.x, you can limit the number of baselines to 2 per file, for instance.

You might consider upgrading to get this feature (and many others in 4.x).