Enterprise Vault™ Installing and Configuring

Storage for Enterprise Vault indexes

The computer hosting the Enterprise Vault Indexing service requires access to adequate storage for the indexes.

Each indexing Service also requires disk space for indexing configuration and reporting data. This is set using Index metadata location in the Indexing service properties. If you install Enterprise Vault on a cluster, then the index metadata folder, Enterprise Vault installation folder\EVIndexing\data\metadata, must be moved to a shared drive. You will also need to update Index metadata location in the Indexing service properties.

Indexes may be placed on local storage, SAN, or NAS. If fast indexing is required or searches across a large number of archives, NAS devices may not be suitable.

File systems that use slow storage media as part of their solution, such as optical disk, are unsuitable for indexes.

If indexes are stored on NetApp devices, and possibly other NAS systems, opportunistic locking must be turned off for volumes that contain indexes. For more information, see the following article on the Veritas Enterprise Support site:

https://www.veritas.com/docs/100017354

As anti-virus software can potentially change data, it is important to exclude the index locations in your virus checking application. For more information, see the following article on the Veritas Enterprise Support site:

https://www.veritas.com/docs/100017720

Table: Index size compared to size of original data shows how to calculate the expected sizes of indexes.

The type of data being archived will also affect the size of indexes. Archiving a large number of text or HTML files will produce larger indexes. Archiving a large number of binary files, such as image files, will produce smaller indexes, as the content is not indexed.

There is no sharing of index files.