Updates to restore PostgreSQL flex doc

Author: PriskeyJeronika

articles/backup/media/restore-azure-database-postgresql-flex/restore.png

@@ -2,7 +2,7 @@
 title: Restore Azure PostgreSQL-Flexible server as Files using Azure portal
 description: Learn about how to restore Azure PostgreSQL-Flexible server as Files.
 ms.topic: how-to
-ms.date: 04/30/2025
+ms.date: 05/06/2025
 ms.service: azure-backup
 ms.custom:
   - ignite-2024
@@ -24,10 +24,12 @@ Before you restore from Azure Database for PostgreSQL Flexible server backups, r
 
 - Ensure the target storage account for restoring backup as a file is accessible via a public network. If the storage account uses a private endpoint, [update its public network access settings](backup-azure-database-postgresql-flex-manage.md#enable-public-network-access-for-the-database-storage-account) before executing a restore operation.
 
-## Restore Azure PostgreSQL-Flexible database
+## Restore Azure PostgreSQL - Flexible server backups as files
 
 >[!Note]
->The restore operation transfers all PostgreSQL – flexible server databases to a designated storage account container. After restoration, move the files to a new or existing PostgreSQL – Flexible server.
+>Restore operation is a two step process: 
+>1. Restore the backup from Backup vault to a storage container.  
+>2. Restore the backup files from storage container to a new or existing flexible server. 
 
 To restore Azure PostgreSQL-Flexible database, Follow these steps:
 
@@ -50,13 +52,11 @@ To restore Azure PostgreSQL-Flexible database, Follow these steps:
    :::image type="content" source="./media/restore-azure-database-postgresql-flex/review.png" alt-text="Screenshot showing the review process page."::: 
 
 1. Submit the Restore operation and track the triggered job under **Backup jobs**.
-   :::image type="content" source="./media/restore-azure-database-postgresql-flex/validate.png" alt-text="Screenshot showing the validate process page.":::
-
 
 After the restore job is completed successfully, go to the storage account container to view the restored databases as files (`.sql` files) from your PostgreSQL – Flexible server. Azure Backup also generates the following backup files:
 
 - `Database.sql file` per database: Contains data and schema information for a particular database.  
-- `Roles.sql files` for entire instance: Contains all  role information ((azure_su(superuser) azure_pg_admin, replication, local admin, Microsoft Entra admins and any other custom roles on the server)) that exists at server level.
+- `Roles.sql files` for entire instance: Contains all role information that exists at server level.
 - `Tablespace.sql file`: Tablespace file.
 - `Schema.sql file`: Contains schema information for all the databases on the server.
 
@@ -121,7 +121,24 @@ Here are the key considerations:
 Before you restore the database objects, ensure that you properly dump and clean up the roles. To perform this action, download the `roles.sql`script from your storage container and create all required logins. 
 - **Create Non-Entra Roles**: Use a local admin account to run the role creation scripts. 
 - **Create Microsoft Entra Roles**: If you need to create roles for Microsoft Entra users, use a Microsoft Entra administrator account to run the necessary scripts. 
+
+You can download the roles script from your storage account as shown in the following screenshot:
+
+:::image type="content" source="./media/restore-azure-database-postgresql-flex/containers.png" alt-text="Screenshot showing the containers page.":::
+
+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:
+
+- **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.
+- **Excluding service-specific users**: Exclude Single server service users, such as `azure_superuser` or `azure_pg_admin`. These are specific to the service and are created automatically in the new environment.
+
+Use the following sed command to clean up your roles dump:
+
+```
+sed -i '/azure_superuser/d; /azure_pg_admin/d; /azuresu/d; /^CREATE ROLE replication/d; /^ALTER ROLE replication/d; /^ALTER ROLE/ {s/NOSUPERUSER//; s/NOBYPASSRLS//;}' roles.sql
+```
+
+This command deletes the lines containing `azure_superuser`, `azure_pg_admin`, `azuresu`, lines starting with *CREATE ROLE* replication and *ALTER ROLE* replication, and removes the *NOSUPERUSER* and *NOBYPASSRLS* attributes from *ALTER ROLE* statements.
 
- ## Next steps
+## Next steps
 
 [Manage backup of Azure PostgreSQL - Flexible Server using Azure portal](backup-azure-database-postgresql-flex-manage.md).