Enterprise Vault™ Introduction and Planning
- About this guide
- Overview of Enterprise Vault
- How Enterprise Vault works
- About Enterprise Vault indexing
- About Enterprise Vault tasks
- About Enterprise Vault services
- About the Archive Discovery Search Service
- About the Enterprise Vault Outlook Add-In
- About Enterprise Vault Search
- Enterprise Vault administration
- About reporting and monitoring in Enterprise Vault
- Exchange Server archiving
- About Exchange Server archiving and user mailboxes
- Exchange Server and journal mailbox archiving
- Exchange Public Folder archiving
- File System Archiving
- Archiving Microsoft SharePoint servers
- Domino mailbox archiving
- Domino Journal archiving
- SMTP Archiving
- Skype for Business Archiving
- Enterprise Vault Accelerators
- About Compliance Accelerator
- The Compliance Accelerator client application
- About Discovery Accelerator
- Discovery Accelerator client application
- Building in resilience
- About Enterprise Vault and VCS
- About Enterprise Vault and Windows Server Failover Clustering
- About Enterprise Vault building blocks
- Planning component installation
- Where to set up the Enterprise Vault Services and Tasks
- Installation planning for client components
- Planning your archiving strategy
- How to define your archiving policy for user mailboxes
- How to plan the archiving strategy for Exchange public folders
- How to plan settings for retention categories
- How to plan vault stores and partitions
- About Enterprise Vault reports
Enterprise Vault databases and planning their installation
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. One possible exception is the Default Upgrade Group, which Enterprise Vault creates if you previously upgraded 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.
If you configure FSA Reporting, Enterprise Vault also uses one or more FSA Reporting databases to hold the FSA Reporting data that 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.
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 creates databases with the following names:
Enterprise Vault also creates the following database locations:
A location for the Monitoring database data
A location for the Monitoring database transaction log
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:
A basic configuration, in which Enterprise Vault locates the primary filegroup and all the non-primary filegroups on one device.
An option to configure additional locations for the 32 non-primary 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.
On the first occasion that you configure a file server for FSA Reporting, a wizard helps you to create an FSA Reporting database. When you configure additional file servers for FSA Reporting, you can choose to use the existing FSA Reporting database or to configure an additional one.
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.