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
Scalability and disaster recovery
To handle incoming journal data in large environments, you can configure multiple Enterprise Vault SMTP servers with the same SMTP routing address, for example journal@ev.example.com. Alternatively, you can configure multiple SMTP routing addresses for the Enterprise Vault SMTP servers, for example, journal1@ev.example.com, journal2@ev.example.com, journal3@ev.example.com, and so on. Load balancing can be handled using load balancing technologies, such as DNS MX records, or network load balancers.
Deploying multiple Enterprise Vault SMTP servers provides for disaster recovery. If one of the Enterprise Vault SMTP servers fails, the load balancer can route the connection request to the next available server.
You can also use clustering services to make the Enterprise Vault SMTP server highly available.