Skip to content

Commit cf00c18

Browse files
committed
removing automatic failover for LA
1 parent d5d53c8 commit cf00c18

File tree

3 files changed

+43
-63
lines changed

3 files changed

+43
-63
lines changed

docs/products/postgresql/crdr/crdr-overview.md

Lines changed: 35 additions & 49 deletions
Original file line numberDiff line numberDiff line change
@@ -14,15 +14,13 @@ import crdrSwitchover from "@site/static/images/content/figma/crdr-switchover.pn
1414
import crdrRevert from "@site/static/images/content/figma/crdr-revert.png";
1515
import crdrSwitchback from "@site/static/images/content/figma/crdr-switchback.png";
1616

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
1918
failure.
2019

2120
## Region-wide outage
2221

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:
2624

2725
- Check your monitoring and alerts, and watch the following metrics:
2826
- Instances, nodes, services failures
@@ -39,12 +37,14 @@ of reasons. To do that, you can:
3937
The CRDR setup is a pair of integrated multi-node services, sharing credentials and a
4038
DNS address but located in different regions. CRDR peer services may be hosted on 1-3 nodes.
4139

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.
4848

4949
The CRDR cycle is a sequence of actions involving CRDR peer services aimed at enabling and
5050
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
6666
- Failed
6767

6868
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.
7070

7171
- Standby
7272

@@ -96,12 +96,9 @@ and the RRS is the **Passive** service replicating from the PRS.
9696

9797
### Recovery transition
9898

99-
CRDR supports three types of the recovery transition:
99+
CRDR supports two types of the recovery transition:
100100

