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/concepts-backup-restore.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,7 +47,7 @@ Flexible Server offers three options:
47
47
48
48
By default, backup storage for servers with same-zone high availability (HA) or no high-availability configuration is set to locally redundant.
49
49
50
-
-**Geo-redundant backup storage (preview)**: You can choose this option at the time of server creation. When the backups are stored in geo-redundant backup storage, in addition to three copies of data stored within the region where your server is hosted, the data is replicated to a geo-paired region.
50
+
-**Geo-redundant backup storage**: You can choose this option at the time of server creation. When the backups are stored in geo-redundant backup storage, in addition to three copies of data stored within the region where your server is hosted, the data is replicated to a geo-paired region.
51
51
52
52
This option provides the ability to restore your server in a different region in the event of a disaster. It also provides at least 99.99999999999999 percent (16 nines) durability of backup objects over a year.
53
53
@@ -103,6 +103,8 @@ With continuous backup of transaction logs, you'll be able to restore to the las
103
103
104
104
-**Custom restore point**: This option allows you to choose any point in time within the retention period defined for this flexible server. By default, the latest time in UTC is automatically selected. Automatic selection is useful if you want to restore to the last committed transaction for test purposes. You can optionally choose other days and times.
105
105
106
+
-**Fast restore point**: This option allows users to restore the server in the fastest time possible within the retention period defined for their flexible server. Fastest restore is possible by directly choosing the timestamp from the list of backups. This restore operation provisions a server and simply restores the full snapshot backup and doesn't require any recovery of logs which makes it fast. We recommend you select a backup timestamp which is greater than the earliest restore point in time for a successful restore operation.
107
+
106
108
For latest and custom restore point options, the estimated time to recover depends on several factors, including the volume of transaction logs to process after the previous backup time, and the total number of databases recovering in the same region at the same time. The overall recovery time usually takes from few minutes up to a few hours.
107
109
108
110
If you've configured your server within a virtual network, you can restore to the same virtual network or to a different virtual network. However, you can't restore to public access. Similarly, if you configured your server with public access, you can't restore to private virtual network access.
@@ -113,7 +115,7 @@ If you've configured your server within a virtual network, you can restore to th
113
115
>If you accidentally deleted your server, please reach out to support. In some cases, your server might be restored with or without data loss.
114
116
115
117
116
-
## Geo-redundant backup and restore (preview)
118
+
## Geo-redundant backup and restore
117
119
118
120
To enable geo-redundant backup from the **Compute + storage** pane in the Azure portal, see the [quickstart guide](./quickstart-create-server-portal.md).
119
121
@@ -130,7 +132,7 @@ The estimated time to recover the server (recovery time objective, or RTO) depen
130
132
131
133
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.
132
134
133
-
For more information about performing a geo-restore, see the [how-to guide](how-to-restore-server-portal.md#performing-geo-restore-preview).
135
+
For more information about performing a geo-restore, see the [how-to guide](how-to-restore-server-portal.md#performing-geo-restore).
134
136
135
137
> [!IMPORTANT]
136
138
> 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.
This article provides step-by-step procedure to perform point-in-time recoveries in flexible server using backups.
18
18
19
19
## Prerequisites
20
20
- If you don't have an Azure subscription, create a [free](https://azure.microsoft.com/free/) account before you begin.
21
21
- Install or upgrade Azure CLI to the latest version. See [Install Azure CLI](/cli/azure/install-azure-cli).
22
-
-Login to Azure account using [az login](/cli/azure/reference-index#az-login) command. Note the **id** property, which refers to **Subscription ID** for your Azure account.
22
+
-Log in to Azure account using [az login](/cli/azure/reference-index#az-login) command. Note the **id** property, which refers to **Subscription ID** for your Azure account.
23
23
24
24
```azurecli-interactive
25
25
az login
@@ -31,7 +31,7 @@ This article provides step-by-step procedure to perform point-in-time recoveries
31
31
az account set --subscription <subscription id>
32
32
```
33
33
34
-
- Create a PostgreQL Flexible Server if you have not already created one using the ```az postgres flexible-server create``` command.
34
+
- Create a PostgreQL Flexible Server if you haven't already created one using the ```az postgres flexible-server create``` command.
35
35
36
36
```azurecli
37
37
az postgres flexible-server create --resource-group myresourcegroup --name myservername
@@ -70,7 +70,7 @@ Time taken to restore will depend on the size of the data stored in the server.
70
70
After the restore is completed, you should perform the following tasks to get your users and applications back up and running:
71
71
72
72
- If the new server is meant to replace the original server, redirect clients and client applications to the new server
73
-
- Ensure appropriate VNet rules are in place for users to connect. These rules are not copied over from the original server.
73
+
- Ensure appropriate VNet rules are in place for users to connect. These rules aren't copied over from the original server.
74
74
- Ensure appropriate logins and database level permissions are in place
75
75
- Configure alerts as appropriate for the newly restore server
This article provides step-by-step procedure to perform point-in-time recoveries in flexible server using backups. You can perform either to a latest restore point or a custom restore point within your retention period.
17
17
@@ -62,9 +62,9 @@ Follow these steps to restore your flexible server using an existing backup.
62
62
63
63
7. A notification will be shown that the restore operation has been initiated.
64
64
65
-
## Performing Geo-Restore (Preview)
65
+
## Performing Geo-Restore
66
66
67
-
If your source server is configured with geo-redundant backup, you can restore the servers in a paired region. Please note that, for the first time restore, please wait at least 1 hour after the source server is created.
67
+
If your source server is configured with geo-redundant backup, you can restore the servers in a paired region. Note that, for the first time restore, please wait at least 1 hour after the source server is created.
68
68
69
69
1. In the [Azure portal](https://portal.azure.com/), choose your flexible server that you want to geo-restore the backup from.
Copy file name to clipboardExpand all lines: articles/postgresql/flexible-server/release-notes.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ This page provides latest news and updates regarding feature additions, engine v
25
25
26
26
## Release: July 2022
27
27
28
-
* Support for [Geo-redundant backup](./concepts-backup-restore.md#geo-redundant-backup-and-restore-preview) in [additional regions](./overview.md#azure-regions) - Australia East, Australia Southeast, Canada Central, Canada East, UK South, UK West, East US, West US, East Asia, Southeast Asia, North Central US, South Central US, and France Central.
28
+
* Support for [Geo-redundant backup](./concepts-backup-restore.md#geo-redundant-backup-and-restore) in [more regions](./overview.md#azure-regions) - Australia East, Australia Southeast, Canada Central, Canada East, UK South, UK West, East US, West US, East Asia, Southeast Asia, North Central US, South Central US, and France Central.
29
29
30
30
## Release: June 2022
31
31
@@ -84,7 +84,7 @@ This page provides latest news and updates regarding feature additions, engine v
84
84
* Support for [Terraform](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/postgresql_flexible_server).
85
85
* Support for [new regions](overview.md#azure-regions) Central India and Japan West.
86
86
* Support for non-SSL mode of connectivity using a new `require_secure_transport` server parameter.
87
-
* Support for `log_line_prefix` server parameter which adds the string at the beginning of each log line.
87
+
* Support for `log_line_prefix` server parameter, which adds the string at the beginning of each log line.
88
88
* Support for [Azure Resource Health](../../service-health/resource-health-overview.md) for Flexible server health diagnosis and to get support.
89
89
* Several bug fixes, stability, and performance improvements.
90
90
@@ -148,7 +148,7 @@ In addition, consider the following points of contact as appropriate:
148
148
149
149
Will Flexible Server replace Single Server or Will Single Server be retired soon?
150
150
151
-
We continue to support Single Server and encourage you to adopt Flexible Server which has richer capabilities such as zone resilient HA, predictable performance, maximum control, custom maintenance window, cost optimization controls and simplified developer experience suitable for your enterprise workloads. If we decide to retire any service, feature, API or SKU, you will receive advance notice including a migration or transition path. Learn more about Microsoft Lifecycle policies [here](/lifecycle/faq/general-lifecycle).
151
+
We continue to support Single Server and encourage you to adopt Flexible Server, which has richer capabilities such as zone resilient HA, predictable performance, maximum control, custom maintenance window, cost optimization controls and simplified developer experience suitable for your enterprise workloads. If we decide to retire any service, feature, API or SKU, you will receive advance notice including a migration or transition path. Learn more about Microsoft Lifecycle policies [here](/lifecycle/faq/general-lifecycle).
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments