Installing the ClusterDBMigrationService-3.9.0.3

Last Updated : Mar 30, 2026 |

About this task

The ClusterDBMigrationService-3.9.0.3 service is delivered and pre-loaded as a part of Element Manager release 3.9. The ClusterDBMigrationService-3.9.0.3 service is versioned as a 3.9 service. However, the snap-in is compatible and intended for installation on 3.8.1.1 Avaya Breeze® platform clusters.

You must install the ClusterDBMigrationService on the Avaya Breeze® platform 3.8.x cluster before you backup the Avaya Oceana® databases and migrate to Avaya Breeze® platform 3.9.0.3 with Avaya Oceana® 3.10.0.2. This enables you to restore the existing cluster database backed up from 3.8.x to the cluster following the upgrade of the cluster servers to Avaya Breeze® platform 3.9.

Important:

The ClusterDBMigrationService is required for the cluster database backup of snap-ins that need to be restored to Avaya Breeze® platform 3.9.0.3 with Avaya Oceana® 3.10.0.2.

As a precaution, take a remote backup of your cluster databases before installing the ClusterDBMigrationService. If a reversion is necessary, you can still use these backups on Avaya Breeze® platform 3.8.x and earlier nodes. When you install ClusterDBMigrationService on Avaya Breeze® platform cluster, the postgres compatibility version is permanently changed to postgres 13 and is no longer compatible with Avaya Breeze® platform 3.8.1.1 and before releases.

Procedure

  1. On the System Manager web console, click Elements > Avaya Breeze® > Service Management > Services.
  2. Select the ClusterDBMigrationService-3.9.0.3 service and click Install.
  3. Select the clusters on which you want to install the ClusterDBMigrationService-3.9.0.3 service and click Commit.
  4. To see the status of the service installation, click Refresh.
    • Installed: A green check mark indicates that the snap-in has completed installation on all the Avaya Breeze® platform servers in the cluster.

    • Installing: A yellow exclamation mark enclosed in a triangle indicates that the snap-in has not completed installation on all the servers.

    Perform this step only for Cluster 1.