Upgrade the Session Delivery Manager Cluster

Note:

Ensure that you are currently running OCSDM, Release 7.5M3. If you are running any version of OCSDM prior to Release 7.5M3, you cannot install OCSDM Release 8.x. After installing OCSDM 8.x, you can upgrade to OCSDM 9.0 from OCSDM 8.x or 8.x.x.

Note:

It is recommended that you take a cold DB backup from the master node before proceeding with upgrade.

Use following summary of tasks to upgrade your OCSDM server cluster:

See the Session Delivery Manager Software Distribution Media section in the Oracle Communications Session Delivery Manager Release Notes for more information about the names and descriptions of the software files that you need to do this upgrade.
Download the OCSDM application image file to each OCSDM server cluster node in the same base directory in which the previous software was initially installed.
You must unzip the tar file on each node to create the OCSDM installation directory, which contains the installation program used to run the installation. Refer to the Create a Session Delivery Manager Installation Directory section for more information.
If you are upgrading Report Manager, the Oracle Database and Oracle BI Publisher must be running before you upgrade OCSDM so that Report Manager database data is migrated.
Start the installation on the master cluster node and migrate the application data from the previous release to this master cluster node.
Continue the installation on the master node.
Migrate the application data from the previous release to each cluster replica node.
With the introduction of OCSDM, Release 8.0, you must select one server to start in the cluster only (which in this case is the master node). Once this server is started and operational, you can start the other server(s) in the cluster.

Start the Session Delivery Manager Cluster Upgrade

Note:

The previous release of Oracle Communications Session Delivery Manager must manage at least one device to be upgraded successfully.

Login to the master cluster server node as the root user.
Navigate to the OCSDM installation bin directory.
For example:
```
cd /<sdm-install-directory>/AcmePacket/NNC<version>/bin
```
Run the setup application with the setup.sh script. The setup.sh application determines that a migration of the application data needs to occur from the current version to 9.x. If you are migrating from OCSDM Release 7.5M3, specific plugin(s) may need to be installed based on the product devices (SBCs, E-SBCs, or both).
```
./setup.sh
```
Note:
A warning message appears if you have less than the recommended minimum physical memory. Proceeding without the recommended minimum physical memory may result in performance degradation.
WARNING:
This process may take several minutes to complete. Interrupting the setup.sh process risks corrupting the system.
The data migration tool automatically detects the previous release. When you are prompted, select that you have a clustered system and use the following section to complete your upgrade.

Migrate Application Data on the Master Cluster Node

Transfer the application data on the master node (member) of the cluster system.

Enter 1 to transfer application data from the previous Oracle Communications Session Delivery Manager installation.

Setup has detected that database migration needs to be performed.
The migration process involves backing up the existing database and then
performing various operations to migrate the database to the current version.
Depending on size of the existing database and the operations to be performed,
this process may take up to an hour to complete, however you can cancel and
rollback the process at any time by pressing the <a> key followed by <enter>.
Note that database migration MUST be performed before setup can continue.
[X]  1 - Proceed with database migration   [Default]
[ ]  2 - Cancel and exit setup
Please select an option [1] 1

When prompted, enter Yes to transfer application data from the previous OCSDM installation.

[X]  1 - Proceed with database migration   [Default]
[ ]  2 - Cancel and exit setup
Do you want to continue Yes/No?  Yes

When you are prompted, specify the directory path on your server where you downloaded the requested product plugin(s). Once the directory path(s) to the product plugin(s) are provided, the migration process continues migrating current application data to the new release. During this process, the setup application asks you if you want to transfer a backup of the migrated database (DB) to other members of the cluster. If you answer yes, a backup is done and transferred to the targeted members of the server cluster.

Enter 1 to copy the transferred database to other cluster nodes.

Your existing setup is configured for a clustered environment.  Setup on all
other nodes in your cluster will require the migrated database archive just
created.  Setup can now attempt to copy this archive via SFTP to other cluster
nodes.
Note that if you skip this step, you must manually copy the migrated database
archive to all other nodes in the cluster, as this archive will be required
during setup on the other cluster nodes
[X]  1 - Copy the migrated database archive to other cluster nodes   [Default]
[ ]  2 - Do not copy the migrated database archive
Please select an option [1] 1

When prompted, enter Yes to continue.

Enter the username, password, and folder path for the SFTP credentials for each cluster node when prompted.