101-
- [Automatic failover](/docs/products/postgresql/crdr/crdr-overview#automatic-failover)
102-
- **Self-activating** response to a region-wide outage
103-
- **Destroys the primary service** and requires the primary service recreation to fail back.
104-
- [Manual failover](/docs/products/postgresql/crdr/crdr-overview#manual-failover)
101+
- [Failover](/docs/products/postgresql/crdr/crdr-overview#failover-to-the-recovery-region)
105102
- **Triggered by you** for any purposes other than a region-wide outage
106103
- **Destroys the primary service** and requires the primary service recreation to fail back.
107104
- [Switchover](/docs/products/postgresql/crdr/crdr-overview#switchover-to-the-recovery-region)
@@ -110,55 +107,44 @@ CRDR supports three types of the recovery transition:
110107

111108
#### Failover to the recovery region
112109

113-
[Failover to the RRS](/docs/products/postgresql/crdr/failover/crdr-failover-to-recovery) is
114-
performed either
115-
[automatically](/docs/products/postgresql/crdr/failover/crdr-failover-to-recovery) or
116-
[manually](/docs/products/postgresql/crdr/failover/crdr-failover-to-recovery). When completed, the
117-
PRS is **Failed** and the RRS is up and running as an **Active** service. To fail back to
118-
the PRS, it needs to be recreated first.
110+
You trigger a
111+
[failover to the RRS](/docs/products/postgresql/crdr/failover/crdr-failover-to-recovery)
112+
in the event of a region-wide outage or for testing purposes. When completed, the PRS is
113+
**Failed** and the RRS is up and running as an **Active** service. To fail back to the PRS,
114+
it needs to be recreated first.
119115

120116
<img src={crdrFailover} className="centered" alt="CRDR failover" width="100%" />
121117

122-
##### Automatic failover
123-
124-
In the event of a region-wide failure, a CRDR process is triggered automatically. The RRS
125-
takes over from the PRS so that your workloads remain available at all times during
126-
the region outage.
127-
128-
##### Manual failover
129-
130-
You trigger a failover to the RRS yourself for testing purposes: to simulate a
131-
disaster scenario and verify the disaster resilience of your infrastructure.
132-
133118
#### Switchover to the recovery region
134119

135-
[Switchover to the RRS](/docs/products/postgresql/crdr/failover/crdr-failover-to-recovery) is
136-
performed manually for testing, simulating a disaster scenario, or verifying the
137-
disaster resilience of your infrastructure. You trigger a switchover yourself at your
138-
convenient time. When completed, the PRS is **Passive** and the RRS is up and running as
139-
an **Active** service. To switch back to the primary service, no service recreation is
140-
needed.
120+
You trigger a
121+
[switchover to the RRS](/docs/products/postgresql/crdr/switchover/crdr-switchover) at your
122+
convenient time for testing, simulating a disaster scenario, or verifying the disaster
123+
resilience of your infrastructure. When completed, the PRS is **Passive** and the RRS is
124+
up and running as an **Active** service. To switch back to the primary service, no service
125+
recreation is needed.
141126

142127
<img src={crdrSwitchover} className="centered" alt="CRDR switchover" width="100%" />
143128

144129
### Recovery reversion
145130

146-
The recovery reversion is a manual operation you trigger to shift your workload back to
147-
the primary region and restore the CRDR setup to its original configuration. There are two
148-
types of recovery reversion:
131+
You trigger a recovery reversion to shift your workload back to the primary region and
132+
restore the CRDR setup to its original configuration.
133+
134+
There are two types of the recovery reversion:
149135

150136
- [Failback](/docs/products/postgresql/crdr/crdr-overview#failback-to-the-primary-region)
151-
- Reverts an
152-
[automatic failover](/docs/products/postgresql/crdr/crdr-overview#automatic-failover)
153-
or a [manual failover](/docs/products/postgresql/crdr/crdr-overview#manual-failover).
137+
- Reverts a
138+
[failover](/docs/products/postgresql/crdr/crdr-overview#failover-to-the-recovery-region).
154139
- Recreates the primary service.
155140
- [Switchback](/docs/products/postgresql/crdr/crdr-overview#switchback-to-the-primary-region)
156-
- Reverts a switchover.
141+
- Reverts a
142+
[switchover](/docs/products/postgresql/crdr/crdr-overview#switchover-to-the-recovery-region).
157143
- No need to recreate the primary service.
158144

159145
#### Failback to the primary region
160146

161-
The failback process consists of two steps you initiate manually at your convenience:
147+
The failback process consists of two steps you initiate at your convenience:
162148

163149
1. [Primary service recreation](/docs/products/postgresql/crdr/failover/crdr-revert-to-primary)
164150

@@ -177,7 +163,7 @@ The failback process consists of two steps you initiate manually at your conveni
177163

178164
#### Switchback to the primary region
179165

180-
You initiate a switchback manually at your convenience to switch the direction of the
166+
You initiate a switchback at your convenience to switch the direction of the
181167
replication and route the traffic back to the primary region. When completed, both the PRS
182168
and the RRS are up and running again: the PRS as an active service, and the RRS as a
183169
passive service.

docs/products/postgresql/crdr/failover/crdr-failover-to-recovery.md

Lines changed: 7 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -9,12 +9,11 @@ import RelatedPages from "@site/src/components/RelatedPages";
99
import Tabs from '@theme/Tabs';
1010
import TabItem from '@theme/TabItem';
1111

12-
Perform an emergency promotion of your recovery service when the primary region becomes unavailable.
12+
Move your workload to another region for disaster recovery or testing purposes.
1313

14-
In the event of a region outage,
15-
[failover](/docs/products/postgresql/crdr/crdr-overview#failover-to-the-recovery-region)
16-
happens automatically. To simulate a disaster and test the resilience of your
17-
infrastructure, you can also perform a manual failover.
14+
A [failover](/docs/products/postgresql/crdr/crdr-overview#failover-to-the-recovery-region)
15+
allows you to respond to a region outage or simulate a disaster and test the resilience of
16+
your infrastructure.
1817

1918
## Prerequisites
2019

@@ -25,15 +24,10 @@ infrastructure, you can also perform a manual failover.
2524
- [Aiven API](/docs/tools/api)
2625
- [Aiven Provider for Terraform](https://registry.terraform.io/providers/aiven/aiven/latest/docs)
2726

28-
## Automatic failover
29-
30-
[Automatic failover](/docs/products/postgresql/crdr/crdr-overview#automatic-failover) is
31-
enabled by default with your CRDR setup. It's triggered automatically in the event of a
32-
region outage.
27+
## Perform a failover
3328

34-
## Fail over manually
35-
36-
Initiate a [manual failover](/docs/products/postgresql/crdr/crdr-overview#manual-failover)
29+
Initiate a
30+
[failover](/docs/products/postgresql/crdr/crdr-overview#failover-to-the-recovery-region)
3731
using a tool of your choice:
3832

3933
<Tabs groupId="group1">

docs/products/postgresql/crdr/failover/list-failover.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title: Failover & failback
44

55
import DocCardList from '@theme/DocCardList';
66

7-
Perform a manual
7+
Perform a
88
[failover](/docs/products/postgresql/crdr/crdr-overview#failover-to-the-recovery-region)
99
to the recovery region, and later
1010
[revert](/docs/products/postgresql/crdr/crdr-overview#failback-to-the-primary-region) to

0 commit comments

Comments
 (0)