The client cache is where Vault Standard stores state information (such as working folder associations) and other data for faster retrieval (such as a copy of the repository structure).
By default, these cache files are located in the current user’s Local Settings folder
(e.g., C:\Documents and Settings\user\Local Settings\Application
Data\SourceGear).
Prior to Vault 3.1, these files were stored in the Application Data settings folder,
such as C:\Documents and Settings\user\Application Data\SourceGear, so if
your cache files are there, it is because that machine had a Vault version prior to 3.1
loaded.
You may change the location of these files to any disk location, but in doing so you will cause the client to lose all of its state information. For example, your working folder associations will be lost, and after you reset working folders, the files in the working folders will have Unknown statuses (if your baseline files are stored here too – see next option below).
If you want to keep your client state, it is recommended that you move your state files into the new location prior to changing the location of the cache files (which you can do via the link provided in the options dialog).
This change does not take effect until you restart the client. It is highly recommended that you restart the client immediately after changing this option.
A baseline file is the version of the file the user retrieved from the server prior to editing it. Baseline files provide Vault Standard with working folder state information, enabling the client to know when a file has been edited, and is also used to compute a delta for the file that is sent to the server (so that less information needs to be sent and stored).
These baseline files can be stored in one of two places: Inside the client cache folder (whose location is determined in the option above), or within the working folder itself. Because these folders will grow quite large, you will want to make sure they are located in a place where there is plenty of disk space.
If you choose to store baseline files inside the working folder, an
_sgvault folder will be created in each working folder.
As with changing the location of the client cache, if you change this option, working folder data and status will be lost (files will become of Unknown status).
The default is “In Client Cache Folder”.
If checked, Vault Standard will only keep a specified number of the most recent baseline files per file.
The default is Unchecked. The default number of files to keep is 3.
This button provides quick access to your
Vault Client cache folder, without the need to browse. The
Vault client cache is in the Vault_1 folder.
If the local copy of the repository structure is not synchronized with the
Vault Standard Server, you can reset it with this option. This will
delete the CacheMember_LastStructureGetTime and
CacheMember_Repository files from the client cache. The client will then
request the entire tree structure from the Vault Standard Server.
If checked, any modified file that Vault Standard overwrites in the working folder will be backed up into the backup folder specified below.
The default is Checked.
This tells the Vault Standard client where to store the backup
files. Choosing “In Working Folders”, will place them in a folder named
“_sgbak” within the working folder of the file being backed up.
Choosing a custom location will backup the files in the folder that you choose.
The default is “In Working Folders”.