Skip to content

Commit 7216401

Browse files
committed
fix and acrolinx
1 parent 59cab3f commit 7216401

File tree

2 files changed

+32
-31
lines changed

2 files changed

+32
-31
lines changed

articles/postgresql/flexible-server/how-to-manage-high-availability-portal.md

Lines changed: 31 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -15,11 +15,11 @@ ms.date: 06/23/2022
1515

1616
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.
1717

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

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

22-
## Pre-requisites
22+
## Prerequisites
2323

2424
> [!IMPORTANT]
2525
> 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
2828

2929
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.
3030

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

3333
:::image type="content" source="./media/how-to-manage-high-availability-portal/subscription-region.png" alt-text="Screenshot of subscription and region selection.":::
3434

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

3737
:::image type="content" source="./media/how-to-manage-high-availability-portal/zone-selection.png" alt-text="Screenshot of availability zone selection.":::
3838

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

4141
:::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.":::
4242

4343
4. If you chose the Availability zone in step 2 and if you chose zone-redundant HA, then you can choose the standby zone.
4444
:::image type="content" source="./media/how-to-manage-high-availability-portal/choose-standby-availability-zone.png" alt-text="Screenshot of Standby AZ selection.":::
4545

4646

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

4949
:::image type="content" source="./media/how-to-manage-high-availability-portal/configure-server.png" alt-text="Screenshot of configure compute and storage screen.":::
5050

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
5252
**General purpose** or **Memory Optimized** compute tiers. Then you can select **compute size** for your choice from the dropdown.
5353

5454
:::image type="content" source="./media/how-to-manage-high-availability-portal/select-compute.png" alt-text="Compute tier selection screen.":::
@@ -58,60 +58,60 @@ This section provides details specifically for HA-related fields. You can follow
5858

5959
:::image type="content" source="./media/how-to-manage-high-availability-portal/storage-backup.png" alt-text="Screenshot of Storage Backup.":::
6060

61-
8. Click **Save**.
61+
8. Select **Save**.
6262

6363
## Enable high availability post server creation
6464

6565
Follow these steps to enable high availability for your existing Azure Database for PostgreSQL flexible server instance.
6666

6767
1. In the [Azure portal](https://portal.azure.com/), select your existing Azure Database for PostgreSQL flexible server instance.
6868

69-
2. On the Azure Database for PostgreSQL flexible server instance page, click **High Availability** from the left panel to open high availability page.
69+
2. On the Azure Database for PostgreSQL flexible server instance page, select **High Availability** from the left panel to open high availability page.
7070

7171
:::image type="content" source="./media/how-to-manage-high-availability-portal/high-availability-left-panel.png" alt-text="Left panel selection screen.":::
7272

73-
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.
7474

7575
:::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.":::
7676

7777
:::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.":::
7878

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

81-
5. Click **Enable HA** button to enable the high availability.
81+
5. Select **Enable HA** button to enable the high availability.
8282

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

8585
## Disable high availability
8686

8787
Follow these steps to disable high availability for your Azure Database for PostgreSQL flexible server instance that is already configured with high availability.
8888

8989
1. In the [Azure portal](https://portal.azure.com/), select your existing Azure Database for PostgreSQL flexible server instance.
9090

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

9393
:::image type="content" source="./media/how-to-manage-high-availability-portal/high-availability-left-panel.png" alt-text="Left panel selection screenshot.":::
9494

95-
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.
9696

9797
:::image type="content" source="./media/how-to-manage-high-availability-portal/disable-high-availability.png" alt-text="Screenshot showing disable high availability.":::
9898

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

101-
5. Click **Disable HA** button to disable the high availability.
101+
5. Select **Disable HA** button to disable the high availability.
102102

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

105105
## Forced failover
106106

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

109109
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.
111111
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.
115115
7. Check the new Primary availability zone and the Standby availability zone.
116116

117117
:::image type="content" source="./media/how-to-manage-high-availability-portal/ha-forced-failover.png" alt-text="On-demand forced failover option screenshot.":::
@@ -125,11 +125,11 @@ Follow these steps to force failover your primary to the standby Azure Database
125125

126126
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.
127127
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.
129129
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.
133133
7. Check the new Primary availability zone and the Standby availability zone.
134134
:::image type="content" source="./media/how-to-manage-high-availability-portal/ha-planned-failover.png" alt-text="Screenshot of On-demand planned failover.":::
135135

@@ -143,11 +143,11 @@ Follow these steps to perform a planned failover from your primary to the standb
143143
144144
## Enabling Zone redundant HA after the region supports AZ
145145

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

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**.
149149
2. Choose a server name, availability zone.
150-
3. Click **Review+Create**".
150+
3. Select **Review+Create**".
151151
4. A new Azure Database for PostgreSQL flexible server instance is created from the backup.
152152
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.
153153
6. After data verification, you can optionally [delete](how-to-manage-server-portal.md#delete-a-server) the old server.

articles/postgresql/flexible-server/quickstart-create-server-portal.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -93,6 +93,7 @@ Open your server's **Overview** page. Make a note of the **Server name** and the
9393

9494
:::image type="content" source="./media/quickstart-create-database-portal/8-server-name.png" alt-text="The server Overview page.":::
9595

96+
<a name="connect-to-the-postgresql-database-using-psql"></a>
9697
## Connect to the Azure Database for PostgreSQL flexible server database using psql
9798

9899
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

Comments
 (0)