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
[Troubleshoot common errors for backup and restore operations for Azure Database for PostgreSQL - Flexible Server](backup-azure-database-postgresql-flex-troubleshoot.md).
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-database-postgresql-flex-overview.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,15 +2,15 @@
2
2
title: About Azure Database for PostgreSQL Flexible server backup
3
3
description: An overview on Azure Database for PostgreSQL Flexible server backup
4
4
ms.topic: overview
5
-
ms.date: 09/09/2024
5
+
ms.date: 02/28/2025
6
6
ms.service: azure-backup
7
7
ms.custom:
8
8
- ignite-2024
9
9
author: jyothisuri
10
10
ms.author: jsuri
11
11
---
12
12
13
-
# About Azure Database for PostgreSQL - Flexible server backup (preview)
13
+
# About Azure Database for PostgreSQL - Flexible Server backup
14
14
15
15
Azure Backup and Azure Database Services have come together to build an enterprise-class backup solution for Azure Database for PostgreSQL servers that retains backups for up to 10 years. The feature offers the following capabilities:
16
16
@@ -27,7 +27,7 @@ To perform the backup operation:
27
27
1. Grant permissions to the backup vault MSI on the target ARM resource (PostgreSQL-Flexible server), establishing access, and control.
28
28
1. Configure backup policies, specify scheduling, retention, and other parameters.
29
29
30
-
Once the configuration is complete:
30
+
Once the configuration is successful:
31
31
32
32
1. The Backup service invokes the backup based on the policy schedules on the ARM API of PostgresFlex server, writing data to a secure blob-container with a SAS for enhanced security.
33
33
1. Backup runs independently preventing disruptions during long-running tasks.
@@ -59,4 +59,4 @@ You incur charges for:
59
59
60
60
## Next steps
61
61
62
-
[Azure Database for PostgreSQL -Flex backup](backup-azure-database-postgresql-flex.md).
62
+
[Back up Azure Database for PostgreSQL - Flexible Server using Azure portal](tutorial-create-first-backup-azure-database-postgresql-flex.md).
# Restore Azure Database for PostgreSQL - flexible server using Azure PowerShell (preview)
12
+
# Restore Azure Database for PostgreSQL - Flexible Server using Azure PowerShell
13
13
14
-
This article explains how to restore **Azure Database for PostgreSQL - flexible server** to an Azure Database for PostgreSQL - flexible server backed-up by Azure Backup.
14
+
This article describes how to restore Azure Database for PostgreSQL - Flexible Server using Azure PowerShell.
15
15
16
-
In this article, you'll learn how to:
16
+
>[!Note]
17
+
>The Original Location Recovery (OLR) option isn't supported for PaaS databases. Instead, use the Alternate-Location Recovery (ALR) to restore from a recovery point and create a new database in the same or another Azure PostgreSQL – Flexible server, keeping both the source and restored databases.
17
18
18
-
- Restore to create a new PostgreSQL - flexible server
19
-
20
-
- Track the restore operation status
21
-
22
-
We'll refer to an existing backup vault _TestBkpVault_ under the resource group _testBkpVaultRG_ in the examples.
19
+
Let's use an existing Backup vault `TestBkpVault`, under the resource group `testBkpVaultRG` in the examples.
Backup vault uses managed identity to access other Azure resources. To restore from backup, Backup vault’s managed identity requires a set of permissions on the Azure PostgreSQL – Flexible Server to which the database should be restored.
31
28
32
-
Backup vault uses managed identity to access other Azure resources. To restore from backup, Backup vault’s managed identity requires a set of permissions on the storage account to which the server would be restored.
33
-
34
-
To assign the relevant permissions for vault's system-assigned managed identity on the target storage account, see the [set of permissions needed to backup Azure PostgreSQL database](./backup-azure-database-postgresql-overview.md#set-of-permissions-needed-for-azure-postgresql-database-restore).
29
+
To assign the relevant permissions for vault's system-assigned managed identity on the target PostgreSQL – Flexible Server, check the [set of permissions](backup-azure-database-postgresql-flex-overview.md#azure-backup-authentication-with-the-postgresql-server) needed to backup Azure PostgreSQL – Flexible Server database.
35
30
36
31
To restore the recovery point as files to a storage account, the [Backup vault's system-assigned managed identity needs access on the target storage account](./restore-azure-database-postgresql.md#restore-permissions-on-the-target-storage-account).
37
32
38
-
### Fetching the relevant recovery point
33
+
##Fetch the relevant recovery point
39
34
40
-
Fetch all instances using [Get-AzDataProtectionBackupInstance](/powershell/module/az.dataprotection/get-azdataprotectionbackupinstance)command and identify the relevant instance.
35
+
Fetch all instances using [Get-AzDataProtectionBackupInstance](/powershell/module/az.dataprotection/get-azdataprotectionbackupinstance)cmdlet and identify the relevant instance.
You can also use **Az.Resourcegraph** and the [Search-AzDataProtectionBackupInstanceInAzGraph](/powershell/module/az.dataprotection/search-azdataprotectionbackupinstanceinazgraph)command to search recovery points across instances in many vaults and subscriptions.
42
+
You can also use `Az.Resourcegraph` and the [Search-AzDataProtectionBackupInstanceInAzGraph](/powershell/module/az.dataprotection/search-azdataprotectionbackupinstanceinazgraph)cmdlet to search recovery points across instances in many vaults and subscriptions.
You can restore the recovery point for a PostgreSQL – Flexible server database as files only.
62
+
You can restore the recovery point for a PostgreSQL – Flexible Server database as files only.
67
63
68
-
####Restore as files
64
+
### Restore as files
69
65
70
-
Fetch the URI of the container, within the storage account to which permissions were assigned as detailed [above](#set-up-permissions). For example, a container named **testcontainerrestore** under a storage account **testossstorageaccount** with a different subscription.
66
+
Fetch the Uniform Resource Identifier (URI) of the container, within the storage account to which permissions were assigned. For example, a container named `testcontainerrestore` under a storage account `testossstorageaccount` with a different subscription.
Use the [Initialize-AzDataProtectionRestoreRequest](/powershell/module/az.dataprotection/initialize-azdataprotectionrestorerequest)command to prepare the restore request with all relevant details.
72
+
Use the [Initialize-AzDataProtectionRestoreRequest](/powershell/module/az.dataprotection/initialize-azdataprotectionrestorerequest)cmdlet to prepare the restore request with all relevant details.
>After the restore to the target storage account is complete , you can use the pg_restore utility to restore an Azure Database for PostgreSQL – Flexible Server database from the target.
83
80
84
-
Use the [Start-AzDataProtectionBackupInstanceRestore](/powershell/module/az.dataprotection/start-azdataprotectionbackupinstancerestore) command to trigger the restore with the request prepared above.
81
+
To connect to an existing PostgreSQL – Flexible Server and an existing database, use the following cmdlet:
Track all the jobs using the [Get-AzDataProtectionJob](/powershell/module/az.dataprotection/get-azdataprotectionjob) command. You can list all jobs and fetch a particular job detail.
89
+
-`-Fd`: The directory format.
90
+
-`-j`: The number of jobs.
91
+
-`-C`: Starts the output with a cmdlet to create the database itself and then reconnect to it.
93
92
94
-
You can also use *Az.ResourceGraph* to track jobs across all Backup vaults. Use the [Search-AzDataProtectionJobInAzGraph](/powershell/module/az.dataprotection/search-azdataprotectionjobinazgraph) command to get the relevant job, which is across all backup vault.
93
+
The following example shows how the syntax might appear:
### Create PostgreSQL - flexible server from restored storage account
99
+
If you have more than one database to restore, rerun the earlier cmdlet for each database.
100
+
Also, by using multiple concurrent jobs `-j`, you can reduce the restore time of a large database on a **multi-vCore** target server. The number of jobs can be equal to or less than the number of `vCPUs` allocated for the target server.
101
101
102
-
Post restoration completion to the target storage account, you can use **pg_restore** utility to restore an Azure Database for PostgreSQL – Flexible server database from the target. Use the following command to connect to an existing PostgreSQL – Flexible server and an existing database.
102
+
## Trigger the restore
103
+
104
+
To trigger the restore operation with the prepared request, use the [`Start-AzDataProtectionBackupInstanceRestore`](/powershell/module/az.dataprotection/start-azdataprotectionbackupinstancerestore) cmdlet
-C: Begin the output with a command to create the database itself and then reconnect to it.
110
+
## Track jobs
111
+
112
+
Track all jobs by using the [`Get-AzDataProtectionJob`](/powershell/module/az.dataprotection/get-azdataprotectionjob) cmdlet. You can list all jobs and fetch a particular job detail.
111
113
112
-
Here's an example of how this syntax might appear:
114
+
You can also use `Az.ResourceGraph` to track jobs across all Backup vaults. Use the [`Search-AzDataProtectionJobInAzGraph`](/powershell/module/az.dataprotection/search-azdataprotectionjobinazgraph) cmdlet to get the relevant job that is across all Backup vaults.
If you have more than one database to restore, re-run the earlier command for each database.
119
-
120
-
Also, by using multiple concurrent jobs -j, you can reduce the time it takes to restore a large database on a multi-vCore target server. The number of jobs can be equal to or less than the number of vCPUs that are allocated for the target server.
121
-
122
120
## Next steps
123
121
124
-
-[Azure PostgreSQL - flexible server Backup](backup-azure-database-postgresql-flex-overview.md)
122
+
[Troubleshoot common errors for backup and restore operations for Azure Database for PostgreSQL - Flexible Server](backup-azure-database-postgresql-flex-troubleshoot.md).
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-database-postgresql-flex-support-matrix.md
+17-17Lines changed: 17 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,45 +2,45 @@
2
2
title: Azure Database for PostgreSQL- Flexible server support matrix
3
3
description: Provides a summary of support settings and limitations of Azure Database for PostgreSQL- Flexible server backup.
4
4
ms.topic: reference
5
-
ms.date: 12/17/2024
5
+
ms.date: 02/28/2025
6
6
ms.custom: references_regions, ignite-2024
7
7
ms.service: azure-backup
8
8
author: jyothisuri
9
9
ms.author: jsuri
10
10
---
11
11
12
-
# Support matrix for Azure Database for PostgreSQL- Flexible server (preview)
12
+
# Support matrix for Azure Database for PostgreSQL- Flexible Server
13
13
14
-
You can use [Azure Backup](./backup-overview.md) to protect Azure Database for PostgreSQL- Flexible server. This article summarizes supported regions, scenarios, and the limitations.
14
+
You can use [Azure Backup](./backup-overview.md) to protect Azure Database for PostgreSQL- Flexible Server. This article summarizes supported regions, scenarios, and the limitations.
15
15
16
16
## Supported regions
17
17
18
-
Azure Database for PostgreSQL - Flexible server backup is now available in all public regions.
18
+
Azure Database for PostgreSQL - Flexible server backup is generally available in the following regions: East Asia, Central India, Southeast Asia, UK South, and UK West. However, this feature is currently in preview for other regions.
19
19
20
20
## Support scenarios
21
21
22
-
- PostgreSQL Flexible Server backup data can be recovered in user specified storage containers that can be used to rebuild the PostgreSQL flexible server. You can restore this data as a new PostgreSQL - flexible server with the database native tools.
22
+
Consider the following support scenarios when you back up Azure Database for PostgreSQL – Flexible Server:
23
23
24
+
- Vaulted backup restores are only available as **Restore to Files** in user specified storage containers. You can restore this data as a new PostgreSQL - flexible server with the database native tools.
24
25
- Backups for the PostgreSQL server are supported when the Backup Vault is in the same or a different subscription as the database, provided they are within the same tenant and region. Restores are supported across regions (Azure Paired) and across subscriptions within the same tenant.
25
-
26
-
- Recommended limit for the maximum server size is 4 TB.
27
-
26
+
- For vaulted backups, entire server is backed up with all databases. Backup of specific databases isn't supported.
27
+
- Recommended limit for the maximum server size is **1 TB**. While backups can be attempted on server size exceeding 1 TB, which aren't officially supported, and the success of vaulted backups for such server can't be guaranteed.
28
28
- PostgreSQL - Flexible servers encrypted by Customer Managed Key are supported.
29
-
30
-
- Private endpoint-enabled Azure PostgreSQL flexible servers can be backed up by allowing trusted Microsoft services in the network settings.
31
-
32
-
- Backups for PGSQLFlex will exclude databases owned by `azuresu` or `azure_pg_admin`, including the native `postgres` database. As a result, databases with these owners cannot be backed up or restored.
33
-
29
+
- Private endpoint-enabled Azure Database for PostgreSQL - Flexible servers can be backed up by allowing trusted Microsoft services in the network settings.
30
+
- Backups for PostgreSQL Flexible servers exclude databases owned by `azuresu` or `azure_pg_admin`, including the native PostgreSQL database. So, databases with these owners can't be backed up or restored.
34
31
35
32
## Limitation
36
33
37
-
- Currently, restoring backups directly to flexible server isn't supported.
34
+
Azure Database for PostgreSQL – Flexible Server backups include the following limitations:
38
35
39
-
- Currently, backing up individual databases isn't supported. You can only back up the entire server.
36
+
- Vaulted backup doesn't support storage in archive tier.
37
+
- Vaulted backup isn't supported on replicas; backup can be configured only on primary servers.
38
+
- For restore operation, item level recovery (recovery of specific databases) isn't supported.
39
+
- Weekly backups are supported for only one day in the week on which backup is initiated.
40
+
- Vaulted backups don't support tables containing a row with **BYTEA length exceeding 500 MB**.
40
41
41
-
- Only weekly backups are supported with option to opt for only one day in the week on which backup is initiated.
42
42
43
43
44
44
## Next steps
45
45
46
-
-[Back up Azure Database for PostgreSQL -flex server](backup-azure-database-postgresql-flex.md).
46
+
-[Back up Azure Database for PostgreSQL -Flexible Server using Azure portal](tutorial-create-first-backup-azure-database-postgresql-flex.md).
0 commit comments