PEC-REP/Current/GCXIPEGuide/HADR - Revision history

WikiSysop at 19:00, April 7, 2022

2022-04-07T19:00:33Z

Show changes

Richard.pfeiffer@genesys.com: Published

2021-11-18T21:17:53Z

Published

Barry.grenon@genesys.com: Published

2021-09-23T15:15:11Z

Published

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

2021-09-08T19:48:33Z

Tony.gilchrist@genesys.com: Published

2021-09-01T18:29:55Z

Published

Tony.gilchrist@genesys.com: Published

2021-06-30T17:51:42Z

Published

Tony.gilchrist@genesys.com: Published

2021-06-29T19:46:17Z

Published

New page

{{ArticleUnstructured
|Standalone=No
|DisplayName=High availability and disaster recovery
|TocName=High availability and disaster recovery
|Context=Find out how Genesys Customer Experience Insights (GCXI) provides disaster recovery in the event the service goes down.
|ComingSoon=No
|PEPageType=7617f411-2cb3-47cc-b3d8-5c3f8d0e295a
}}
{{ServiceHA
|ServiceId=1f419ea4-5e6e-4052-abc1-c56ff55106e2
|HA=active-active
|DR=active-active
|NoHA=No
}}
By default, GCXI provides High Availability support using StatefulSets with 2 x Pods in Active-Active mode, which form a MicroStrategy cluster. GCXI does not support autoscaling.

GCXI does not support Disaster Recovery or any kind of cross-regional deployment. In most scenarios, GCXI is deployed in customer's primary region only. If GCXI is deployed in supplementary regions, each such deployment is completely independent from each other. Pods in different regions do not communicate with each other.

===Multi-region availability===
{| class="wikitable"
! class="confluenceTh" |Functionality
! class="confluenceTh" |Pattern
! colspan="1" class="confluenceTh" |Design
! colspan="1" class="confluenceTh" |Dependencies
! colspan="1" class="confluenceTh" |Limitation
! class="confluenceTh" |Activate
! colspan="1" class="confluenceTh" |Activate Time
! class="confluenceTh" |Rollback
! colspan="1" class="confluenceTh" |Rollback Time
! colspan="1" class="confluenceTh" |Changes
|-
| class="confluenceTd" |GCXI
| class="confluenceTd" |Pilot-Light
| colspan="1" class="confluenceTd" |GCXI deployed in the primary region. The DB and File storage are replicated to secondary region.
| colspan="1" class="confluenceTd" |GIM DB must be available in the secondary region
| colspan="1" class="confluenceTd" |None
| class="confluenceTd" |
*If needed teardown GCXI in primary region
*Change secondary region replicated DB and File storage to R/W and have them replicated to primary region (if available)
*Deploy GCXI in secondary region using the replicated DB and File storage
*Notify tenant to use the secondary GCXI tile <strike>in Portal</strike>
| colspan="1" class="confluenceTd" |under 15 mins
| class="confluenceTd" |
*Teardown secondary region GCXI with a pipeline.
*Deploy GCXI in primary region
**If the DB and File storage is replicated to primary region, change to R/W and have replicated to secondary region
**If the DB and File storage is not replicated to primary region, recreate them using backup data from the secondary region.
*Update URL for GCXI tile <strike>in Portal</strike>
| colspan="1" class="confluenceTd" |under 15 mins
| colspan="1" class="confluenceTd" |Change the GCXI pipeline to convert replicated DB and File Storage to R/W and deploy GCXI

Make sure the Postgres DB is replication across regions

Change the File storage to GZRS Azure files to do replication of the data

*Reports themselves - email or link <br />
*Cube - in memory - refreshes on period basis. All the links

Add secondary GCXI tile <strike>to Portal pipeline</strike>
|-
|}

===Regional failover support===
<br />

