Skip to content

Commit fe43f3e

Browse files
committed
edit pass: how-to-restore-server-portal
1 parent f4738b8 commit fe43f3e

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

articles/postgresql/flexible-server/concepts-backup-restore.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -132,7 +132,7 @@ The estimated time to recover the server (recovery time objective, or RTO) depen
132132

133133
During the geo-restore, the server configurations that can be changed include virtual network settings and the ability to remove geo-redundant backup from the restored server. Changing other server configurations--such as compute, storage, or pricing tier (Burstable, General Purpose, or Memory Optimized)--during geo-restore is not supported.
134134

135-
For more information about performing a geo-restore, see the [how-to guide](how-to-restore-server-portal.md#performing-geo-restore).
135+
For more information about performing a geo-restore, see the [how-to guide](how-to-restore-server-portal.md#perform-geo-restore).
136136

137137
> [!IMPORTANT]
138138
> When the primary region is down, you can't create geo-redundant servers in the respective geo-paired region, because storage can't be provisioned in the primary region. Before you can provision geo-redundant servers in the geo-paired region, you must wait for the primary region to be up.

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -145,7 +145,7 @@ Follow these steps to perform a planned failover from your primary to the standb
145145

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

148-
1. From the overview page of the server, click **Restore** to [perform a PITR](how-to-restore-server-portal.md#restoring-to-the-latest-restore-point). Choose **Latest restore point**.
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**.
149149
2. Choose a server name, availability zone.
150150
3. Click **Review+Create**".
151151
4. A new Flexible server will be created from the backup.

articles/postgresql/flexible-server/how-to-restore-server-portal.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@ If your source server is configured with geo-redundant backup, you can restore t
9696

9797
By default, the backups for the restored server are configured with geo-redundant backup. If you don't want geo-redundant backup, you can select **Configure Server** and then clear the **Restore to paired region** checkbox.
9898

99-
If the source server is configured with *private access*, you can restore only to another virtual network in the remote region. You can either choose an existing virtual network or create a new virtual network and restore your server into that.
99+
If the source server is configured with *private access*, you can restore only to another virtual network in the remote region. You can either choose an existing virtual network or create a new virtual network and restore your server into that network.
100100

101101
## Next steps
102102

0 commit comments

Comments
 (0)