The EDM can be deployed in one of the following supported configurations:
Standalone EDM non-DB HA: EDM is deployed alone on one SQL Server.
Standalone EDM DB HA: EDM is deployed alone on two SQL Servers.
EDM/ACM co-res DB HA: EDM is deployed co-res with the ACM databases on two SQL Servers.
Note:
The co-resident deployment of Avaya Control Manager databases and the EDM is not supported in a non-DB HA configuration (one SQL Server per Datacenter) in production environments.
Avaya Oceana® provides High Availability (HA) of Context Store External Data Mart (EDM) when:
EDM is installed co-resident with Avaya Control Manager databases on Microsoft SQL Server using Microsoft SQL Server Enterprise Edition and Windows AlwaysOn Advanced Availability Groups (AAG).
EDM is installed standalone on Microsoft SQL Server without Avaya Control Manager databases using Microsoft SQL Server Standard Edition and Windows AlwaysOn Basic Availability Group (BAG).
Important:
For a non-DB HA configuration in production environments, the co-resident deployment of Avaya Control Manager and EDM is not supported.
In an availability group, you must have a maximum of two EDM replicas.
The following version combinations are tested for the co-resident deployment using AAG:
The following version combinations are tested for the standalone EDM using BAG:
Note:
Avaya Oceana® also supports the External Data Mart database running the specified Microsoft SQL Server versions in the table above on any supported version of Windows Operating System.
For supported version combinations, see the following: