This page was last edited on February 13, 2019, at 20:50.
Comments or questions about this documentation? Contact us for support!
This deployment contains the following components:
The controlling site can be divided into two separate data centers:
There are no restrictions or configuration limitations to perform this, except that the data interlink between sites must contain satisfactory conditions. The following figure illustrates the described architecture:
The contact center behavior is the same as that in a deployment using a single pool for applications and users. The exception is that the complete failure of one of the user pools does not cause contact center failure. However, it reduces the availability of agents from the affected pool.
According to Microsoft documentation (see https://technet.microsoft.com/en-us/library/jj205184.aspx), the user experiences the following scenarios during a failover.
The recovery time depends on the administrator identifying the pool failure and initiating failover execution. This might take up to 60 minutes.
There are no restrictions in operations when the failover is completed and the environment is stabilized. The performance of the system might be slightly affected.
The behavior of paired pools during initial configuration or during failback (when the failed pool is restored) is similar to the behavior during failover.
Microsoft does not provide support for failover of the Application FE pool.