You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/products/postgresql/crdr/crdr-overview.md
+35-49Lines changed: 35 additions & 49 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,15 +14,13 @@ import crdrSwitchover from "@site/static/images/content/figma/crdr-switchover.pn
14
14
import crdrRevert from "@site/static/images/content/figma/crdr-revert.png";
15
15
import crdrSwitchback from "@site/static/images/content/figma/crdr-switchback.png";
16
16
17
-
The cross-region disaster recovery (CRDR) feature ensures your business continuity by
18
-
automatically recovering your workloads to a remote region in the event of a region-wide
17
+
The cross-region disaster recovery (CRDR) feature ensures your business continuity by recovering your workloads to a remote region in the event of a region-wide
19
18
failure.
20
19
21
20
## Region-wide outage
22
21
23
-
Although CRDR detects a region failure and recovers your workloads in another region
24
-
automatically, you still might want to look into the region status yourself for a variety
25
-
of reasons. To do that, you can:
22
+
CRDR allows you to cope with the primary region failure by initiating a recovery transition
23
+
to another region. To identify a region outage, look into the region status:
26
24
27
25
- Check your monitoring and alerts, and watch the following metrics:
28
26
- Instances, nodes, services failures
@@ -39,12 +37,14 @@ of reasons. To do that, you can:
39
37
The CRDR setup is a pair of integrated multi-node services, sharing credentials and a
40
38
DNS address but located in different regions. CRDR peer services may be hosted on 1-3 nodes.
41
39
42
-
- Primary region service (**PRS**) is the original service you use unless there's a region
43
-
outage, in which case it hands over to the RRS. As soon as the region is up again and
44
-
the PRS is ready, the PRS takes back control from the RRS.
45
-
- Recovery region service (**RRS**) is the service you create for disaster recovery purposes.
46
-
This service takes over from the PRS when a region is down and hands over to the PRS when
47
-
the region and the PRS are up and running again.
40
+
- Primary-region service is the original service you use on regular basis. It hands over to
41
+
the recovery-region service when you initiate a failover or a switchover. When you
42
+
initiate a failback or a switchback, the primary-region service takes back control from
43
+
the recovery-region service as soon as the infrastructure is up and running again.
44
+
- Recovery-region service is the service you create for disaster recovery purposes. It
45
+
takes over from the primary-region service when you initiate a failover or a switchover.
46
+
When you initiate a failback or a switchback, the recovery-region service hands over to
47
+
the primary-region service as soon as the infrastructure is up and running again.
48
48
49
49
The CRDR cycle is a sequence of actions involving CRDR peer services aimed at enabling and
50
50
executing CRDR as well as resuming the original service operation.
@@ -66,7 +66,7 @@ Throughout the CRDR cycle, CRDR peer services or service nodes go into the follo
66
66
- Failed
67
67
68
68
A CRDR peer service is **Failed** when it's defunct or unreachable after failing over
69
-
automatically or manually in the event of a region outage. Only a PRS can be failed.
69
+
in the event of a region outage. Only a PRS can be failed.
70
70
71
71
- Standby
72
72
@@ -96,12 +96,9 @@ and the RRS is the **Passive** service replicating from the PRS.
96
96
97
97
### Recovery transition
98
98
99
-
CRDR supports three types of the recovery transition:
99
+
CRDR supports two types of the recovery transition:
0 commit comments