Versions Compared

Old Version 6

changes.mady.by.user CXDev

Saved on

compared with

New Version Current

changes.mady.by.user CXDev

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The overall architecture will look like below.

...

Note

Note

Each Node represents a VM.

For the hardware resilience, these nodes/VMs should be on two physical servers. If all the VMs are deployed on the same physical server, it will provide only VM level resilience and fault tolerance.

Failover scenarios

When the Primary or Secondary node is down
The system will switch to the other active node.

Impact

All applications will continue to work after the seamless failover.

Recovery

NA

When Primary and Secondary nodes are down

Impact

All applications and services will not work.

Recovery

The manual intervention is required to recover the system.

When primary or secondary SupervisorTools instance is down
The other active instance will make itself primary as it becomes aware of the failure of the primary node using KeepAlived

Impact

All read/write operations on the Supervisor Tools will continue to function seamlessly. No impact on live calls. With MSSQL Server failover cluster, there’ll be no loss of data.

Recovery

For any integration between the IVR and the web app, the Supervisor Tools APIs used in the IVR scripts will seamlessly failover to the secondary instance to provide the appropriate call treatment.

The failover for the web users will also be seamless with a virtual web portal IP.

When primary and secondary Supervisor Tools instances are down

Impact

All read/write operations on the datastore will fail.

Recovery

A manual intervention is required to resume the datastore operations.

...