1. Support
  2. Knowledge base
  3. 100023744
Supported upgrade paths for Enterprise Vault (EV), Compliance Accelerator (CA) and Discovery Accelerator (DA).

Supported upgrade paths for Enterprise Vault (EV), Compliance Accelerator (CA) and Discovery Accelerator (DA).

Article: 100023744
Last Published: 2023-03-06
Ratings: 11 2
Product(s): Enterprise Vault

Problem

Supported upgrade paths for Enterprise Vault (EV), Compliance Accelerator (CA), and Discovery Accelerator (DA).

Cause

For new features or fixes to be obtained for Enterprise Vault (EV), Compliance Accelerator (CA) or Discovery Accelerator (DA), upgrades to the next major and / or minor releases must be completed. The order in which the products are upgraded can affect the functionality and supportability of the products. 

Solution

Note that the information below is for the Major Releases of Enterprise Vault.  Any Minor Release (for example: 12.3) or Update Release (for example: 12.3.1) is included in the major release scope for upgrades. Note that upgrading to an Update Release requires upgrading to the appropriate Major Release and Minor Release prior to upgrading to the Update Release version (for example: 11.0.1 to 12.3 to 12.3.1.
 
ENTERPRISE VAULT:


  
--------------------------------------------------------------------------------------
NOTES: 
  1. When upgrading EV in an environment with CA and / or DA, the suggested product upgrade sequence is:
    1. DA
    2. CA
    3. EV on all EV servers
    4. EV binaries or EV-API on the DA server when DA is installed on a stand-alone server
    5. EV binaries or EV-API on the CA server when CA is installed on a stand-alone server
  2. The version of CA or DA must be greater than or equal to the installed version of EV.  For example, if EV 12.0 is installed, CA and/or DA must also be at the 12.0 or greater release. The exception to this rule is when CA is to be upgraded to 11.0 SP1 or later where EV must first be upgraded to 11.0 SP1 or later as noted above.
  3. Update Releases must first have the base release installed and databases upgraded.  For example, to upgrade from EV 12.5.0 to EV 14.2.1, you must first upgrade to EV 14.2.0, upgrade the databases and then upgrade to EV 14.2.1 and upgrade the databases again.
  4. When upgrading EV in a 14.2 or older environment with CA and / or DA to the 14.3 or greater release, the required product upgrade sequence is:
    1. EV on all EV servers
    2. EV binaries or EV-API on the DA server when DA is installed on a stand-alone server
    3. DA
    4. EV binaries or EV-API on the CA server when CA is installed on a stand-alone server
    5. CA
----------------------------------------------------------------------------------------
 
Note that the information below is for the Major and Minor level releases of Compliance Accelerator.  Any Update Release (for example: 12.3.1) is included in the Minor Release scope of the Minor Release for upgrades. Note that upgrading to an Update Release requires upgrading to the appropriate Major Release and Minor Release prior to upgrading to the Update Release version (for example: 11.0.1 to 12.3 to 12.3.1).

COMPLIANCE ACCELERATOR:


--------------------------------------------------------------------------------------
NOTES:
  1. Enterprise Vault cannot be at a higher version than CA except during an upgrade from 14.2 or older to 14.3 or greater.  For example, CA 12.0.0 is not supported in an EV 14.0 installation.  The only exception to this rule is when upgrading CA to 11.0 SP1 or later wherein EV must first be upgraded to 11.0 SP1 or later to allow for the new Compliance Sampling through the EV Storage Service.  For example, when upgrading from EV and CA 12.0.0 to EV and CA 14.0, EV must first be upgraded to 14.0 before CA can be upgraded to 14.0.
  1. CA 11.0 must have the full EV binaries or EV Runtime API version 10.0.1 or greater or 11.0 installed on the CA server.
  2. CA 11.0 SP1 (11.0.1) must have the full EV binaries or EV Runtime API version 11.0.1 installed on the CA server as well as the full EV binaries version 11.0.1 on all EV servers in the environment.
  3. CA 14.0 must have the full EV binaries or EV Runtime API version 12.0.0 or greater or 14.0 installed on the CA server.
  4. Update Releases must first have the base release installed and databases upgraded.  For example, to upgrade from CA 12.5.0 to CA 14.2.1 / VAS 3.2, you must first upgrade to CA 14.2.0 / VAS 3.2, upgrade the databases and then upgrade to CA 14.2.1 / VAS 3.2 and upgrade the databases again.
--------------------------------------------------------------------------------------
Note that the information below is for the Major and Minor level releases of Discovery Accelerator.  Any Update Release (for example: 12.3.1) is included in the Minor Release scope of the Minor Release for upgrades. Note that upgrading to an Update Release requires upgrading to the appropriate Major Release and Minor Release prior to upgrading to the Update Release version (for example: 11.0.1 to 12.3 to 12.3.1).

DISCOVERY ACCELERATOR:
 
--------------------------------------------------------------------------------------
  NOTES:
  1. Enterprise Vault cannot be at a higher version than DA except during an upgrade from 14.2 or older to 14.3 or greater.  For example, DA 12.0.0 is not supported in an EV 12.1.0 installation.  This means that DA must be upgraded before EV.
  1. DA 11.0 must have the full EV binaries or EV Runtime API version 10.0.1 or greater or 11.0 installed on the DA server.
  2. DA 14.0 must have the full EV binaries or EV Runtime API version 12.0.0 or greater or 14.0 installed on the DA server.
  3. Update Releases must first have the base release installed and databases upgraded.  For example, to upgrade from DA 12.5.0 to DA 14.2.1, you must first upgrade to DA 14.2.0, upgrade the databases and then upgrade to DA 14.2.1 and upgrade the databases again.
 

Was this content helpful?

Article Languages