Skip to content

Commit 1c4e2b8

Browse files
removed images
1 parent 417dd6e commit 1c4e2b8

File tree

1 file changed

+1
-11
lines changed

1 file changed

+1
-11
lines changed

articles/backup/restore-azure-database-postgresql-flex.md

Lines changed: 1 addition & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Restore Azure PostgreSQL-Flexible server as Files using Azure portal
33
description: Learn about how to restore Azure PostgreSQL-Flexible server as Files.
44
ms.topic: how-to
5-
ms.date: 05/06/2025
5+
ms.date: 05/12/2025
66
ms.service: azure-backup
77
ms.custom:
88
- ignite-2024
@@ -35,21 +35,15 @@ To restore Azure PostgreSQL-Flexible database, Follow these steps:
3535

3636
1. Go to **Backup vault** > **Backup Instances**. Select the PostgreSQL - Flexible server to be restored and select **Restore**.
3737

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-
4038
Alternatively, go to [Backup center](./backup-center-overview.md) and select **Restore**.
4139

4240
1. Select the point in time you would like to restore by using **Select restore point**. Change the date range by selecting **Time period**.
4341

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-
4642
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.
4743

4844
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":::
5045

5146
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":::
5347

5448
1. Submit the Restore operation and track the triggered job under **Backup jobs**.
5549

@@ -63,8 +57,6 @@ After the restore job is completed successfully, go to the storage account conta
6357
>[!Note]
6458
>We recommend you not to run this script on the PostgreSQL - Flexible server because the schema is already part of the `database.sql` script.
6559
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-
6860
## Restore the backup files from storage container to a new or existing PostgreSQL – Flexible server
6961

7062
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
124116

125117
You can download the roles script from your storage account as shown in the following screenshot:
126118

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-
129119
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:
130120

131121
- **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

Comments
 (0)