Storage required for the fingerprint databases
A vault store group's fingerprint database holds the fingerprint, the storage location, and sharing boundary information for each SIS part that is stored in the group's vault stores.
The fingerprint database has an initial storage requirement of 212 MB, made up as follows:
100 MB for the primary filegroup
1 MB for each of the 32 non-primary filegroups
80 MB for the transaction log device
The non-primary filegroups hold the SIS part fingerprints and other information about the SIS parts. If you share items using Enterprise Vault single instance storage, the non-primary filegroups may grow very rapidly in size. Ensure that there is adequate space for the non-primary filegroups to grow as data is added.
The New Vault Store Group wizard provides the following options for the initial configuration of the fingerprint database:
A default basic configuration, where Enterprise Vault locates the primary filegroup and all the non-primary filegroups on one device.
An advanced configuration option, where you can specify separate locations for the 32 non-primary SQL filegroups.
To ensure acceptable archiving and retrieval performance, it is important to configure the fingerprint database appropriately for the amount of sharing in the vault store group.
For optimal performance, do as follows:
Use the advanced configuration option to specify as many locations as possible on the SQL Server, up to the maximum of 32.
Use a separate device for each location. If you specify more than one location on the same device there is no performance benefit.
To add or change locations after the fingerprint database is configured is a SQL Server administration task.
Limit transaction logs to an appropriate size for your back-up and maintenance plan.
About the storage requirements for Enterprise Vault
Storage required for the vault store databases
Storage required for the Enterprise Vault Directory database
Storage required for the Monitoring database
Storage required for the FSA Reporting database
Storage required for the audit database