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
- Classification using Microsoft File Classification Infrastructure on Windows Server 2016
- Data Classification Services does not support all the types of retention categories available in Enterprise Vault 12.5
- eDiscovery Platform compatibility with Enterprise Vault
- Additional points to note when upgrading from Enterprise Vault 11.0 or 11.0.1
- 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 OWA Extensions
- 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
Upgrading the Enterprise Vault databases
Before you start any Enterprise Vault services on the target server, you must upgrade the Enterprise Vault databases.
Enterprise Vault provides a PowerShell cmdlet called Start-EVDatabaseUpgrade, which you can use to upgrade all Enterprise Vault databases.
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 |
Veritas.EnterpriseVault.12.Reports.mp | Required so that reports can be viewed. |
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 the target 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).