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/backup/restore-azure-database-postgresql-flex.md
+1-11Lines changed: 1 addition & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Restore Azure PostgreSQL-Flexible server as Files using Azure portal
3
3
description: Learn about how to restore Azure PostgreSQL-Flexible server as Files.
4
4
ms.topic: how-to
5
-
ms.date: 05/06/2025
5
+
ms.date: 05/12/2025
6
6
ms.service: azure-backup
7
7
ms.custom:
8
8
- ignite-2024
@@ -35,21 +35,15 @@ To restore Azure PostgreSQL-Flexible database, Follow these steps:
35
35
36
36
1. Go to **Backup vault** > **Backup Instances**. Select the PostgreSQL - Flexible server to be restored and select **Restore**.
37
37
38
-
:::image type="content" source="./media/restore-azure-database-postgresql-flex/restore-inline.png" alt-text="Screenshot showing how to restore a database." lightbox="./media/restore-azure-database-postgresql-flex/restore-expanded.png":::
39
-
40
38
Alternatively, go to [Backup center](./backup-center-overview.md) and select **Restore**.
41
39
42
40
1. Select the point in time you would like to restore by using **Select restore point**. Change the date range by selecting **Time period**.
43
41
44
-
:::image type="content" source="./media/restore-azure-database-postgresql/select-restore-point-inline.png" alt-text="Screenshot showing the process to select a recovery point." lightbox="./media/restore-azure-database-postgresql-flex/select-restore-point-expanded.png":::
45
-
46
42
1. Choose the target storage account and container in **Restore parameters** tab. Select **Validate** to check the restore parameters permissions before the final review and restore.
47
43
48
44
1. Once the validation is successful, select **Review + restore**.
49
-
:::image type="content" source="./media/restore-azure-database-postgresql-flex/review-restore-inline.png" alt-text="Screenshot showing the restore parameter process." lightbox="./media/restore-azure-database-postgresql-flex/review-restore-expanded.png":::
50
45
51
46
1. After final review of the parameters, select **Restore** to restore the selected PostgreSQL - Flexible server backup in target storage account.
52
-
:::image type="content" source="./media/restore-azure-database-postgresql-flex/review-inline.png" alt-text="Screenshot showing the review process page." lightbox="./media/restore-azure-database-postgresql-flex/review-expanded.png":::
53
47
54
48
1. Submit the Restore operation and track the triggered job under **Backup jobs**.
55
49
@@ -63,8 +57,6 @@ After the restore job is completed successfully, go to the storage account conta
63
57
>[!Note]
64
58
>We recommend you not to run this script on the PostgreSQL - Flexible server because the schema is already part of the `database.sql` script.
65
59
66
-
:::image type="content" source="./media/restore-azure-database-postgresql-flex/database-files.png" alt-text="Screenshot shows the database schema per database." lightbox="./media/restore-azure-database-postgresql-flex/database-files.png":::
67
-
68
60
## Restore the backup files from storage container to a new or existing PostgreSQL – Flexible server
69
61
70
62
To restore the backup files from storage container to a new or existing PostgreSQL – Flexible server, follow these steps:
@@ -124,8 +116,6 @@ Before you restore the database objects, ensure that you properly dump and clean
124
116
125
117
You can download the roles script from your storage account as shown in the following screenshot:
126
118
127
-
:::image type="content" source="./media/restore-azure-database-postgresql-flex/containers-inline.png" alt-text="Screenshot showing the containers page." lightbox="./media/restore-azure-database-postgresql-flex/containers-expanded.png":::
128
-
129
119
When you migrate the output file, `roles.sql` might include certain roles and attributes that aren't applicable in the new environment. You must consider the following:
130
120
131
121
-**Removing attributes that can be set only by superusers**: If you migrate to an environment where you don't have superuser privileges, remove attributes such as *NOSUPERUSER* and *NOBYPASSRLS* from the roles dump.
0 commit comments