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/cosmos-db/postgresql/concepts-backup.md
+5-31Lines changed: 5 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ ms.service: cosmos-db
7
7
ms.subservice: postgresql
8
8
ms.custom: ignite-2022, references_regions
9
9
ms.topic: conceptual
10
-
ms.date: 12/20/2023
10
+
ms.date: 01/21/2024
11
11
---
12
12
13
13
# Backup and restore in Azure Cosmos DB for PostgreSQL
@@ -41,36 +41,10 @@ Azure Cosmos DB for PostgreSQL supports the following backup redundancy options.
41
41
42
42
* Locally redundant backup storage: This option is automatically chosen for regions that don't support availability zones. When the backups are stored in locally redundant backup storage, multiple copies of backups are stored in the same region.
43
43
44
-
* Cross-region backup (in preview)
44
+
* Cross-region backup
45
45
* Geo-redundant backup storage: You can choose this option at the time of cluster creation. When the backups are stored in another region, in addition to three copies of data stored within the region where your cluster is hosted, the data is replicated to another region.
46
46
47
-
Geo-redundant backup is supported in the following Azure regions.
> Geo-redundant backup and restore in Azure Cosmos DB for PostgreSQL is currently in preview.
71
-
> This preview version is provided without a service level agreement, and it's not recommended
72
-
> for production workloads. Certain features might not be supported or might have constrained
73
-
> capabilities.
47
+
[Azure region where cluster's geo-redundant backup is stored](./resources-regions.md#regional-availability-for-azure-cosmos-db-for-postgresql) depends on the Azure region where the Azure Cosmos DB for PostgreSQL cluster is located.
74
48
75
49
### Backup storage cost
76
50
@@ -87,7 +61,7 @@ database, or if an application accidentally overwrites good data with bad data.
87
61
> [!NOTE]
88
62
> While cluster backups are always stored for 35 days, you might need to
89
63
> open a support request to restore the cluster to a point that is earlier
90
-
> than the latest failover time. Maintenance and compute / storage scaling operations use
64
+
> than the latest failover time. In addition to [high availability (HA)](./concepts-high-availability.md), [maintenance](./concepts-maintenance.md) and compute / storage scaling operations use
91
65
> failovers to minimize downtime during these operations.
92
66
93
67
For same-region restore, when all nodes are up and running, you can restore cluster without any data loss. In an extremely rare case of a node experiencing a catastrophic event (and [high availability](./concepts-high-availability.md) isn't enabled on the cluster), you might lose up to 5 minutes of data.
@@ -115,4 +89,4 @@ In most cases, cluster restore takes up to 1 hour.
115
89
* See the steps to [restore a cluster](howto-restore-portal.md)
116
90
in the Azure portal.
117
91
* See [backup and restore limits and limitations](./reference-limits.md#backup-and-restore).
118
-
* Learn about [Azure availability zones](../../availability-zones/az-overview.md).
92
+
* Learn about [Azure availability zones](../../availability-zones/az-overview.md).
# Product updates for Azure Cosmos DB for PostgreSQL
@@ -22,6 +22,10 @@ Updates that don’t directly affect the internals of a cluster are rolled out g
22
22
23
23
Updates that change cluster internals, such as installing a [new minor PostgreSQL version](https://www.postgresql.org/developer/roadmap/), are delivered to existing clusters as part of the next [scheduled maintenance](concepts-maintenance.md) event. Such updates are available immediately to newly created clusters.
24
24
25
+
### January 2024
26
+
* General availability: Geo-redundant backup and restore
27
+
* Learn more about [backup and restore Azure Cosmos DB for PostgreSQL](./concepts-backup.md#backup-redundancy)
28
+
25
29
### December 2023
26
30
* Preview: [PgBouncer](./concepts-connection-pool.md) is now supported with [Microsoft Entra ID authentication](./concepts-authentication.md#microsoft-entra-id-authentication-preview).
27
31
* General availability: Azure Cosmos DB for PostgreSQL is now available in Poland Central and South India.
@@ -170,7 +174,6 @@ might have capabilities with limitations. For more information, see
Copy file name to clipboardExpand all lines: articles/cosmos-db/postgresql/reference-limits.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
@@ -6,7 +6,7 @@ author: niklarin
6
6
ms.service: cosmos-db
7
7
ms.subservice: postgresql
8
8
ms.topic: conceptual
9
-
ms.date: 01/08/2024
9
+
ms.date: 01/21/2024
10
10
---
11
11
12
12
# Azure Cosmos DB for PostgreSQL limits and limitations
@@ -116,12 +116,12 @@ By default this database is called `citus`. Azure Cosmos DB for PostgreSQL suppo
116
116
117
117
## Backup and restore
118
118
119
-
### Geo-redundant backup and restore (preview)
119
+
### Geo-redundant backup and restore
120
120
* Geo-redundant backup can be enabled only during cluster creation.
121
-
* You can enable geo-redundant backup when you perform a cluster restore.
121
+
* You can enable geo-redundant backup when you perform a [cluster restore](./howto-restore-portal.md).
122
122
* You can enable geo-redundant backup when you [promote a cluster read-replica to an independent cluster](./howto-read-replicas-portal.md#promote-a-read-replica).
123
-
* Geo-redundant backup can't be enabled on single node clusters with [burstable compute](./concepts-burstable-compute.md).
124
123
* Geo-redundant backup can't be disabled once cluster is created.
124
+
* Geo-redundant backup can't be enabled on single node clusters with [burstable compute](./concepts-burstable-compute.md).
125
125
*[Customer managed key (CMK)](./concepts-customer-managed-keys.md) isn't supported for clusters with geo-redundant backup enabled.
126
126
* Azure Cosmos DB for PostgreSQL cluster with geo-redundant backup enabled can't have a [cluster read replica](./concepts-read-replicas.md) in the region where geo-redundant backup is stored.
Copy file name to clipboardExpand all lines: articles/cosmos-db/postgresql/resources-regions.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
@@ -1,13 +1,13 @@
1
1
---
2
2
title: Regional availability – Azure Cosmos DB for PostgreSQL
3
-
description: Azure regions where you can run a cluster
3
+
description: Azure regions where you can run an Azure Cosmos DB for PostgreSQL cluster, configure geo-redundant backup, and can get AZ outage resiliency protection
4
4
ms.author: nlarin
5
5
author: niklarin
6
6
ms.service: cosmos-db
7
7
ms.subservice: postgresql
8
8
ms.topic: conceptual
9
9
ms.custom: references_regions, ignite-2022
10
-
ms.date: 01/02/2024
10
+
ms.date: 01/21/2024
11
11
12
12
---
13
13
@@ -24,7 +24,7 @@ Azure Cosmos DB for PostgreSQL is available in the following Azure regions:
24
24
| Brazil South |:heavy_check_mark:|:heavy_check_mark:|:x:|
25
25
| Canada Central |:heavy_check_mark:|:heavy_check_mark:| Canada East |
26
26
| Canada East |:heavy_check_mark:| N/A | Canada Central |
27
-
| Central India |:heavy_check_mark:|:heavy_check_mark:|:x:|
27
+
| Central India |:heavy_check_mark:|:heavy_check_mark:|South India|
28
28
| Central US |:heavy_check_mark:|:heavy_check_mark:| East US 2 |
29
29
| East Asia |:heavy_check_mark:|:heavy_check_mark:| Southeast Asia |
30
30
| East US |:heavy_check_mark:|:heavy_check_mark:| West US |
@@ -39,7 +39,7 @@ Azure Cosmos DB for PostgreSQL is available in the following Azure regions:
39
39
| Poland Central |:heavy_check_mark:|:heavy_check_mark:|:x:|
40
40
| Qatar Central |:heavy_check_mark:|:x:|:x:|
41
41
| South Central US |:heavy_check_mark:|:heavy_check_mark:| North Central US |
42
-
| South India |:heavy_check_mark:| N/A |:x:|
42
+
| South India |:heavy_check_mark:| N/A |Central India|
43
43
| Southeast Asia |:heavy_check_mark:|:x:| East Asia |
44
44
| Sweden Central |:heavy_check_mark:|:heavy_check_mark:|:x:|
45
45
| Switzerland North |:heavy_check_mark:|:heavy_check_mark:| Switzerland West |
0 commit comments