In addition, I found it very useful to use the FvLoader utility. The loader can be used to create and configure external vaults and vaulting rules. See WCSysAdminGuide Chap 5. With the utility you can load all of your vaulting rules from a file. We created separate folders for each object type we were vaulting.
BAE Systems IT
In Reply to Bill Palm:
Files are put directly into a cache vault upon creation. They are then
moved permanently to the vault defined in the vaulting rules for that
particular object. They are never stored in the database if you are using
It's usually recommended to put all files in a single vault using the
wt.fv.forceContentToVault option in wt.properties. A single vault can have
multiple folders so you don't stress the OS by putting too many files in a
single OS folder. If you are using Windows, set disable8dot3 to true (1)
using the fsutil command (fsutil behavior set disable8dot3 1) for better
performance. If you're using Windchill 9.0, you can use Root Folders which
will make simplify maintenance of the folders by automatically creating new
folders as needed (used in conjunction with a wt.properties threshold value
- check for details).
Manager - RAPiDS Support Center
ProductSpace Solutions, Inc.
On Tue, Jan 6, 2009 at 4:24 PM, bill o'rourke <->wrote:
> We are setting up vaulting for the first time, and were wondering if the
> kind folks in WindchillLand had some dos and don'ts about vaulting. Some
> questions we have is it possible to have new data move to the vault upon
> creation, or do you have to set up the vaulting jobs to run periodically?
> And do most folks have separate vaults/folders for each product\library, or
> do you tend to lump them all together? Any and all help is most appreciated!
I just would like to encourage everyone to use a single folder as vault (at least on windows) --- I don't think it's worth the headache to sperate the objects into different folders.
we ha a vault of 2.000.000 Files and 600 GB in one Folder without any problem.
NTFS can handle 4,294,967,295 Files and 256terabytes of data (it doesn't depend on the folders but is the value per volume)
The only thing you have to do is:
If you use large numbers of files in an NTFS folder (300,000 or more), disable short-file name generation for better performance, and especially if the first six characters of the long file names are similar.