Supported upgrade paths for Enterprise Vault, Compliance Accelerator / Veritas Advanced Surveillance and Discovery Accelerator

Important EV Notes:

1. The information below is for the Base and Update Maintenance Release versions of EV.
2. Upgrading to an Update Maintenance Release requires first upgrading to the appropriate Base Release, including all EV databases, prior to upgrading to the Update Maintenance Release version. For example, to upgrade from EV 14.0.1 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.
3. The version of CA/VAS or DA must be greater than or equal to the installed version of EV.  For example, if EV 14.0 is installed, CA/VAS and/or DA must also be at 14.0, or greater, release. The exception to this rule is when CA/VAS or DA is to be upgraded to 14.3 or later, EV must first be upgraded to 14.3 or later to allow for use of the proximity operators of NEAR, BEFORE and NOT WITHIN as part of search criteria (see the exception below).
4. When upgrading EV in an environment with CA/VAS and / or DA, the documented and recommended product upgrade sequence is as follows, with the exception as noted below:
   1. DA
   2. CA/VAS
   3. EV on all EV servers
   4. EV binaries or EV-API on the DA server(s) when DA is installed on stand-alone servers
   5. EV binaries or EV-API on the CA/VAS server(s) when CA/VAS is installed on stand-alone servers
5. Exception: As new Search operators were introduced in CA/VAS and DA 14.3 and newer, when upgrading EV from a 14.2 or earlier environment with CA/VAS and / or DA to a 14.3 or newer version, the required product upgrade sequence is:
   1. EV on all EV servers
   2. EV binaries or EV-API on the DA server(s) when DA is installed on stand-alone server(s)
   3. DA
   4. EV binaries or EV-API on the CA/VAS server(s) when CA is installed on stand-alone servers
   5. CA

COMPLIANCE ACCELERATOR 12.x:

DISCOVERY ACCELERATOR 14.x:

Important DA Notes:

1. The information below is for the Base and Update Maintenance Release versions of DC.
2. Upgrading to an Update Maintenance Release requires first upgrading to the appropriate Base Release, including all DA databases, prior to upgrading to the Update Maintenance Release version. For example, to upgrade from DA 14.0.1 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.
3. When upgrading from DA 14.5.1 to 14.5.2, there are no database schema changes. As such, there is no database upgrade required for the Configuration, Customer or Custodian Manager databases. It is required to upgrade the Clients from 14.5.1 to 14.5.2.
4. When upgrading from DA 15.0.1 to 15.0.2, there are no database schema changes. As such, there is no database upgrade required for the Configuration, Customer or Custodian Manager databases. It is required to upgrade the Clients from 15.0.1 to 15.0.2.
5. 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 14.0 installation.  The only exception to this rule is when upgrading DA to 14.3 or later wherein EV must first be upgraded to 14.3 or later to allow for the new proximity operators of NEAR, BEFORE and NOT WITHIN to be usable.  For example, when upgrading from EV and DA 12.0.0 to EV and DA 14.3, EV must first be upgraded to 14.3 before DA can be upgraded to 14.3.
6. 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.
7. Update Maintenance Releases must first have the Base release installed and databases upgraded. For example, to upgrade from DA 14.4.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.