Knowledgebase

Search:     Advanced search

Migrating from the 32-bit Helix ALM Server to the 64-bit Server on the Same Computer

Article ID: 463  |  Last updated: 27 Apr, 2017

This article explains how to migrate data from the 32-bit Helix ALM Server to the 64-bit server for the same Helix ALM version on the same computer. If you need to move the server installation to a different computer, see Moving the Server Between Computers.

Note: If you need to upgrade Helix ALM, we recommend upgrading all 32-bit client and server components first to make sure the upgrade is successful before migrating to the 64-bit server. See the installation help for information about upgrading Helix ALM.

Migrating to the 64-bit server

  1. Make sure the computer you are installing the 64-bit Helix ALM Server on meets the minimum system requirements.
  2. Stop the server if it is running.
  3. Back up the server database and projects.
  4. If you use SQL Server, create unique 64-bit ODBC DSNs to replace the 32-bit DSNs configured for Helix ALM databases.
  5. If you are also migrating to the 64-bit Helix ALM License Server, see Migrating from the 32-bit License Server to the 64-bit License Server on the Same Computer before installing the 64-bit license server.
  6. Install the 64-bit server.
  7. If you use Oracle, install the 64-bit Oracle OCI Client.
  8. Configure projects.

Installing the 64-bit server

Note: In Helix ALM (and TestTrack 2015.1 - 2016.1), the 32-bit and 64-bit server components are bundled in the same installer. Run the installer you used to install the 32-bit components again and select to install 64-bit applications. For TestTrack 2015.0.2 and earlier, 32-bit and 64-bit server components are in separate installers.

Windows

  1. Run the Helix ALM installer and select the components to install.

    Make sure to install the 64-bit server components in a different directory than the 32-bit components.

    Note: Select ‘Do not start the Helix ALM Server’ and ‘Do not start the Helix ALM License Server’ when prompted so you can move your existing data before starting the 64-bit server.

  2. Copy the TTServDb directory, including all project subdirectories and files, from the 32-bit Helix ALM application directory to the 64-bit directory.

    By default, the 32-bit application directory is C:\Program Files (x86)\Perforce\Helix ALM and the 64-bit directory is C:\Program Files\Perforce\Helix ALM. If you use Oracle, PostgreSQL, or SQL Server databases, the server and project database locations depends on the RDBMS database type and configuration.

Linux

  1. Run the Helix ALM installer and select the components to install.

    The 32-bit and 64-bit servers are installed in the same directory. The default application directory is /var/lib/HelixALM.

Back to migrating steps


Installing the 64-bit Oracle OCI Client

If you use Oracle, download and install the 64-bit Oracle OCI Client. The required Oracle libraries must be installed in the 64-bit Helix ALM application directory.

Back to migrating steps


Configuring projects

  1. Start the Helix ALM License Server and Helix ALM Server.
  2. Start the Helix ALM Server Admin Utility.
  3. Check the server database location in the server options to make sure the correct database is used.

    If you use an Oracle, PostgreSQL, or SQL Server database, you may need to change the database configuration.

  4. If you use SQL Server, add connections for the DSNs you created for projects.
  5. Make sure all projects you use are added and loaded.

    If projects do not load, you made need to upgrade them to the current version.

Back to migrating steps

Article ID: 463  |   Last updated: 27 Apr, 2017
Tags
database move 64-bit migrate

Prev   Next
Helix ALM Cannot Connect to the License Server     ODBC Join Examples