Please enter search query.
Search <book_title>...
Enterprise Vault™ Introduction and Planning
Last Published:
2019-02-06
Product(s):
Enterprise Vault (12.4)
- 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
- About Enterprise Vault Search
- Enterprise Vault administration
- About reporting and monitoring in Enterprise Vault
- Exchange Server 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
- 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
Typical Enterprise Vault configuration in a Windows Server failover cluster
Figure: Enterprise Vault in an active/passive failover pair configuration illustrates a typical configuration.
In this example:
NODEA and NODEB are the two Enterprise Vault nodes in the failover cluster. NODEA is the primary node. NODEB is the failover node.
The SQL server and Microsoft Exchange may also be configured in the cluster: this does not affect Enterprise Vault.
The volumes for the Enterprise Vault services data are configured on shared storage.
The Enterprise Vault cluster server is configured on the primary node, NODEA. If NODEA fails, the cluster server's resources fail over to NODEB, and the cluster server comes online on NODEB.