Cisco Media Sense node failure

Nishad Ismail · ‎04-02-2018

Hi All,

We have HA deployment for the Cisco MediaSense with Primary & Secondary

How to restore the Mediasence ,When one of the MediaSense goes corrupted or goes down

Regards,

NKI

ItalkNetworks · ‎04-02-2018

Hi Nishad,

Please follow the below procedure for restoring media sense node from backup.

+++ Restore MediaSense Node From Backup

Use this procedure to restore a MediaSense node from a backup.

Before you restore virtual machine, you must have one backup from which to restore.

Procedure

Step 1

Using the VMware vSphere Client, log in and connect to the VMware vSphere Hypervisor 5.1 server using the IP address or hostname of the vCenter Server, and entering the root username and password credentials. The vSphere Client window appears.

Step 2

Select File > Deploy OVF Template. The Deploy OVF Template appears.

Step 3

Enter the path from where you want to restore the MediaSense, or browse to the path and click Next. The selected OVF Template Details appears.

Step 4

Enter the name and location of the deployed template and click Next.

Note

The name should be unique within the inventory folder.

Step 5

Select the destination where you want to store the virtual machine files and click Next.

Step 6

Select the format in which you want to store the virtual disks and click Next. The deployment settings appears.

Step 7

Click Finish to start deployment. The Deploying Test screen appears showing the progress of the deployment.

Reference document:

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/mediasense/11/Design_Guide/CUMS_BK_MC36D963_00_mediasense-srnd_11/CUMS_BK_MC36D963_00_mediasense-srnd_10-5_chapter_01001.html#task_ED31D1B5E3BF48FE9B30064BB046F66F

Please rate if helpful.

HTH,

Akansha Sharma

Nishad Ismail · ‎04-04-2018

Hi Akansha Sharma,

What will happen when i restore only one MediaSense server which crashed .

There is chance of DATA mismatch in Both mediaSense server

Do we have recommendation for restore scenario's..

Regards,

NKI

ItalkNetworks · ‎04-04-2018

Hi Nishad,

Please refer to the below for data replication in Media sense High availability deployment

Data Replication and Recovery for Primary or Secondary Node

If either the primary or secondary server goes out of service, the database replication process proceeds as follows:

MediaSense continues to write data to the recording database. Because the data cannot be replicated to the out of service node, Informix stores the data in the ora_ersb replication buffer on the node that is still working. If the node that is out of service comes back up before ora_ersb is full, replication is automatically restored and the data in ora_ersb is synchronized between both nodes.
If one node is out of service for an extended period, the ora_ersb buffer on the working node may fill up. If ora_ersb reaches 90 percent of its capacity, the system automatically stops replication on the working node (which then acts like a single node). The system does this to prevent ora_ersb from getting too full and the system from becoming dysfunctional.
If replication is stopped on the working node, it is automatically restored after the out-of-service node comes back into service. User intervention is not required. After replication is restored, data sync jobs are launched to compare both the meta data and the configuration data on both nodes and to synchronize this data.

You can check the data sync job status by running the following CLI command on either one of the nodes:

show db_synchronization status [db_ora_meta|db_ora_config]

+++ As per the document, If replication is stopped on the working node, it is automatically restored after the out-of-service node comes back into service. User intervention is not required. After replication is restored, data sync jobs are launched to compare both the meta data and the configuration data on both nodes and to synchronize this data.

Reference document:

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/mediasense/11/User_Guide/CUMS_BK_M5B01864_00_ms-user-guide-11/CUMS_BK_M5B01864_00_ms-user-guide-105_chapter_01.html

Please rate the post if, helpful.

HTH,

Akansha Sharma

ItalkNetworks · ‎04-04-2018

Hi Nishad,

Please refer to the below for data replication in Media sense High availability deployment

Data Replication and Recovery for Primary or Secondary Node

If either the primary or secondary server goes out of service, the database replication process proceeds as follows:

+++ Media Sense continues to write data to the recording database. Because the data cannot be replicated to the out of service node, Informix stores the data in the ora_ersb replication buffer on the node that is still working. If the node that is out of service comes back up before ora_ersb is full, replication is automatically restored and the data in ora_ersb is synchronized between both nodes.

+++ If one node is out of service for an extended period, the ora_ersb buffer on the working node may fill up. If ora_ersb reaches 90 percent of its capacity, the system automatically stops replication on the working node (which then acts like a single node). The system does this to prevent ora_ersb from getting too full and the system from becoming dysfunctional.

+++ If replication is stopped on the working node, it is automatically restored after the out-of-service node comes back into service. User intervention is not required. After replication is restored, data sync jobs are launched to compare both the meta data and the configuration data on both nodes and to synchronize this data.

+++ You can check the data sync job status by running the following CLI command on either one of the nodes:

show db_synchronization status [db_ora_meta|db_ora_config]

+++ As per the document, If replication is stopped on the working node, it is automatically restored after the out-of-service node comes back into service. User intervention is not required. After replication is restored, data sync jobs are launched to compare both the meta data and the configuration data on both nodes and to synchronize this data.

Reference document:

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/mediasense/11/User_Guide/CUMS_BK_M5B01864_00_ms-user-guide-11/CUMS_BK_M5B01864_00_ms-user-guide-105_chapter_01.html

Please rate the post if, helpful.

HTH,

Akansha Sharma