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
+4-2Lines changed: 4 additions & 2 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).
Copy file name to clipboardExpand all lines: articles/postgresql/flexible-server/how-to-restore-server-portal.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,7 +62,7 @@ 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
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.
0 commit comments