Clustered Systems: Master Node

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

  1. 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
  2. When prompted, enter Yes to transfer application data from the previous Oracle Communications Session Delivery Manager installation.
    [X]  1 - Proceed with database migration   [Default]
    [ ]  2 - Cancel and exit setup
    Do you want to continue Yes/No?  Yes
  3. 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 SDM 7.5M3 application data to SDM 8.0. 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.
  4. 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
  5. When prompted, enter Yes to continue.
  6. 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
  7. Press Enter and continue to the Typical Installation.
  8. Once you have completed the Typical Installation 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.