04-02-2018 07:20 AM - edited 03-17-2019 12:32 PM
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
04-02-2018 09:31 PM
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.
Reference document:
Please rate if helpful.
HTH,
Akansha Sharma
04-04-2018 03:52 AM
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
04-04-2018 11:31 AM
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:
Please rate the post if, helpful.
HTH,
Akansha Sharma
04-04-2018 11:32 AM
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:
Please rate the post if, helpful.
HTH,
Akansha Sharma
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide