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
Upgrading the Enterprise Vault databases
Before you start any Enterprise Vault services, you must upgrade the Enterprise Vault databases.
Note:
You only need to complete this procedure on one Enterprise Vault server.
Enterprise Vault provides a PowerShell cmdlet called Start-EVDatabaseUpgrade, which you can use to upgrade all Enterprise Vault databases.
Note:
After upgrading Enterprise Vault databases to version 14.2, all the existing index locations will be closed for new index additions. A new index location must be configured to store new Elasticsearch indexes. The Enterprise Vault Indexing service does not start until a new index location has been configured.
The upgrade of the Directory database schema requires additional disk space on the SQL Server computer, mainly for log file growth. You can reclaim most of this additional space by routine database maintenance after the upgrade.
The required amount of space for the upgrade depends on which recovery model the database uses.
Table: Space required for the upgrade of the Directory database lists the additional space requirements.
Table: Space required for the upgrade of the Directory database
Directory database recovery model | Required additional space on the volume that holds the database transaction log files |
---|---|
Simple or Bulk-logged | Twice the combined size of the Directory database data files |
Full | Four times the combined size of the Directory database data files |
Note:
Enterprise Vault does not let you proceed with the upgrade unless this additional space is available.
These estimated space requirements are based on the assumption that you perform the recommended maintenance activities when you back up the database before the upgrade.
See Backing up the upgraded Enterprise Vault databases.
The upgrade of a large Directory database may take a long time to complete. The upgrade time depends on the size of the database, the database recovery model, the upgrade path, and the available resources.
To upgrade Enterprise Vault's databases
- On any Enterprise Vault server, log in using the Vault Service account.
- Run the Enterprise Vault Management Shell.
- In the Enterprise Vault Management Shell, run the following command:
Start-EVDatabaseUpgrade
Note that you can also run Start-EVDatabaseUpgrade -verbose if you want to see detailed output.
- Wait for Start-EVDatabaseUpgrade to complete the upgrade of all the databases.
When the upgrade is complete, you can examine the upgrade reports for errors.
Start-EVDatabaseUpgrade writes the reports in the Reports\DBUpgrade
subfolder of the Enterprise Vault installation folder (for example C:\Program Files (x86)\Enterprise Vault
).