Veritas Enterprise Vault™ Introduction and Planning
- About this guide
- Introduction
- Overview of Enterprise Vault
- How Enterprise Vault works
- About Enterprise Vault indexing
- About Enterprise Vault tasks
- About Enterprise Vault services
- About the Enterprise Vault Outlook Add-In
- Enterprise Vault administration
- About reporting and monitoring in Enterprise Vault
- Exchange Server archiving
- Exchange Public Folder archiving
- File System Archiving
- File Blocking with File System Archiving
- Archiving Microsoft SharePoint servers
- Domino mailbox archiving
- Domino Journal archiving
- SMTP Archiving
- Enterprise Vault Accelerators
- About Compliance Accelerator
- About Discovery Accelerator
- Building in resilience
- 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
About index volumes
The index for an archive comprises one or more sequential index volumes. Each index volume contains index documents for the items that are stored in the archive.
Typically, a user mailbox index requires only one or two volumes. Indexes for larger archives, such as file system archives and journal archives, are likely to have multiple volumes.
When an index volume is full, the Index Server automatically creates a new index volume. The location that is selected for new index volumes depends on whether the vault store is managed by a single Index Server or an Index Server group. If the vault store is indexed by an Index Server group, the index volumes for an archive may be distributed across multiple Index Servers and locations, as shown in Figure: Spread of index volumes in an Index Server group. In general, when the index for a mailbox rolls over, the existing Index Server is used, if possible. The index location is selected using a round robin algorithm, to balance the load across all index locations. For larger archives, such as journal archives, new volumes are distributed evenly across the Index Servers and index locations.
The Enterprise Vault Administration Console includes tools for managing index volumes.