|
|
Enterprise Vault has the following core databases:
The Enterprise Vault Directory database. There is just one of these and it may be shared by more than one Enterprise Vault site.
The vault store databases. There is one of these for each vault store in a site.
The fingerprint databases. There is one of these for each vault store group. If you upgrade to Enterprise Vault 8.0, Enterprise Vault does not create a fingerprint database for the Default Upgrade Group until you configure sharing for it.
The Enterprise Vault Monitoring database. There is one of these for each Enterprise Vault Directory database. If multiple Enterprise Vault sites share a Directory database, then they must also share a Monitoring database. The Monitoring database holds the status information that the Monitoring agents gather about the Enterprise Vault servers.
In addition, if you configure FSA Reporting, Enterprise Vault creates an FSA Reporting database to hold the reporting data it gathers from the file servers.
SQL Server must be installed and set up before configuring Enterprise Vault. Note that the sort order/collation setting for the SQL Server installation must be case-insensitive; case-sensitive installations are not supported.
Microsoft SQL Server does not need to be on the same computer as the Directory Service computer, nor does it have to be on the vault store computers. On each computer, run Microsoft SQL Enterprise Manager to register the SQL Servers you have installed.
It is possible, perhaps as part of network reconfiguration, to change the instance of SQL Server that manages the Directory database. The process is described in the Administration Console help.
When configuring Enterprise Vault, you are asked to supply the following:
The Vault Service account details. This enables Enterprise Vault to create the Directory database and vault store databases
The SQL server location and the data and log file locations for the Enterprise Vault Directory database
The SQL server location and the data and log file locations for the Enterprise Vault Monitoring database
Enterprise Vault also creates the following database locations:
Each vault store database contains an entry for each item that is archived in the associated vault store, so the vault store databases will grow over time. Only when an item is deleted from the archive will references to it be deleted from the relevant vault store database.
When you create a vault store group, Enterprise Vault creates a fingerprint database for the group. The New Vault Store Group wizard provides the following options for configuring the database filegroups:
The non-primary filegroups can grow rapidly in size when you use single instance storage. For best performance, spread the non-primary filegroups across multiple locations.
If you configure FSA Reporting, Enterprise Vault creates the FSA Reporting database, named EnterpriseVaultFSAReporting, and sets up locations for the database data and transaction log.
For database storage requirements, see "Storage requirements" in Installing and Configuring.
If Compliance Accelerator or Discovery Accelerator is installed, there will also be separate databases created for each of these. The Accelerator databases can be managed by the same SQL Server as the Enterprise Vault databases or a different one, as required.
In Compliance Accelerator, data about all departments, captured items, searches and items reviewed is kept permanently in the databases. Similarly, in Discovery Accelerator, data about cases, searches, search results and items reviewed is kept permanently in the databases. Ensure that there is enough storage space for the growing database files. The databases can be managed using standard SQL administration tools.