edit

Author: anaharris-ms

.openpublishing.redirection.json

@@ -10883,6 +10883,11 @@
             "source_path_from_root": "/articles/networking/disaster-recovery-dns-traffic-manager.md",
             "redirect_url": "/azure/reliability/reliability-traffic-manager",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/cosmos-db/mongodb/vcore/high-availability.md",
+            "redirect_url": "/azure/reliability/reliability-cosmos-mongodb",
+            "redirect_document_id": false
         }
 
     ]

articles/cosmos-db/mongodb/vcore/TOC.yml

@@ -30,6 +30,8 @@
           href: vector-search-ai.md
     - name: MongoDB feature support
       href: compatibility.md
+    - name: Reliability
+      href: /azure/reliability/reliability-cosmos-mongodb?toc=/azure/cosmos-db/mongodb/vcore/toc.json
     - name: High availability
       href: high-availability.md
     - name: Failover and disaster recovery

articles/cosmos-db/mongodb/vcore/high-availability.md

@@ -284,12 +284,8 @@
       href: reliability-chaos-studio.md
     - name: Azure Community Training
       href: reliability-community-training.md
-    - name : Azure Cosmos DB for MongoDB vCore
-      items:
-      - name: Availability zones
-        href: /azure/cosmos-db/mongodb/vcore/high-availability?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json
-      - name: Disaster recovery
-        href : ../cosmos-db/mongodb/vcore/failover-disaster-recovery.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json
+    - name: Azure Cosmos DB for MongoDB vCore
+      href: reliability-cosmos-mongodb.md
     - name: Azure Databox
       href: ../databox/data-box-disk-faq.yml?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json#how-can-i-recover-my-data-if-an-entire-region-fails-
     - name: Azure Data Manager for Energy

articles/reliability/TOC.yml

@@ -0,0 +1,81 @@
+---
+title: Reliability in Azure Cosmos DB for MongoDB vCore
+description: Find out about reliability in Azure Cosmos DB for MongoDB vCore
+author: anaharris-ms
+ms.author: gahllevy
+ms.reviewer: sidandrews
+ms.service: cosmos-db
+ms.subservice: mongodb
+ms.topic: conceptual
+ms.date: 02/13/2024
+ms.custom: references_regions, subject-reliability
+CustomerIntent: As a cloud architect/engineer, I need general guidance reliability in Azure Cosmos DB for MongoDB vCore
+---
+
+# Reliability in Azure Cosmos DB for MongoDB vCore
+
+[!INCLUDE[MongoDB vCore](/cosmos-db/includes/appliesto-mongodb-vcore)]
+
+This article contains detailed information on regional resiliency with [availability zones](#availability-zone-support) and [cross-region disaster recovery and business continuity](#cross-region-disaster-recovery-and-business-continuity) for Azure Cosmos DB for MongoDB vCore.
+
+For an architectural overview of reliability in Azure, see [Azure reliability](/azure/architecture/framework/resiliency/overview).
+
+
+## Availability zone support
+
+[!INCLUDE [Availability zone description](includes/reliability-availability-zone-description-include.md)]
+
+To gain availability zone support, you must enable High availability (HA). 
+
+HA avoids database downtime by maintaining standby replicas of every shard in a cluster. If a shard goes down, Azure Cosmos DB for MongoDB vCore switches incoming connections from the failed shard to its standby replica.
+
+When HA is enabled in a region that supports availability zones, HA replica shards are provisioned in a different availability zone from their primary shards. HA replicas don't receive requests from clients unless their primary shard fails.
+
+If HA is disabled, each shard has its own locally redundant storage (LRS) with three synchronous replicas maintained by Azure Storage service. If there's a single replica failure, the Azure Storage service detects the failure, and transparently re-creates the relevant data. For LRS storage durability, see [Summary of redundancy options](/storage/common/storage-redundancy#summary-of-redundancy-options). However, in the case of a region failure,  you run the risk of extensive downtime and possible data loss.
+
+
+### Prerequisites
+
+Your Azure Cosmos DB for MongoDB vCore cluster must be created in the following regions:
+
+-	Australia East  
+-	Southeast Asia 
+-	Canada Central
+-	North Europe
+-	UK South
+-	West Europe
+-	Central US
+-	East US
+-	East US 2
+-	South Central US
+-	West US 2
+
+
+### Create a resource with availability zones enabled
+
+To enable availability zones, you must enable High availability (HA) when [creating a cluster](quickstart-portal.md) or in the [**Scale** section of an existing cluster](how-to-scale-cluster.md) in the Azure portal.
+
+
+## Cross-region disaster recovery and business continuity
+
+[!INCLUDE [introduction to disaster recovery](includes/reliability-disaster-recovery-description-include.md)]
+
+
+
+Azure Cosmos DB for MongoDB vCore does not provide built-in automatic failover or disaster recovery. Planning for high availability is a critical step as your solution scales.
+
+Azure Cosmos DB for MongoDB vCore automatically takes backups of your data at regular intervals. The automatic backups are taken without affecting the performance or availability of the database operations. All backups are performed automatically in the background and stored separately from the source data in a storage service. These automatic backups are useful in scenarios when you accidentally delete or modify resources and later require the original versions.
+
+Automatic backups are retained in various intervals based on whether the cluster is currently active or recently deleted.
+
+| | Retention period |
+| --- | --- |
+| **Active clusters** | `35` days |
+| **Deleted clusters** | `7` days |
+
+## Next steps
+[Scale a cluster in Azure Cosmos DB for MongoDB vCore](how-to-scale-cluster.md)
+
+- Read more about [feature compatibility with MongoDB](compatibility.md).
+- Review options for [migrating from MongoDB to Azure Cosmos DB for MongoDB vCore](migration-options.md)
+- Get started by [creating an account](quickstart-portal.md).

articles/reliability/reliability-cosmos-mongodb.md

@@ -103,7 +103,7 @@ For a more detailed overview of reliability principles in Azure, see [Reliabilit
 |-------|-------|-------|
 |Azure Chaos Studio | [Reliability in Azure Chaos Studio](reliability-chaos-studio.md)| [Reliability in Azure Chaos Studio](reliability-chaos-studio.md)|
 |Azure Community Training|[Reliability in Community Training](reliability-community-training.md) |[Reliability in Community Training](reliability-community-training.md) |
-|Azure Cosmos DB for MongoDB vCore|[High availability in Azure Cosmos DB for MongoDB vCore](/azure/cosmos-db/mongodb/vcore/high-availability?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json)|[Failover for business continuity and disaster recovery with Azure Cosmos DB for MongoDB vCore](../cosmos-db/mongodb/vcore/failover-disaster-recovery.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json) |
+|Azure Cosmos DB for MongoDB vCore|[Reliability in Azure Cosmos DB for MongoDB vCore](./reliability-cosmos-mongodb.md)|[Reliability in Azure Cosmos DB for MongoDB vCore](./reliability-cosmos-mongodb.md) |
 |Azure Databox| |[Microsoft Azure Data Box Disk FAQ](../databox/data-box-disk-faq.yml?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json#how-can-i-recover-my-data-if-an-entire-region-fails-) |
 |Azure Data Manager for Energy| [Reliability in Azure Data Manager for Energy](./reliability-energy-data-services.md) |[Reliability in Azure Data Manager for Energy](./reliability-energy-data-services.md) |
 |Azure Data Share| |[Disaster recovery for Azure Data Share](../data-share/disaster-recovery.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json)|