The Disaster Recovery (DR) limitations are as follows:

• Automatic switchover: If a disaster occurs in DC1, you must manually move all operations to DC2. Disaster recovery does not support automatic switchover from DC1 to DC2.

• Call preservation: For planned and unplanned switchovers, not all active voice contacts move with Avaya Oceana® during the switchover. All existing voice contacts are anchored in the Avaya Aura® Communication Manager. The calls use the same fallback mechanism to the Elite mechanism as standard Elite calls.

• Partial switchover: Avaya Oceana® supports only sharing of the following applications between both data centers for partial disaster recovery switchover:

  • Avaya Aura® System Manager primary

  • Avaya Aura® Communication Manager primary

  • Avaya Control Manager primary

  • Application Enablement Services servers in Data Center 2

• Avaya Aura® Communication Manager switchover to ESS: Requires a corresponding Avaya Oceana® switchover.

• Cross-WAN Application Enablement Services link to ESS: No Device, Media, and Call Control (DMCC) over WAN. Application Enablement Services servers in DC1 must connect to the Communication Manager only.

  Note:

  Application Enablement Services (AES) servers in DC2 can temporarily connect to the main site Avaya Aura® Communication Manager in a partial disaster recovery failover.

• WAN outage scenario: Active-Active mode is not available.

• Avaya Aura® Communication Manager: The Communication Manager configuration changes while the DC2 is active.

Avaya Oceana® disaster recovery supports a single disaster recovery site, a single ESS. Disaster recovery requires downtime while activating the DC2. It also mandates that the WAN delay is less than 50 milliseconds for Avaya Control Manager. In addition, the downtime may result in the loss of historical reporting data.