Skip to main content

Migration

In Open iT, a migration refers to moving the software installation from one machine to another, typically involving a change in hardware, operating system environment, or infrastructure (e.g., transferring from one server to a new host).

A migration may also be performed when moving between major software versions, such as migrating from version 9.19 to version 10.2.

This guide walks you through the CLIMS Server migration process. It includes step-by-step instructions on preparing both source and destination environments, transferring necessary files, and validating the system after migration. Follow this guide carefully to minimize downtime and avoid potential issues during the migration process.

Prerequisites​

Accomplish the following items before migrating:

  1. Export the RavenDB database. Perform a complete database backup.

  2. Take a snapshot of the current CLIMS system. Capture the exact state of the CLIMS system for post-migration health checking and assessment. Record the number of connected clients and license daemons.

Install the New CLIMS Server​

Start by installing the target version 10 of CLIMS Server on the new environment.

CLIMS Server Installation

Update the Client-Server Connection​

Direct the CLIMS Clients to the new CLIMS Server.

  1. Access the old CLIMS Server web interface.

  2. Go to the Clients page.

  3. Click on any of the connected clients.

  4. Go to the Configuration page.

  5. Click on Main.json to download a copy of the file.

  6. Open the downloaded <hostname>_Main.json using any text editor.

  7. Change the value of Server to the new CLIMS Server URL.

    Main.json
    {
        "Main":  {
            "Network":  {
                "Server": "https://new-clims.customer.openit.com"
            },

  8. Save the file as Main.json.

  9. Move the updated Main.json file to the Remote directory of the old CLIMS Server environment, which is C:\Program Files\OpeniT\Zero\Configuration\Remote by default.

    This enables file distribution to all connected clients.

note

Recommended reading: Remote Directory in the CLIMS Server

Upgrade the old CLIMS Server and Clients​

Proceed by upgrading the old CLIMS Server to a version between the current and target versions.

For example, if the old CLIMS Server is 9.19.400, upgrade to any version 9.19 lower than version 10.

CLIMS Server Upgrade to Version 9.19

Continue by upgrading the CLIMS Clients through the newly upgraded CLIMS Server.

CLIMS Client Upgrade through the Web Interface

Upgrade the CLIMS Clients through the New CLIMS Server​

Once the CLIMS Clients are connected to the new CLIMS Server, upgrade the clients again to match the CLIMS Server version.

CLIMS Client Upgrade through the Web Interface

Import the RavenDB Database to the New CLIMS Server​

Finalize the migration process by transferring the old CLIMS Server's RavenDB database to the new CLIMS Server.

Import the RavenDB Database

Health Check​

For a quick health check, compare the snapshots from the old CLIMS system to the new CLIMS system.

  1. Check if all expected CLIMS Clients are up and connected to the CLIMS Server.

  2. Check if the new CLIMS system has the same count of license daemon.

  3. Check usages per license manager.