November 2017
E90428-01
Oracle Communications Session Monitor Migration Guide from 3.3.x.x to 4.0.0.0,
Copyright 2017, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.
This page provides detailed information and instructions on how a customer can migrate from version 3.3 to version 4.0 without losing the call history, namely the database entries and the block storage.
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.
In case deploying 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 2-disk configuration.
WARNING
The migration process involves installing a new Operating System on the host and there is the risk of overwriting/corrupting/losing data.
The customer is responsible for backing up the data before attempting to start the migration process.
Perform an upgrade to the latest 3.3 version and make sure that the upgrade was successful.
Get a savepoint and a diagnostics package.
Stop mysql and all Session Monitor services.
systemctl stop mysql.service
pld-systemctl stop 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/mysqlNOTE: 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.
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.
Configure the machine using PSA - the configuration should be as close as possible to the previous state.
In the disk usage page, make sure that the secondary disk does not appear. If it does, unmount it and refresh.
Complete the configuration.
Stop mysql and all Session Monitor services.
systemctl stop mysqld.service
pld-systemctl stopMount the secondary disk to OCSM_PREFIX/var/vsi .
Run the migration helper script with the migrate action:
OCSM_PREFIX/usr/share/pld/scripts/admin/migration-helper.sh -a migrateThe migration is complete.