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 Enterprise Vault building blocks
An alternative to clustering is to implement Enterprise Vault building blocks. This is part of a straightforward methodology for deploying Enterprise Vault in a way that is both scalable and reliable. You can easily extend a solution made from building blocks to increase capacity. In addition, you can configure building blocks for several different failover schemes such as active/passive and active/active.
A building block is a repeatable unit of Enterprise Vault functionality hosted on an application server. By adding sufficient building blocks, Enterprise Vault can be extended to scale to the largest of workloads, as shown in Figure: Enterprise Vault building blocks.
Each building block comprises a set of Enterprise Vault services that deliver the same functionality.
The combined services form a unit known as a building block, which is identified by a building block name.
Each building block is hosted on a particular server, but in the event of a disaster on that server Enterprise Vault can failover a building block to another server (without the need for clustering technology). Failover does not require any reconfiguration on the desktop and users are unaffected.