Please enter search query.
Search <book_title>...
Enterprise Vault™ Introduction and Planning
Last Published:
2019-10-21
Product(s):
Enterprise Vault (12.5)
- 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
Building blocks and high availability
The building block approach can be used in an N+1 architecture in which an idle server stands by to replace any one of N servers that may fail. The "+1" server could also be used to run as an extra, hot standby server running IIS to take some of the workload from the other servers.
In an active/active architecture an existing server can take on the additional workload of a failed server. An active/active solution can be implemented if servers have spare capacity to handle extra work. After failover the net performance may drop, depending on the amount of spare capacity. Thought must be given to this during the design stage.