Failover scenarios

Last Updated : Mar 24, 2023 |

Scenarios

Description

Unplanned total outage of DC1

Failure of Avaya Oceana® components and Avaya Aura® Communication Manager telephony infrastructure.

This failure mode results in unavoidable system downtime and the loss of all alerting, queued, and in-progress contacts.

Planned total outage of DC1

The controlled manual shutdown of DC1 and switchover to DC2.

Avaya Oceana® supports a maintenance mode. Avaya Oceana® does not add any new contacts to the queue in the maintenance mode so that agents can handle the existing queued contacts before the shutdown.

Unplanned total outage of Avaya Oceana® or Avaya Analytics™ components only at DC1.

Avaya Aura®, Communication Manager, and other applications remain operational.

Partial disaster recovery failure of Avaya Oceana® components at DC1 only.

You can switch the Contact Center functionality to DC2 if the Avaya Aura® infrastructure functionality and all other applications remain operational in DC1.

The Communication Manager and Application Enablement Services components continue to be operational in DC1. You must re-configure Avaya Oceana® components at DC2 and ensure that Avaya Oceana® components point to Application Enablement Services at DC2. You must also re-configure Application Enablement Services at DC2 to communicate with the Communication Manager at DC1.

Important:

  • Retain the same administration settings while DC2 is functioning. If you make any changes, Avaya Oceana® handles the changes similar to an ESS switchover.

  • This failure mode does not support Avaya WebRTC Connect voice and video calls.

Unplanned total outage of Communication Manager at DC1

Failure of the Communication Manager at DC1.

If failure of the Communication Manager results in a switchover to the ESS at DC2, you must manually switchover Avaya Oceana® components to DC2.

When you identify the failure of Communication Manager, you must immediately commence the manual switchover of all Avaya Oceana® channels to ensure that Avaya Oceana® voice routing is operational without delay.

Unplanned partial outage of Avaya Oceana® components at DC1

The failure of one or more Avaya Oceana® components at DC1.

When you identify the failure of an Avaya Oceana® component, you must recover the component at DC1 or perform one of the following actions:

  • Partial disaster recovery to DC2.

  • Full switchover to DC2.

When a partial failure occurs, you must determine whether the downtime to recover the components or the disruption caused by a partial or full switchover is preferable.

Split WAN

WAN outage.

Avaya Oceana® does not support an active-active mode of operation; therefore, if a split WAN occurs, DC1 operates in isolation from DC2.

The data replication for Avaya Aura® System Manager, Avaya Control Manager, Unified Collaboration Administration (UCA), and Omnichannel Provider (OCP) breaks temporarily. After the WAN connection is restored, Avaya Oceana® components synchronize data from DC1 to DC2. The synchronization depends on the WAN outage time.

Avaya Oceana® components can buffer only a limited number of changes that DC2 synchronizes after recovery. After reaching the buffer limit, Avaya Oceana® components start to overwrite the oldest changed records. When an extended WAN outage occurs, you must manually synchronize data from DC1 to DC2.