Veritas Enterprise Vault™ Upgrade Instructions
- About this guide
- Before you begin
- Points to note when upgrading from Enterprise Vault 11.0
- About this chapter
- Vault service account requires a new SQL permission
- Enterprise Vault 12.1 requires uniform SQL collation
- Order of upgrade in an environment with Compliance Accelerator or Discovery Accelerator
- Enabling fast browsing for Enterprise Vault Search
- eDiscovery Platform compatibility with Enterprise Vault
- Support for Outlook 2013 SP1 on the Enterprise Vault server
- Automatic migration of content conversion settings
- Improved consistency when applying a retention period to moved items
- Points to note when upgrading from Enterprise Vault 12
- 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
- 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
- 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
Preparing for the upgrade of Domino mailbox archiving
This section describes how to prepare your Domino servers for the upgrade of Domino mailbox archiving.
Complete the following procedure on all Enterprise Vault Domino Gateway servers and on all Domino mail servers on which you have updated these forms to include the Enterprise Vault customizations:
Forms9.nsfForms85.nsfForms8.nsf
Note:
The following procedure requires you to replace the forms files with the original Domino versions. When you replace the forms files you lose any non-Enterprise Vault customizations that you made to them. If you made any non-Enterprise Vault customizations to the forms files, you must reapply these changes to the files after you have upgraded Enterprise Vault.
To prepare for the upgrade of Domino mailbox archiving
- Stop the HTTP task.
- Skip this step for Domino 9.
Delete
Forms85_x.nsfif it exists on the server. - Skip this step for Domino 9.
Replace the
Forms85.nsf,and Forms8.nsffiles with the original Domino versions that you backed up before you installed the previous version of Enterprise Vault. - If the forms databases have replication enabled, the changes that EVInstall makes are replicated to all Domino mail servers. If you want to prevent the replication to other mail servers, disable the replication of
Forms8.nsf,Forms85.nsf, andForms9.nsf. - Update the ACLs on the original Domino
.nsffiles to give Manager access to the ID of the user that will run EVInstall.