Omnichannel Database utilizes the Cache mirroring feature for Campus HA. A mirror can provide HA through automatic failover where a failure of the Cache instance causes the other instance to take over automatically.

All Omnichannel Database clients connect to the active mirror through a Virtual IP address, which is always bound to an interface on the currently active database.

When you configure Omnichannel Database, you can do data mirroring with one of the following:

• HA active and standby Omnichannel Database servers within one Avaya Oceana® site (Data Center 1) with automatic failover

  In this configuration, you do not have a geo-redundant backup.

• Active Omnichannel Database server in Data Center 1 and Geo backup Omnichannel Database server in the geo-redundant site (Data Center 2) with no automatic failover

  For information about this configuration, see Avaya Oceana® and Avaya Analytics™ Disaster Recovery.

• HA active and standby Omnichannel Database servers within Data Center 1 with automatic failover and Geo backup Omnichannel Database server in Data Center 2 with no automatic failover

  For information about this configuration, see Avaya Oceana® and Avaya Analytics™ Disaster Recovery.

In Omnichannel Database HA, Omnichannel Database:

• Records the transcripts of Chat, Email, Messaging, SMS, and Social sessions for Customer History at the end of the interaction.

• Requires its deployment in an active-standby configuration on separate physical servers in the same subnet with a Round Trip Time (RTT) less than 120ms.

• Automatically switches over to the standby server during outage of the active server or lack of communication from the active server. After the switchover, the standby server becomes the active server.

  Data on the standby server remains updated in real time.