Skip to content

Commit fd3ec4d

Browse files
committed
Promote replica to R/W
1 parent 613feda commit fd3ec4d

File tree

2 files changed

+37
-2
lines changed

2 files changed

+37
-2
lines changed

articles/postgresql/hyperscale/concepts-read-replicas.md

Lines changed: 25 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: jonels-msft
66
ms.service: postgresql
77
ms.subservice: hyperscale-citus
88
ms.topic: conceptual
9-
ms.date: 06/17/2022
9+
ms.date: 06/30/2022
1010
---
1111

1212
# Read replicas in Azure Database for PostgreSQL - Hyperscale (Citus)
@@ -85,6 +85,30 @@ psql -h c.myreplica.postgres.database.azure.com -U citus@myreplica -d postgres
8585

8686
At the prompt, enter the password for the user account.
8787

88+
## Replica promotion to independent server group
89+
90+
You can promote a replica to an independent server group that is readable and
91+
writable. A promoted replica no longer receives updates from its original, and
92+
promotion can't be undone. Promoted replicas can have replicas of their own.
93+
94+
There are two common scenarios for promoting a replica:
95+
96+
1. **Disaster recovery.** If something goes wrong with the primary, or with an
97+
entire region, you can open another server group for writes as an emergency
98+
procedure.
99+
2. **Migrating to another region.** If you want to move to another region,
100+
create a replica in the new region, wait for data to catch up, then promote
101+
the replica. To avoid potentially losing data, you may want to disable writes
102+
to the original server group, after replica catches up, as you promote the
103+
replica.
104+
105+
> [!NOTE]
106+
>
107+
> There isn't yet a way in the Azure portal to view replication lag. To
108+
> determine when a replica has sufficiently caught up, you can insert a signal
109+
> row in a table of the original server group, and wait for it to appear in the
110+
> replica.
111+
88112
## Considerations
89113

90114
This section summarizes considerations about the read replica feature.

articles/postgresql/hyperscale/howto-read-replicas-portal.md

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: jonels-msft
66
ms.service: postgresql
77
ms.subservice: hyperscale-citus
88
ms.topic: how-to
9-
ms.date: 06/17/2022
9+
ms.date: 06/30/2022
1010
---
1111

1212
# Create and manage read replicas in Azure Database for PostgreSQL - Hyperscale (Citus) from the Azure portal
@@ -66,6 +66,17 @@ steps:
6666
3. Enter the name of the primary server group to delete. Select **Delete** to
6767
confirm deletion of the primary server group.
6868

69+
## Promote a replica to an independent server group
70+
71+
To promote a server group replica, follow these steps:
72+
73+
1. In the Azure portal, open the **Replication** page for your server group.
74+
75+
2. Select the **Promote** icon for the desired replica.
76+
77+
3. Select the checkbox indicating you understand the action is irreversible.
78+
79+
4. Select **Promote** to confirm.
6980

7081
## Delete a replica
7182

0 commit comments

Comments
 (0)