1 Migrating from 3.3.x.x to 4.0.0.0

This chapter provides detailed information and instructions on migrating from a session monitor release 3.3.x to release 4.0 without losing the call history, namely the database entries and the block storage.

Recommended Approach

The official recommendation is to deploy a new 4.0 Mediation Engine (or ME+Probe) machine that runs in parallel to the 3.3 machine for as long as it takes to generate the desired amount of call history.

This approach minimizes any potential downtime and effectively eliminates the risk of losing or corrupting data.

Supported Scenario

In case deploying on a new machine is not an option (see above), the customer may choose to follow the migration process, in order to reuse the same machine.

Note:

The migration process is only supported for ME (Mediation Engine) or ME+Probe machines in a two-disk configuration.

WARNING:

The migration process involves installing a new operating system on the host and there is a risk of overwriting/corrupting/losing data.

The customer is responsible for backing up the data before attempting to start the migration process.

Migration Steps

This section provides instruction for migrating from a Session Monitor release 3.3.x to release 4.0.

Migrating on Debian Operating System

This section provides instructions to migrating from session monitor release 3.3.x to release 4.0 on a Debian operating system.

To migrate to a session monitor release 4.0:

  1. Perform an upgrade to the latest 3.3.x release and make sure that the upgrade was successful.

  2. Download the Configuration Savepoint and System Diagnostic package from the 3.3.x release OCSM and keep as a back up.

  3. Stop mysql and all Session Monitor services.

     systemctl stop mysql.service
 pld-systemctl stop

  4. Create a backup directory on the secondary disk and run the following commands:

    mkdir -pv /var/vsi/backup
cp -v /root/.my.cnf /var/vsi/backup/.my.cnf
cp -v /etc/fstab /var/vsi/backup/fstab
tar cvfz /var/vsi/backup/etc-iptego.tgz /etc/iptego
tar cvfz /var/vsi/backup/mysql.tgz /var/lib/mysql

    Note:

    You can also copy the migration helper script from an already deployed system and run it with the prepare action, OCSM_PREFIX/usr/share/pld/scripts/admin/migration-helper.sh -a prepare.

  5. Shut down the machine.

The next step is to install Oracle Linux, and Session Monitor on the machine, either by using the official Oracle Linux iso and the Session Monitor rpm, or the Session Monitor iso.

Important:

Regardless of the selected method, leave the secondary disk untouched.

For example, make sure that it is not selected for partitioning in the Oracle Linux installer and by selecting No secondary disk in the Session Monitor installer. See, Figure 1-1.

Figure 1-1 Secondary Disk

Surrounding text describes Figure 1-1 .

Migrating on an Oracle Linux Operating System

This section provides instructions to migrating from session monitor release 3.3.x to release 4.0 on an Oracle Linux operating system.

To migrate to a session monitor release 4.0:

  1. Configure the machine using PSA - the configuration should be as close as possible to the previous state.

  2. In the disk usage page, make sure that the secondary disk does not appear. If it does, unmount it and refresh.

  3. Complete the configuration.

  4. Stop mysql and all Session Monitor services.

    systemctl stop mysqld.service
pld-systemctl stop

  5. Mount the secondary disk to OCSM_PREFIX/var/vsi .

  6. Run the migration helper script with the migrate action:

    OCSM_PREFIX/usr/share/pld/scripts/admin/migration-helper.sh -a migrate

The migration is complete.