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: articles/postgresql/flexible-server/how-to-manage-high-availability-portal.md
+31-31Lines changed: 31 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,11 +15,11 @@ ms.date: 06/23/2022
15
15
16
16
This article describes how you can enable or disable high availability configuration in your Azure Database for PostgreSQL flexible server instance in both zone-redundant and same-zone deployment models.
17
17
18
-
High availability feature provisions physically separate primary and standby replica with the same zone or across zones depending on the deployment model. For more details, see [high availability concepts documentation](./concepts-high-availability.md). You may choose to enable high availability at the time of Azure Database for PostgreSQL flexible server instance creation or after the creation.
18
+
High availability feature provisions physically separate primary and standby replica with the same zone or across zones depending on the deployment model. For more information, see [high availability concepts documentation](./concepts-high-availability.md). You may choose to enable high availability at the time of Azure Database for PostgreSQL flexible server instance creation or after the creation.
19
19
20
-
This page provides guidelines how you can enable or disable high availability. This operation does not change your other settings including VNET configuration, firewall settings, and backup retention. Similarly, enabling and disabling of high availability is an online operation and does not impact your application connectivity and operations.
20
+
This page provides guidelines how you can enable or disable high availability. This operation doesn't change your other settings including VNET configuration, firewall settings, and backup retention. Similarly, enabling and disabling of high availability is an online operation and doesn't impact your application connectivity and operations.
21
21
22
-
## Pre-requisites
22
+
## Prerequisites
23
23
24
24
> [!IMPORTANT]
25
25
> For the list of regions that support Zone redundant high availability, please review the supported regions [here](./overview.md#azure-regions).
@@ -28,27 +28,27 @@ This page provides guidelines how you can enable or disable high availability. T
28
28
29
29
This section provides details specifically for HA-related fields. You can follow these steps to deploy high availability while creating your Azure Database for PostgreSQL flexible server instance.
30
30
31
-
1. In the [Azure portal](https://portal.azure.com/), choose Azure Database for PostgreSQL flexible server and click create. For details on how to fill details such as **Subscription**, **Resource group**, **server name**, **region**, and other fields, see how-to documentation for the server creation.
31
+
1. In the [Azure portal](https://portal.azure.com/), choose Azure Database for PostgreSQL flexible server and select create. For details on how to fill details such as **Subscription**, **Resource group**, **server name**, **region**, and other fields, see how-to documentation for the server creation.
32
32
33
33
:::image type="content" source="./media/how-to-manage-high-availability-portal/subscription-region.png" alt-text="Screenshot of subscription and region selection.":::
34
34
35
-
2. Choose your **availability zone**. This is useful if you want to collocate your application in the same availability zone as the database to reduce latency. Choose **No Preference** if you want the Azure Database for PostgreSQL flexible server instance to deploy the primary server on any availability zone. Note that only if you choose the availability zone for the primary in a zone-redundant HA deployment, you will be allowed to choose the standby availability zone.
35
+
2. Choose your **availability zone**. This is useful if you want to collocate your application in the same availability zone as the database to reduce latency. Choose **No Preference** if you want the Azure Database for PostgreSQL flexible server instance to deploy the primary server on any availability zone. Note that only if you choose the availability zone for the primary in a zone-redundant HA deployment are you allowed to choose the standby availability zone.
36
36
37
37
:::image type="content" source="./media/how-to-manage-high-availability-portal/zone-selection.png" alt-text="Screenshot of availability zone selection.":::
38
38
39
-
3.Click the checkbox for **Enable high availability**. That will open up an option to choose high availability mode. If the region does not support AZs, then only same-zone mode is enabled.
39
+
3.Select the checkbox for **Enable high availability**. That opens up an option to choose high availability mode. If the region doesn't support AZs, then only same-zone mode is enabled.
40
40
41
41
:::image type="content" source="./media/how-to-manage-high-availability-portal/choose-high-availability-deployment-model.png" alt-text="High availability checkbox and mode selection.":::
42
42
43
43
4. If you chose the Availability zone in step 2 and if you chose zone-redundant HA, then you can choose the standby zone.
44
44
:::image type="content" source="./media/how-to-manage-high-availability-portal/choose-standby-availability-zone.png" alt-text="Screenshot of Standby AZ selection.":::
45
45
46
46
47
-
5. If you want to change the default compute and storage, click**Configure server**.
47
+
5. If you want to change the default compute and storage, select**Configure server**.
48
48
49
49
:::image type="content" source="./media/how-to-manage-high-availability-portal/configure-server.png" alt-text="Screenshot of configure compute and storage screen.":::
50
50
51
-
6. If high availability option is checked, the burstable tier will not be available to choose. You can choose either
51
+
6. If high availability option is checked, the burstable tier isn't available to choose. You can choose either
52
52
**General purpose** or **Memory Optimized** compute tiers. Then you can select **compute size** for your choice from the dropdown.
3.Click on the **Enable high availability** checkbox to **enable** the option. It shows same zone HA and zone-redundant HA option. If you choose zone-redundant HA, you can choose the standby AZ.
73
+
3.Select the **Enable high availability** checkbox to **enable** the option. It shows same zone HA and zone-redundant HA option. If you choose zone-redundant HA, you can choose the standby AZ.
74
74
75
75
:::image type="content" source="./media/how-to-manage-high-availability-portal/enable-same-zone-high-availability-blade.png" alt-text="Screenshot to enable same zone high availability.":::
76
76
77
77
:::image type="content" source="./media/how-to-manage-high-availability-portal/enable-zone-redundant-high-availability-blade.png" alt-text="Screenshot to enable zone redundant high availability.":::
78
78
79
-
4. A confirmation dialog will show that states that by enabling high availability, your cost will increase due to additional server and storage deployment.
79
+
4. A confirmation dialog appears stating that by enabling high availability, your costs increase due to more server and storage deployment.
80
80
81
-
5.Click**Enable HA** button to enable the high availability.
81
+
5.Select**Enable HA** button to enable the high availability.
82
82
83
-
6. A notification will show up stating the high availability deployment is in progress.
83
+
6. A notification appears stating the high availability deployment is in progress.
84
84
85
85
## Disable high availability
86
86
87
87
Follow these steps to disable high availability for your Azure Database for PostgreSQL flexible server instance that is already configured with high availability.
88
88
89
89
1. In the [Azure portal](https://portal.azure.com/), select your existing Azure Database for PostgreSQL flexible server instance.
90
90
91
-
2. On the Azure Database for PostgreSQL flexible server instance page, click**High Availability** from the front panel to open high availability page.
91
+
2. On the Azure Database for PostgreSQL flexible server instance page, select**High Availability** from the front panel to open high availability page.
3.Click on the **High availability** checkbox to **disable** the option. Then click**Save** to save the change.
95
+
3.Select on the **High availability** checkbox to **disable** the option. Then select**Save** to save the change.
96
96
97
97
:::image type="content" source="./media/how-to-manage-high-availability-portal/disable-high-availability.png" alt-text="Screenshot showing disable high availability.":::
98
98
99
-
4. A confirmation dialog will be shown where you can confirm disabling high availability.
99
+
4. A confirmation dialog is shown where you can confirm disabling high availability.
100
100
101
-
5.Click**Disable HA** button to disable the high availability.
101
+
5.Select**Disable HA** button to disable the high availability.
102
102
103
-
6. A notification will show up decommissioning of the high availability deployment is in progress.
103
+
6. A notification appears stating that decommissioning of the high availability deployment is in progress.
104
104
105
105
## Forced failover
106
106
107
-
Follow these steps to force failover your primary to the standby Azure Database for PostgreSQL flexible server instance. This will immediately bring the primary down and triggers a failover to the standby server. This is useful for cases like testing the unplanned outage failover time for your workload.
107
+
Follow these steps to force failover your primary to the standby Azure Database for PostgreSQL flexible server instance. This immediately brings the primary down and triggers a failover to the standby server. This is useful for cases like testing the unplanned outage failover time for your workload.
108
108
109
109
1. In the [Azure portal](https://portal.azure.com/), select your existing Azure Database for PostgreSQL flexible server instance that has high availability feature already enabled.
110
-
2. On the Azure Database for PostgreSQL flexible server instance page, click High Availability from the front panel to open high availability page.
110
+
2. On the Azure Database for PostgreSQL flexible server instance page, select High Availability from the front panel to open high availability page.
111
111
3. Check the Primary availability zone and the Standby availability zone
112
-
4. Click on Forced Failover to initiate the manual failover procedure. A pop up will inform you on the potential downtime until the failover is complete. Read the message and click Ok.
113
-
5. A notification will show up mentioning that failover is in progress.
114
-
6. Once failover to the standby server is complete, a notification will pop up.
112
+
4. Select on Forced Failover to initiate the manual failover procedure. A pop up informs you on the potential downtime until the failover is complete. Read the message and select Ok.
113
+
5. A notification appears mentioning that failover is in progress.
114
+
6. Once failover to the standby server is complete, a notification pops up.
115
115
7. Check the new Primary availability zone and the Standby availability zone.
@@ -125,11 +125,11 @@ Follow these steps to force failover your primary to the standby Azure Database
125
125
126
126
Follow these steps to perform a planned failover from your primary to the standby Azure Database for PostgreSQL flexible server instance. This will first prepare the standby server and performs the failover. This provides the least downtime as this performs a graceful failover to the standby server for situations like after a failover event, you want to bring the primary back to the preferred availability zone.
127
127
1. In the [Azure portal](https://portal.azure.com/), select your existing Azure Database for PostgreSQL flexible server instance that has high availability feature already enabled.
128
-
2. On the Azure Database for PostgreSQL flexible server instance page, click High Availability from the front panel to open high availability page.
128
+
2. On the Azure Database for PostgreSQL flexible server instance page, select High Availability from the front panel to open high availability page.
129
129
3. Check the Primary availability zone and the Standby availability zone
130
-
4. Click on Planned Failover to initiate the manual failover procedure. A pop up will inform you the process. Read the message and click Ok.
131
-
5. A notification will show up mentioning that failover is in progress.
132
-
6. Once failover to the standby server is complete, a notification will pop up.
130
+
4. Select on Planned Failover to initiate the manual failover procedure. A pop up informs you about the process. Read the message and select Ok.
131
+
5. A notification appears mentioning that failover is in progress.
132
+
6. Once failover to the standby server is complete, a notification pops up.
133
133
7. Check the new Primary availability zone and the Standby availability zone.
134
134
:::image type="content" source="./media/how-to-manage-high-availability-portal/ha-planned-failover.png" alt-text="Screenshot of On-demand planned failover.":::
135
135
@@ -143,11 +143,11 @@ Follow these steps to perform a planned failover from your primary to the standb
143
143
144
144
## Enabling Zone redundant HA after the region supports AZ
145
145
146
-
There are Azure regions that do not support availability zones. If you have already deployed non-HA servers, you cannot directly enable zone redundant HA on the server, but you can perform restore and enable HA in that server. Following steps shows how to enable Zone redundant HA for that server.
146
+
There are Azure regions that don't support availability zones. If you already deployed non-HA servers, you can't directly enable zone redundant HA on the server, but you can perform restore and enable HA in that server. The following steps shows how to enable Zone redundant HA for that server.
147
147
148
-
1. From the overview page of the server, click**Restore** to [perform a PITR](how-to-restore-server-portal.md#restore-to-the-latest-restore-point). Choose **Latest restore point**.
148
+
1. From the overview page of the server, select**Restore** to [perform a PITR](how-to-restore-server-portal.md#restore-to-the-latest-restore-point). Choose **Latest restore point**.
149
149
2. Choose a server name, availability zone.
150
-
3.Click**Review+Create**".
150
+
3.Select**Review+Create**".
151
151
4. A new Azure Database for PostgreSQL flexible server instance is created from the backup.
152
152
5. Once the new server is created, from the overview page of the server, follow the [guide](#enable-high-availability-post-server-creation) to enable HA.
153
153
6. After data verification, you can optionally [delete](how-to-manage-server-portal.md#delete-a-server) the old server.
## Connect to the Azure Database for PostgreSQL flexible server database using psql
97
98
98
99
There are a number of applications you can use to connect to your Azure Database for PostgreSQL flexible server instance. If your client computer has PostgreSQL installed, you can use a local instance of [psql](https://www.postgresql.org/docs/current/static/app-psql.html) to connect to an Azure Database for PostgreSQL flexible server instance. Let's now use the psql command-line utility to connect to the Azure Database for PostgreSQL flexible server instance.
0 commit comments