Skip to content

Commit 5de6614

Browse files
Updates to supported regions & scenarios
1 parent 85ee66f commit 5de6614

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/backup/backup-azure-database-postgresql-flex-support-matrix.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Azure Database for PostgreSQL- Flexible server support matrix
33
description: Provides a summary of support settings and limitations of Azure Database for PostgreSQL- Flexible server backup.
44
ms.topic: reference
5-
ms.date: 04/30/2025
5+
ms.date: 05/15/2025
66
ms.custom: references_regions, ignite-2024
77
ms.service: azure-backup
88
author: jyothisuri
@@ -15,7 +15,7 @@ You can use [Azure Backup](./backup-overview.md) to protect Azure Database for P
1515

1616
## Supported regions
1717

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.
18+
Vaulted backup for PostgreSQL – flexible server is generally available in all public cloud regions and sovereign regions.
1919

2020
## Support scenarios
2121

@@ -26,8 +26,8 @@ Consider the following support scenarios when you back up Azure Database for Pos
2626
- For vaulted backups, entire server is backed up with all databases. Backup of specific databases isn't supported.
2727
- Vaulted backups are supported for server size **<= 1 TB**. If backup is configured on server size larger than 1 TB, the backup operation fails.
2828
- PostgreSQL - Flexible servers encrypted by Customer Managed Key are supported.
29-
- Private endpoint-enabled Azure Database for PostgreSQL - Flexible servers can be backed up by allowing trusted Microsoft services in the network settings.
3029
- 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.
30+
- Recommended frequency for restore operations is once a day. Multiple restore operations triggered in a day can fail.
3131

3232
## Limitation
3333

0 commit comments

Comments
 (0)