Preparing Session Monitor for Taking the Backup

Disconnect all probes: both standalone and SBC probes, connected to the Mediation Engine Connector so that the Mediation Engine does not receive any traffic. For the Fraud Monitor, disconnect the Mediation Engines connected to Fraud Monitor. For the Mediation Engine Connector, disconnect the Mediation Engine connected to the Mediation Engine Connector.

Run this command to stop the pldclean service. (Applicable to the Mediation Engine only):

sed -i "s/^12/#&/" /opt/oracle/ocsm/usr/share/pld/configs/me/pld-me.cron.d
sed -i "s/^42/#&/" /opt/oracle/ocsm/usr/share/pld/configs/me/pld-me.cron.d
systemctl restart crond.service

This helps prevent any data loss caused by the pldclean service (the pldclean service deletes data regularly based on the retention configured in the PSA.)

From the PSA Page, create Historical System Diagnostics with the Create savepoint and Include mysqldump check boxes enabled.

Download a copy of the Diagnostics created in the above step, to your Backup location. For more information, see System Diagnostics' section in the Session Monitor Release 5.2 Installation Guide.

Note:

Creating the Savepoint is applicable only for the Mediation Engine. Also, selecting the Create savepoint and Include mysqldump check boxes is mandatory for taking a backup.

Go through each page of the PSA and take screenshots of the page. This data is needed during the Session Monitor Fresh Installation phase of the Restore procedure, (if required).

Run the following commands to stop all Session Monitor services:

source /opt/oracle/ocsm/ocsm_env.sh
pld-systemctl stop

This helps in preventing the Session Monitor services from writing any new data during the Backup process.

Note:

Capture any additional configurations from the UI before stopping the Session Monitor services as needed.

If the Backup location selected is on a Remote Server (either the Remote Server selected as part of Strategy-1 OR the newly created target machine as part of Strategy-2), generate an SSH Key to authorize the Remote Server for passwordless SSH logins by executing below steps on the current Session Monitor Server (which is going to be backed up):

Note:

If the file authorized_keys is already present under the /root/.ssh/ folder in the Remote Server, rename that file as authorized_keys_orig using this command:

mv /root/.ssh/authorized_keys /root/.ssh/authorized_keys_orig

Log in to the CLI of the current Session Monitor Server as the root user.

Type ssh-keygen and keep pressing the Enter key until the SSH Key is generated.

For example:

[root@localhost ~]# ssh-keygen
 
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
SHA256:ez/o897z0lOwGElieJUYlMA25W8gd071IKtuzUqga1g root@localhost

Run the following command to copy the SSH Key generated, onto the Remote Server:

ssh-copy-id -i ~/.ssh/id_rsa.pub <User>@<Remote_Server_IP>

For example:

[root@localhost ~]# ssh-copy-id -i ~/.ssh/id_rsa.pub root@10.11.12.13
 
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"
The authenticity of host '10.11.12.13 (10.11.12.13)' can't be established.
ECDSA key fingerprint is SHA256:sEAQZxN2alX76X1rPZcVRKARGczMIZaa+Z4CNTQuTd8.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
root@10.11.12.13's password:
 
Number of key(s) added: 1

Run the following commands to install rsync and parallel on the current Session Monitor Server:

yum install rsync
yum install parallel