|
| 1 | +--- |
| 2 | +title: Relocate an Azure Cosmos DB NoSQL account to another region |
| 3 | +description: Learn how to relocate an Azure Cosmos DB NoSQL account to another region. |
| 4 | +author: seesharprun |
| 5 | +ms.service: cosmos-db |
| 6 | +ms.subservice: nosql |
| 7 | +ms.topic: how-to |
| 8 | +ms.custom: |
| 9 | + - subject-relocation |
| 10 | +ms.date: 06/11/2024 |
| 11 | +ms.author: sidandrews |
| 12 | +ms.reviewer: mjbrown |
| 13 | +--- |
| 14 | + |
| 15 | +# Relocate an Azure Cosmos DB NoSQL account to another region |
| 16 | + |
| 17 | + |
| 18 | +This article describes how to either: |
| 19 | + |
| 20 | +- Relocate a region where data is replicated in Azure Cosmos DB. |
| 21 | +- Migrate account (Azure Resource Manager) metadata and data from one region to another. |
| 22 | + |
| 23 | + |
| 24 | +## Prerequisites |
| 25 | + |
| 26 | +- An app registration must be created with delegated permission to the source and target resource group instance and “API permission” for “User.ReadBasic.All”. |
| 27 | + |
| 28 | +- The selected Cosmos DB API must remain same from source to target. This document uses SQL DB API. |
| 29 | + |
| 30 | +- Account names must be limited to 44 characters, all lowercase. |
| 31 | + |
| 32 | +- When you add or remove locations to an Azure Cosmos account, you can’t simultaneously modify other properties. |
| 33 | + |
| 34 | +- Identify all Cosmos DB dependent resources. |
| 35 | + |
| 36 | + |
| 37 | +## Downtime |
| 38 | + |
| 39 | +## Considerations for Service Endpoints |
| 40 | + |
| 41 | +The virtual network service endpoints for Azure Cosmos DB restrict access to a specified virtual network. The endpoints can also restrict access to a list of IPv4 (internet protocol version 4) address ranges. Any user connecting to the Event Hubs from outside those sources is denied access. If Service endpoints were configured in the source region for the Event Hubs resource, the same would need to be done in the target one. |
| 42 | + |
| 43 | +For a successful recreation of the Azure Cosmos DB to the target region, the VNet and Subnet must be created beforehand. In case the move of these two resources is being carried out with the Azure Resource Mover tool, the service endpoints won’t be configured automatically. Hence, they need to be configured manually, which can be done through the [Azure portal](/azure/key-vault/general/quick-create-portal), the [Azure CLI](/azure/key-vault/general/quick-create-cli), or [Azure PowerShell](/azure/key-vault/general/quick-create-powershell). |
| 44 | + |
| 45 | + |
| 46 | + |
| 47 | +## Redeploy without data |
| 48 | + |
| 49 | +For cases where the Cosmos DB instance needs to be relocated alone without the configuration and customer data, the instance itself can be created using [Microsoft.DocumentDB databaseAccounts](/azure/templates/microsoft.documentdb/2021-04-15/databaseaccounts?tabs=json&pivots=deployment-language-arm-template) |
| 50 | + |
| 51 | +## Redeploy with data |
| 52 | + |
| 53 | +Azure Cosmos DB supports data replication natively, so moving data from one region to another is simple. You can accomplish it by using the Azure portal, Azure PowerShell, or the Azure CLI. It involves the following steps: |
| 54 | + |
| 55 | +1. Add a new region to the account. |
| 56 | + |
| 57 | + To add a new region to an Azure Cosmos DB account, see [Add/remove regions to an Azure Cosmos DB account](../cosmos-db/how-to-manage-database-account.yml#add-remove-regions-from-your-database-account). |
| 58 | + |
| 59 | +1. Perform a manual failover to the new region. |
| 60 | + |
| 61 | + When the region that's being removed is currently the write region for the account, you'll need to start a failover to the new region added in the previous step. This is a zero-downtime operation. If you're moving a read region in a multiple-region account, you can skip this step. |
| 62 | + |
| 63 | + To start a failover, see [Perform manual failover on an Azure Cosmos DB account](../cosmos-db/how-to-manage-database-account.yml#perform-manual-failover-on-an-azure-cosmos-db-account). |
| 64 | + |
| 65 | +1. Remove the original region. |
| 66 | + |
| 67 | + To remove a region from an Azure Cosmos DB account, see [Add/remove regions from your Azure Cosmos DB account](../cosmos-db/how-to-manage-database-account.yml#add-remove-regions-from-your-database-account). |
| 68 | + |
| 69 | +> [!NOTE] |
| 70 | +> If you perform a failover operation or add/remove a new region while an [asynchronous throughput scaling operation](../cosmos-db/scaling-provisioned-throughput-best-practices.md#background-on-scaling-rus) is in progress, the throughput scale-up operation will be paused. It will resume automatically when the failover or add/remove region operation is complete. |
| 71 | +
|
| 72 | +## Redeploy Azure Cosmos DB account metadata |
| 73 | + |
| 74 | +Azure Cosmos DB does not natively support migrating account metadata from one region to another. To migrate both the account metadata and customer data from one region to another, you must create a new account in the desired region and then copy the data manually. |
| 75 | + |
| 76 | +> [!IMPORTANT] |
| 77 | +> It is not necessary to migrate the account metadata if the data is stored or moved to a different region. The region in which the account metadata resides has no impact on the performance, security or any other operational aspects of your Azure Cosmos DB account. |
| 78 | +
|
| 79 | +A near-zero-downtime migration for the API for NoSQL requires the use of the [change feed](../cosmos-db/change-feed.md) or a tool that uses it. |
| 80 | + |
| 81 | +The following steps demonstrate how to migrate an Azure Cosmos DB account for the API for NoSQL and its data from one region to another: |
| 82 | + |
| 83 | +1. Create a new Azure Cosmos DB account in the desired region. |
| 84 | + |
| 85 | + To create a new account via the Azure portal, PowerShell, or the Azure CLI, see [Create an Azure Cosmos DB account](../cosmos-db/how-to-manage-database-account.yml#create-an-account). |
| 86 | + |
| 87 | +1. Create a new database and container. |
| 88 | + |
| 89 | + To create a new database and container, see [Create an Azure Cosmos DB container](../cosmos-db/nosql/how-to-create-container.md). |
| 90 | + |
| 91 | +1. Migrate data by using the Azure Cosmos DB Spark Connector live migration sample. |
| 92 | + |
| 93 | + To migrate data with near zero downtime, see [Live Migrate Azure Cosmos DB SQL API Containers data with Spark Connector](https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/cosmos/azure-cosmos-spark_3_2-12/Samples/DatabricksLiveContainerMigration). |
| 94 | + |
| 95 | +1. Update the application connection string. |
| 96 | + |
| 97 | + With the Live Data Migration sample still running, update the connection information in the new deployment of your application. You can retrieve the endpoints and keys for your application from the Azure portal. |
| 98 | + |
| 99 | + :::image type="content" source="../cosmos-db/media/secure-access-to-data/nosql-database-security-master-key-portal.png" alt-text="Access control in the Azure portal, demonstrating NoSQL database security."::: |
| 100 | + |
| 101 | +1. Redirect requests to the new application. |
| 102 | + |
| 103 | + After the new application is connected to Azure Cosmos DB, you can redirect client requests to your new deployment. |
| 104 | + |
| 105 | +1. Delete any resources that you no longer need. |
| 106 | + |
| 107 | + With requests now fully redirected to the new instance, you can delete the old Azure Cosmos DB account and stop the Live Data Migrator sample. |
| 108 | + |
| 109 | +## Next steps |
| 110 | + |
| 111 | +For more information and examples on how to manage the Azure Cosmos DB account as well as databases and containers, read the following articles: |
| 112 | + |
| 113 | +* [Manage an Azure Cosmos DB account](../cosmos-db/how-to-manage-database-account.yml) |
| 114 | +* [Change feed in Azure Cosmos DB](../cosmos-db/change-feed.md) |
0 commit comments