PEC-AD/Current/WWEPEGuide/HADR - Revision history

WikiSysop at 11:15, June 8, 2022

2022-06-08T11:15:52Z

Matthew.west@genesys.com: Published

2021-10-07T17:45:52Z

Published

Matthew.west@genesys.com: Published

2021-10-07T17:38:47Z

Published

Barry.grenon@genesys.com: Published

2021-09-23T15:13:25Z

Published

Matthew.west@genesys.com: Published

2021-09-17T20:20:28Z

Published

Ed.jamer@genesys.com at 19:47, September 8, 2021

2021-09-08T19:47:45Z

Julie.munn@genesys.com: Published

2021-06-29T17:36:18Z

Published

Julie.munn@genesys.com: Published

2021-06-29T14:24:54Z

Published

New page

{{ArticleUnstructured
|Standalone=No
|DisplayName=High availability and disaster recovery
|TocName=High availability and disaster recovery
|Context=Find out how Workspace Web Edition provides disaster recovery in the event the service goes down.
|ComingSoon=No
|PEPageType=7617f411-2cb3-47cc-b3d8-5c3f8d0e295a
}}
{{ServiceHA}}
To support High Availability and Disaster Recovery, Workspace Web Edition should be deployed as part of Genesys Web Services in multiple regions.

To maintain business continuity without requiring user manual switching to the backup region, the Workspace Web Edition application (browser-side) automatically fails over to the backup region when it detects a loss of connectivity to the primary region. The application notifies the agent (end user) of the failover operation in progress and might prompt for re-authentication.

Refer to the {{Link-SomewhereInThisVersion|manual=WWEPEGuide|topic=Architecture|display text=Architecture}} topic for information about HLA architecture.

===Smart Failover for Workspace Users===
Smart failover support for Workspace users is provided by Genesys Web Services and Applications (GWS).

[[File:SmartFailover 9.0.png]]

*SIP phone dual-registers to both data centers.
*SIP HA handles SIP Server failover.
*Various DNs are provisioned in both SIP Servers, so that agents can operate in either SIP Server deployment.
*An agent's browser is set up with a link to the Workspace application. For Smart Failover, DNS resolution is used to return the URL to the local data center's GWS/Workspace app with the address of the backup site specified as the URL parameter.
*CometD connection (through HTTPS) is maintained with the Workspace client.

===Workspace Agent Site Selection===
Workspace uses DNS to select and distribute Workspace agents across sites and load balance between nodes.

*The browser uses DNS to resolve the common URL address to the local site. The link to the backup site should also be included in the name resolution:
*;<code><nowiki>https://agents.xyz.com</nowiki> <br> <nowiki>https://agents.dc1.xyz.com?site1=agents.dc2.xyz.com</nowiki></code>
*The browser fetches the Workspace application from the data center specified in the DNS (DC1).
*Session stickiness persists the link from the browser app to the GWS instance handling the agent's desktop.

If there is an issue with the current site, Workspace senses this (due to the loss of the CometD connection) and reconnects to the DR site URL specified in the parameter (example, <code>?site1=agents.dc2.xyz.com</code>).

DNS configuration is an important element of this solution and depends on your load balancer/proxy. It needs to support name resolution to the local site, addition of the siteX URL parameter, and sticky sessions.

===Configuration Server===
Configuration Server Proxies are deployed in both data centers to handle requests for configuration information. One data center has a live Configuration Server for making updates. A cold standby pair exists within the other data center.

During a data center failure, the Configuration Server Proxies in the remaining data center handle requests. Configuration updates are not possible. If needed, the cold standby Configuration Server can be turned on in the remaining data center, assuming that configuration database replication is enabled between sites. If the cold standby Configuration Server is turned on, the Configuration Server Proxies need to re-establish a connection with the new operational Configuration Server. Expect performance impacts from switching over.

===Failover Scenarios===

====Voice Channel====
If the SIP phone loses connection to SIP Servers in one data center, it re-connects to SIP Servers in the other data center, based on SIP/dual registration protocol. Existing voice calls might be lost.

GWS monitors the connection to the SIP Server session. The connection drops when the SIP Server goes down. GWS notifies an application in the agent's browser about the Voice channel unavailability with the <code>ServiceStateChanged UNAVAILABLE</code> event.

====Workspace====
Workspace triggers a disaster recovery failover to another site based on the following triggers:

*DN unregistration (DNStateChanged Inactive event received)
*Voice channel unavailability (ServiceStateChanged UNAVAILABLE event received)
*CometD real-time channel loss
*Workspace initialization issues at login
*Registration failure for Softphone
*Registration failure for WebRTC

