Merge pull request #264524 from niklarin/geo-backup

Geo backup update

Author: prmerger-automator[bot]

articles/cosmos-db/postgresql/howto-restore-portal.md

@@ -7,7 +7,7 @@ ms.service: cosmos-db
 ms.subservice: postgresql
 ms.custom: ignite-2022, references_regions
 ms.topic: how-to
-ms.date: 01/21/2024
+ms.date: 01/28/2024
 ---
 
 # Backup and point-in-time restore of a cluster in Azure Cosmos DB for PostgreSQL
@@ -29,8 +29,8 @@ a custom restore point within your retention period.
 Enabling geo-redundant backup is possible during cluster creation on the **Scale** screen that can be accessed on the **Basics** tab. Click the **Save** button to apply your selection. 
 
 > [!NOTE]
-> Geo-redundant backup can be enabled only during cluster creation. 
-> You can't disable geo-redundant backup once cluster is created.
+> Geo-redundant backup can be enabled only during cluster creation or cluster restore. 
+> You can't disable geo-redundant backup once cluster is created. 
 
 ## Confirm type of backup
 To check what type of backup is enabled on a cluster, follow these steps:
@@ -53,6 +53,8 @@ earliest existing backup.
 
 1. If cluster has geo-redundant backup enabled, select remote or same region for restore in the **Location** field. On clusters with zone-redundant and locally redundant backup, location field isn't editable.
 
+1. Set **Geo-redundant backup** checkbox for geo-redundant backup *for the restored cluster* to be stored [in another Azure region](./resources-regions.md). 
+
 1. Select **Next**. 
 
 1. (optional) Make data encryption selection for restored cluster on the **Encryption** tab.
@@ -74,6 +76,8 @@ and time of your choosing.
 
 1. If cluster has geo-redundant backup enabled, select remote or same region for restore in the **Location** field. On clusters with zone-redundant and locally redundant backup, location field isn't editable.
 
+1. Set **Geo-redundant backup** checkbox for geo-redundant backup *for the restored cluster* to be stored [in another Azure region](./resources-regions.md). 
+
 1. Select **Next**. 
 
 1. (optional) Make data encryption selection for restored cluster on the **Encryption** tab.

articles/cosmos-db/postgresql/reference-limits.md

@@ -6,7 +6,7 @@ author: niklarin
 ms.service: cosmos-db
 ms.subservice: postgresql
 ms.topic: conceptual
-ms.date: 01/21/2024
+ms.date: 01/28/2024
 ---
 
 # Azure Cosmos DB for PostgreSQL limits and limitations
@@ -119,7 +119,6 @@ By default this database is called `citus`. Azure Cosmos DB for PostgreSQL suppo
 ### Geo-redundant backup and restore
 * Geo-redundant backup can be enabled only during cluster creation.
     * You can enable geo-redundant backup when you perform a [cluster restore](./howto-restore-portal.md).
-    * 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).
 * Geo-redundant backup can't be disabled once cluster is created.
 * Geo-redundant backup can't be enabled on single node clusters with [burstable compute](./concepts-burstable-compute.md).
 * [Customer managed key (CMK)](./concepts-customer-managed-keys.md) isn't supported for clusters with geo-redundant backup enabled.