===Primary Region failure===
{| class="wikitable"
| class="confluenceTd" |'''Functionality'''
| class="confluenceTd" |'''Operational Impact'''
| class="confluenceTd" |'''Representative Experience'''
| class="confluenceTd" |'''Customer Experience'''
|-
| colspan="1" class="confluenceTd" |GCXI
| colspan="1" class="confluenceTd" |without GCXI functionality 15 mins
| colspan="1" class="confluenceTd" |No Impact
| colspan="1" class="confluenceTd" |No Impact
|}

===Secondary Region Failure===
{| class="wikitable"
| class="confluenceTd" |'''Functionality'''
| class="confluenceTd" |'''Operational Impact'''
| class="confluenceTd" |'''Representative Experience'''
| class="confluenceTd" |'''Customer Experience'''
|-
| class="confluenceTd" |GCXI
| class="confluenceTd" |No Impact
| class="confluenceTd" |No Impact
| class="confluenceTd" |No Impact
|}

===Data Sovereignty and Regulations===
{| class="wikitable"
! class="confluenceTh" |Functionality
! class="confluenceTh" |Design
! colspan="1" class="confluenceTh" |Changes
! class="confluenceTh" |Investigations
|-
| class="confluenceTd" |GCXI
| class="confluenceTd" |There is potential sensitive data in the reports
| colspan="1" class="confluenceTd" |TBD
| class="confluenceTd" |
|}

@@ Line 2: / Line 2: @@
 |ServiceId=1f419ea4-5e6e-4052-abc1-c56ff55106e2
 |HA=38dc863f-3a55-4299-a98a-13454fa5e2bf
-|DR=active-active
+|PrimaryUnit=e9ffb7b5-3b53-449d-a637-5c616ddf5e74
-|AddIncluded=No
+|AddIncluded=Yes
 |NoHA=No
 }}

@@ Line 1: / Line 1: @@
 {{ArticleServiceHA
 |ServiceId=1f419ea4-5e6e-4052-abc1-c56ff55106e2
-|HA=active-active
+|HA=38dc863f-3a55-4299-a98a-13454fa5e2bf
 |DR=active-active
 |NoHA=No
 }}
@@ Line 38: / Line 39: @@
 **If the DB and File storage is replicated to primary region, change to R/W and have replicated to secondary region
 **If the DB and File storage is not replicated to primary region, recreate them using backup data from the secondary region.
 *Update URL for GCXI
 | colspan="1" class="confluenceTd" |under 15 mins
 | colspan="1" class="confluenceTd" |Change the GCXI pipeline to convert replicated DB and File Storage to R/W and deploy GCXI

@@ Line 13: / Line 13: @@
 |NoHA=No
 }}
-By default, GCXI provides High Availability support using StatefulSets with 2 x Pods in Active-Active mode, which form a MicroStrategy cluster. GCXI does not support autoscaling.
+By default, GCXI provides High Availability support using StatefulSets with 2 x Pods in Active-Active mode, which form a MicroStrategy cluster. GCXI does not support autoscaling. High Availability is not applicable to RAA.
 GCXI does not support Disaster Recovery or any kind of cross-regional deployment. In most scenarios, GCXI is deployed in customer's primary region only. If GCXI is deployed in supplementary regions, each such deployment is completely independent from each other. Pods in different regions do not communicate with each other.

@@ Line 39: / Line 39: @@
 *Change secondary region replicated DB and File storage to R/W and have them replicated to primary region (if available)
 *Deploy GCXI in secondary region using the replicated DB and File storage
-*Notify tenant to use the secondary GCXI tile <strike>in Portal</strike>
+*Notify tenant to use the secondary GCXI tile in Portal
 | colspan="1" class="confluenceTd" |under 15 mins
 | class="confluenceTd" |
@@ Line 46: / Line 46: @@
 **If the DB and File storage is replicated to primary region, change to R/W and have replicated to secondary region
 **If the DB and File storage is not replicated to primary region, recreate them using backup data from the secondary region.
-*Update URL for GCXI tile <strike>in Portal</strike>
+*Update URL for GCXI
 | colspan="1" class="confluenceTd" |under 15 mins
 | colspan="1" class="confluenceTd" |Change the GCXI pipeline to convert replicated DB and File Storage to R/W and deploy GCXI