" /> SpeechMiner Disaster Recovery? - Genesys CTI User Forum

Author Topic: SpeechMiner Disaster Recovery?  (Read 1746 times)

Offline hsujdik

  • Hero Member
  • *****
  • Posts: 541
  • Karma: 30
SpeechMiner Disaster Recovery?
« on: October 18, 2018, 03:17:39 PM »
Advertisement
Hi all,

Has anybody deployed SpeechMiner+GIR for a Disaster Recovery scenario? Any thoughts and considerations that should be accounted for?

Genesys doesn't officially support this deployment, and we are trying to work around this gap. So far, no success.

Here's what we have done:
- Shared storage between both sites on WebDav
- Shared storega for the keystore for RCS
- Shared database for SpeechMiner UPlatform
- Two redundant pairs of RCS and RPS
- One IVR Profile for each DataCenter (Primary / DR) pointing to corresponding RPS for call metadata
- Redundant ICONs
- One cluster of Cassandra and ElasticSearch covering both DataCenters

On Disaster Recovery scenario, we attempt to change the RCS mapping on SpeechMiner so it points to either the primary datacenter or the DR datacenter.

Any suggestions or is it really not feasible at all?

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: SpeechMiner Disaster Recovery?
« Reply #1 on: October 19, 2018, 12:17:16 PM »
What do you want to exactly achieve - High-availability mode or business continuity mode?

Offline hsujdik

  • Hero Member
  • *****
  • Posts: 541
  • Karma: 30
Re: SpeechMiner Disaster Recovery?
« Reply #2 on: October 19, 2018, 02:22:47 PM »
A "Disaster Recovery" mode - does not need to be fully automated (some manual actions may be performed), but needs to be able to access, playback and download the recordings made by the Primary site, and be able to record interactions that would be accessible by the Primary site once the primary site is recovered.

Offline hsujdik

  • Hero Member
  • *****
  • Posts: 541
  • Karma: 30
Re: SpeechMiner Disaster Recovery?
« Reply #3 on: October 21, 2018, 06:31:39 PM »
We actually found out what was wront... There was incorrect configuration for towards IRWS url in the RPS configuration file. After changing that and some manual configuration on the SMConfig interface for the recording RCS path, the Disaster Recovery mode was successfully achieved.