The Workspace application needs to authenticate in order to log in to the backup site. The single sign-on (SSO) integration automatically logs in to the backup site without requiring the agent to enter the password.

====Data Center====
If the entire data center fails, both the voice channel and the Workspace application fail. This impacts both CometD connections to the Workspace client, forcing it to reconnect to the backup site. The SIP endpoint also switches over to the other site.

@@ Line 3: / Line 3: @@
 |HA=ebe8e38b-3a96-46c1-86f4-f3b230efd7f7
 |DR=7e917f1a-3c94-4943-8363-8c7532b7f670
 |AddIncluded=No
 |NoHA=No

@@ Line 2: / Line 2: @@
 |ServiceId=9cbd9a42-4bdc-4205-948a-8c130eb304a2
 |HA=ebe8e38b-3a96-46c1-86f4-f3b230efd7f7
-|DR=active-active
+|DR=7e917f1a-3c94-4943-8363-8c7532b7f670
 |AddIncluded=No
 |NoHA=No

@@ Line 1: / Line 1: @@
 {{ArticleServiceHA
 |ServiceId=9cbd9a42-4bdc-4205-948a-8c130eb304a2
-|HA=N+1
+|HA=ebe8e38b-3a96-46c1-86f4-f3b230efd7f7
 |DR=active-active
 |AddIncluded=No

← Older revision		Revision as of 19:47, September 8, 2021
Line 1:		Line 1:
−	{{~~ArticleUnstructured~~	+	{{ArticleServiceHA}}
−	~~\|Standalone=No~~
−	~~\|DisplayName=High availability and disaster recovery~~
−	~~\|TocName=High availability and disaster recovery~~
−	~~\|Context=Find out how Workspace Web Edition provides disaster recovery in the event the service goes down.~~
−	~~\|ComingSoon=No~~
−	~~\|PEPageType=7617f411-2cb3-47cc-b3d8-5c3f8d0e295a~~
−	}}
−	~~{{ServiceHA~~}}
	To support High Availability and Disaster Recovery, Workspace Web Edition should be deployed as part of Genesys Web Services in multiple regions.		To support High Availability and Disaster Recovery, Workspace Web Edition should be deployed as part of Genesys Web Services in multiple regions.

@@ Line 28: / Line 28: @@
 *The browser uses DNS to resolve the common URL address to the local site. The link to the backup site should also be included in the name resolution:
-*;<code><nowiki>https://agents.xyz.com</nowiki> <br> <nowiki>https://agents.dc1.xyz.com?site1=agents.dc2.xyz.com</nowiki></code>
+*;<code><nowiki>https://agents.xyz.com</nowiki> <br> <nowiki>https://agents.dc1.xyz.com?site-1=agents.dc2.xyz.com</nowiki></code>
 *The browser fetches the Workspace application from the data center specified in the DNS (DC1).
 *Session stickiness persists the link from the browser app to the GWS instance handling the agent's desktop.
-If there is an issue with the current site, Workspace senses this (due to the loss of the CometD connection) and reconnects to the DR site URL specified in the parameter (example, <code>?site1=agents.dc2.xyz.com</code>).
+If there is an issue with the current site, Workspace senses this (due to the loss of the CometD connection) and reconnects to the DR site URL specified in the parameter (example, <code>?site-1=agents.dc2.xyz.com</code>).
-DNS configuration is an important element of this solution and depends on your load balancer/proxy. It needs to support name resolution to the local site, addition of the siteX URL parameter, and sticky sessions.
+DNS configuration is an important element of this solution and depends on your load balancer/proxy. It needs to support name resolution to the local site, addition of the site-X URL parameter, and sticky sessions.
 ===Configuration Server===

@@ Line 1: / Line 1: @@
-{{ArticleServiceHA}}
+{{ArticleServiceHA
 To support High Availability and Disaster Recovery, Workspace Web Edition should be deployed as part of Genesys Web Services in multiple regions.
@@ Line 5: / Line 11: @@
 Refer to the {{Link-SomewhereInThisVersion|manual=WWEPEGuide|topic=Architecture|display text=Architecture}} topic for information about HLA architecture.
-<!--
 ===Smart Failover for Workspace Users===
 Smart failover support for Workspace users is provided by Genesys Web Services and Applications (GWS).
@@ Line 54: / Line 60: @@
 ====Data Center====
-If the entire data center fails, both the voice channel and the Workspace application fail. This impacts both CometD connections to the Workspace client, forcing it to reconnect to the backup site. The SIP endpoint also switches over to the other site.-->
+If the entire data center fails, both the voice channel and the Workspace application fail. This impacts both CometD connections to the Workspace client, forcing it to reconnect to the backup site. The SIP endpoint also switches over to the other site.