Important notes for planning HCL VersionVault upgrades

Before you begin the upgrade process, review information about known issues and limitations, gathering required information, and completing any necessary system configuration changes.

  • To run HCL Compass on the same computer with HCL VersionVault, both products must be at the same version level.
  • If you plan to upgrade the servers, upgrade them in the following order: the license server, the registry server, the VOB, and view servers.
  • Before upgrading to a new release, complete all deliver operations that are in progress.
  • If you plan to install or upgrade HCL VersionVault on a Solaris operating system with global and non-global zones, see Deploying HCL VersionVault on Solaris zones.
Important: If you are switching to the 64-bit version of HCL VersionVault from the 32-bit version, you must first uninstall the 32-bit version of VersionVault before installing the 64-bit version. Note that when you uninstall VersionVault, the CCM.preserve directory is created. This directory contains any custom settings from the VersionVault product that you uninstalled. When you reinstall the VersionVault product on the same machine, the installation process discovers the CCM.preserve directory and presents options to let you use the preserved settings from the previous installation for the new installation or to ignore them.