This section describes the things to be taken care after restore procedure is complete which enables you to start using your Session Monitor.

1. Start Session Monitor services by running the following command:

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

2. Run the command to restart the crond services:

   systemctl start crond.service

3. Certificate Exchange: Before logging into the system, you will need to exchange certificates between respective nodes as required.
4. Configuring connection between nodes:
   Post restore, you will need to re-establish all the connections between all nodes such as:

   • Mediation Engine-Probe
   • Mediation Engine-Mediation Engine Connector

   • For Mediation Engine and Standalone Probe Machine, Delete older Mediation Engine details from the Probe and then add the new Mediation Engine details.
   • For Mediation Engine and Embedded Probe Machine, delete the Probe info from Mediation Engine from admin→Settings→Probe section to re-establish connection
5. Multi VSP: Post the restore, multi-vsp will be disabled by default. You will need to enable multi-vsp again as per your requirement.
6. SELinux: SELinux state won't be restored. Post restore, you can Enable or Disable SELinux again as per your requirement. SELinux policy modules have changed with Session Monitor Release 6.0, see Enabling SELinux for information.
7. Changing nginx to httpd: httpd changes won't be restored. Post restore procedure Apache Web Server will be reverted back to NGINX. You will need to change back from nginx to httpd again as per your requirement.
8. External Authentication: For External Authentication enabled Machines, re-enable 'External Authentication' from Settings as these changes will not be restored. Post restore, it is mandatory to copy the new pld.conf template from /opt/oracle/ocsm/etc/httpd/conf.d/pld.conf to /etc/httpd/conf.d/ folder and configure External Authentication details again. This ensures new fixes and any changes in the pld.conf template to be applied on the system.
9. Retention: For systems with retention configured in Mediation Engine, If backup and restore procedure took more than 24 hours, it is recommend to adjust retention by adding x days (n+x) and then readjust retention back to your existing one after n days. x = Number of days taken for backup and restore, n = Existing Retention Configured.
   For example, A system has Calls Retention set to 10 days. The backup and restore procedure took 2 Days. Once Restore is completed, in Mediation Engine we need to set Calls Retention as 12 Days (10 + 2). Then after 10 Days you need to set Retention back to 10 Days.
10. System Diagnostics: Keep safely in the new Session Monitor Server the backup copy of the System Diagnostics taken during backup process which will be required in future diagnostics.
11. You can now rename the /root/.ssh/authorized_keys_orig file in the Remote Server to /root/.ssh/authorized_keys
    The Restore procedure is now complete.