Provide SFTP credentials for cluster node 2.2.2.2:
username:  [] myuser
password:  [] xxxxx
remote folder path:  [        ] /home/myuser
remote folder path:  [/home/myuser]

For example, a successful application data transfer shows information similar to the following:

cluster node: 2.2.2.2
destination file: /home/myuser/ColdBackup_2012_02_13_112911_db.tar.gz
result:  SUCCEEDED
cluster node: 3.3.3.3
destination file: /home/otheruser/ColdBackup_2012_02_13_112911_db.tar.gz
result:  SUCCEEDED
Press <enter> to continue
Database migration is now complete.
Press <enter> to continue with setup

Press Enter and continue to the setup, where you can select your OCSDM installation type. You must re-enter the setup parameters that you used when you previously setup OCSDM. Refer to the Typical Installation, Custom Installation, Easy Installation, or Headless Installation chapter for more information.
Once you have completed the setup on the master node, go to the Migrate Application Data on Each Cluster Replica Node section to complete the cluster upgrade on the replica nodes in the cluster.

Migrate Application Data on Each Cluster Replica Node

Transfer the application data to each replica node (member) of the cluster system.

Pre-requisites: Ensure that you have shut down the server, downloaded and unzipped the application image file, and started the setup application on the replica node before starting this task.

Enter 1 to continue importing the database backup.

Setup has detected that database migration needs to be performed.
The migration process involves backing up the existing database and then
performing various operations to migrate the database to the current version.
Depending on size of the existing database and the operations to be performed,
this process may take up to an hour to complete, however you can cancel and
rollback the process at any time by pressing the <a> key followed by <enter>.
Note that database migration MUST be performed before setup can continue.
[X]  1 - Proceed with database migration   [Default]
[ ]  2 - Cancel and exit setup
Please select an option [1] 1

Enter Yes to continue.

[X]  1 - Proceed with database migration   [Default]
[ ]  2 - Cancel and exit setup
Do you want to continue Yes/No? Yes

Enter 1 to continue.

Your existing setup is configured for a clustered environment.  For your
existing environment, setup must be run on cluster node 1.1.1.1 prior
to running setup on any other cluster node (including this one).  When setup
is run on cluster node 1.1.1.1, a migrated master database archive
file will be produced.
If you have already run setup on 1.1.1.1 and either allowed setup to
automatically copy the database archive file to this node, or have copied this
file manually, please select option [1] below.  Otherwise, please select
option [2] below to cancel setup.  Then run setup on 1.1.1.1 before
running setup again on this node.
[X]  1 - Specify location of migrated master database archive file   [Default]
[ ]  2 - Cancel and exit setup
Please select an option [1] 1

Enter Yes to continue.

[X]  1 - Proceed with database migration   [Default]
[ ]  2 - Cancel and exit setup
Do you want to continue Yes/No? Yes

Enter the full path to the database backup and enter yes to continue the import process.

Enter migrated master database archive file path:
[        ] /home/myuser/ColdBackup_2012_02_13_112911_db.tar.gz
[/home/myuser/ColdBackup_2012_02_13_112911_db.tar.gz]
backing up existing database....done
restoring the migrated master database...done
Restore migrated master database archive succeeded
Press <enter> to continue with setup

Press Enter to continue the Typical Installation and later the Custom Installation of Oracle Communications Session Delivery Manager (depending on your installation requirements of Oracle Communications Session Delivery Manager). These installation(s) must be completed to use the current Oracle Communications Session Delivery Manager software version on this replica node system.
Press Enter and continue to the setup, where you can select your OCSDM installation type. You must re-enter the setup parameters that you used when you previously setup OCSDM. Refer to the Typical Installation, Custom Installation, Easy Installation, or Headless Installation chapter for more information.
Repeat the previous steps if you need to transfer application data on another replica node (member) of the cluster system.

Transfer the Migrated Application Database Backup to the Replica Node Manually

Use this task if you opted not to copy the migrated database archive when you migrated application data on the master cluster node when upgrading OCSDM from a previous release.

Log into the replica node, shut it down and do a backup of the application database (also known as a cold backup). See the Backup Databases on a Shutdown Server section in the Session Delivery Manager Server Database Maintenance chapter of the Oracle Communications Session Delivery Manager Administration Guide for more information.
Migrate the application data on this replica node from the backed up application database. See the Migrate Application Data on Each Cluster Replica Node section in this chapter for more information.
Repeat the previous steps for any remaining cluster node.