Enterprise Vault™ Upgrade Instructions
- About this guide
- Before you begin
- Points to note when upgrading
- Installing Outlook on the Enterprise Vault server
- Improved consistency when applying a retention period to items
- Steps to upgrade your system
- Enterprise Vault server preparation
- Single server: upgrading the Enterprise Vault server software
- Multiple servers: upgrading the Enterprise Vault server software
- Veritas Cluster Server: upgrading the Enterprise Vault server software
- Windows Server Failover Clustering: upgrading the Enterprise Vault server software
- Upgrading standalone Administration Consoles
- Upgrading Enterprise Vault Reporting
- Upgrading MOM and SCOM
- Upgrading Exchange Server forms
- Upgrading Domino mailbox archiving
- Upgrading the FSA Agent
- Upgrading Enterprise Vault Office Mail App
- Upgrading SharePoint Server components
- Upgrading SMTP archiving
- Checking the SMTP journaling type configuration
- Upgrading your Enterprise Vault sites to use Enterprise Vault Search
- Setting up provisioning groups for Enterprise Vault Search
- Configuring user browsers for Enterprise Vault Search
- Setting up Enterprise Vault Search Mobile edition
- Upgrading Enterprise Vault API applications
Additional requirements for the Enterprise Vault index server
In a new installation of Enterprise Vault 14.2 or later, or an upgrade to Enterprise Vault 14.2 or later, Elasticsearch is the new indexing engine.
The Elasticsearch indexing engine has following requirements:
Additional CPU and RAM configuration. Refer to the Enterprise Vault hardware requirements section in the Installing and Configuring guide.
Memory is allocated and reserved for the Elasticsearch indexing engine. By default, 8 GB of memory is reserved for the Elasticsearch indexing engine. Reservation of memory for the Elasticsearch indexing engine provides lesser memory to other Enterprise Vault services if those are running on the Enterprise Vault index server. It is recommended that you increase the RAM by 8GB to ensure that all the applications run smoothly.
A single index location to store all index data of the Elasticsearch indexes. The Elasticsearch indexing engine does not allow multiple index locations. It is recommended that you provision disk space considering this requirement. Additionally, it is recommended to have separate index location for storing the index data of Elasticsearch indexes. Elasticsearch index data is 8% of the total disk space of archived items. Provision disk space for index data based on future requirement.
Additional disk requirement for storing snapshots of the Elasticsearch indexes.
Additional two TCP ports is used by the Elasticsearch indexing engine for communication on the index server. By default, you must keep any two ports open between the range 9200-9300. The port range can be changed later.