Enterprise Vault™ Upgrade Instructions
- About this guide
- Before you begin
- Points to note when upgrading
- Order of upgrade in an environment with Compliance Accelerator or Discovery Accelerator
- Silently installing Enterprise Vault from the command line
- Installing Outlook on the Enterprise Vault server
- Securing Enterprise Vault web applications
- Weak protocols and ciphers are blocked
- Improved consistency when applying a retention period to items
- Automatic migration of NetApp C-Mode connection settings
- Enterprise Vault auditing configuration
- Amazon Simple Storage Service (S3) partition
- Classification using Microsoft File Classification Infrastructure on Windows Server 2016 and 2019
- Data Classification Services does not support all the types of retention categories available in Enterprise Vault 14.2 and later
- Managing certificates for Enterprise Vault Cloud Storage Adapter
- eDiscovery Platform compatibility with Enterprise Vault
- 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
- About upgrading Domino mailbox archiving
- Domino client version required to run EVInstall.nsf
- Preparing for the upgrade of Domino mailbox archiving
- Upgrading Domino mailbox archiving
- Granting the Domino archiving user access to mail files
- Identifying internal mail recipients
- Run the Domino provisioning task
- Upgrading the FSA Agent
- Compatible versions of the FSA Agent and Enterprise Vault server
- About upgrading the FSA Agent
- Upgrading FSA Agent services that are clustered for high availability
- Upgrading the FSA Agent on a target Windows file server from the Administration Console
- Upgrading the FSA Agent on an FSA Reporting proxy server from the Administration Console
- Upgrading the FSA Agent manually
- Upgrading Enterprise Vault Office Mail App
- Upgrading SharePoint Server components
- Upgrading SMTP archiving
- Required and optional tasks when upgrading SMTP Archiving
- Checking the SMTP journaling type configuration
- Checking the permissions of the SMTP Archiving task account
- Checking the 'Journal report processing' advanced SMTP policy setting
- Checking the 'Journal Reports settings' advanced SMTP policy setting
- Checking the 'Selective Journal Archiving' site setting
- About upgrading legacy SMTP archiving components
- Migrating existing targets to provisioning groups
- Reconfiguring targets that are configured for target address rewriting to use multiple archives
- Granting the Administrators group and system account full access to the SMTP holding folder
- Upgrading your Enterprise Vault sites to use Enterprise Vault Search
- About Enterprise Vault Search
- Server requirements for Enterprise Vault Search
- Defining search policies for Enterprise Vault Search
- Allowing privileged Enterprise Vault Search users to restore items to other users' mailboxes
- Setting up provisioning groups for Enterprise Vault Search
- Creating and configuring Client Access Provisioning tasks for Enterprise Vault Search
- Configuring user browsers for Enterprise Vault Search
- Configuring Enterprise Vault Search for use in Forefront TMG and similar environments
- Setting up Enterprise Vault Search Mobile edition
- Upgrading Enterprise Vault API applications
Configuring index data location
The Enterprise Vault administrator must configure an index data location from the Enterprise Vault Administration Console or by running the Getting Started wizard. The Enterprise Vault Admin service and the Enterprise Vault Directory service must be running before configuring the index data location.
To set up the Enterprise Vault index data location through Enterprise Vault Administration Console, perform the following steps:
In the left pane, expand the Enterprise Vault site hierarchy until the Indexing container is visible.
Expand the Indexing container.
Expand the index server to which you want to add an index data location.
Right-click the index server, click , and then click the tab.
Click to choose an empty folder in which index data can be stored.
Click to apply the changes.
Start Enterprise Vault indexing service once the configuration is done.
Repeat this procedure on every computer on which the Enterprise Vault Indexing service is installed.
If you want to backup the newly created Elasticsearch indexes, you first need to set up an index snapshot location through PowerShell using the following steps:
Run the Enterprise Vault Management Shell.
In the Enterprise Vault Management Shell, run the following command:
Set-EVIndexSnapshotLocation -SnapshotLocationPath "I:\" -SiteId <EV site id>
For more information, see the PowerShell Cmdlets guide.
Restart the Enterprise Vault Indexing service on every computer on which the Enterprise Vault Indexing service is installed..