187

Tip 334 - How to copy data from one Cosmos DB container to another container

 3 years ago
source link: https://microsoft.github.io/AzureTipsAndTricks/blog/tip334.html
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client

# How to copy data from one Cosmos DB container to another container

# Cosmos DB data migration

Sometimes, you need to migrate data from one Azure Cosmos DB (opens new window) to another. You can, for instance, do this if you need to change the partition key of a container, or to consolidate Cosmos DB instances.

The Cosmos DB live data migrator tool (opens new window) enables you to migrate data from one container to another. In this post, we'll configure the tool to try it out.

# Prerequisites

If you want to follow along, you'll need the following:

# Use the Cosmos DB live data migrator tool

Let's try it out. To use the migration tool, we first need to create an application registration.

  1. Go to the Azure portal (opens new window)

  2. Search for "app registrations", and click on the App registration result

  3. Click New registration to start registering the migration tool app

    1. Type in a Name for the application. For instance "tips01".
    2. Put in a *Redirect URI. This should contain the name, so something like "https://tips01-ui.azurewebsites.net/signin-oidc"
    3. Click Register
    118register1.png

    (Create an App Registration in the Azure portal)

    1. Next, note the Application (client) ID in the overview blade of the App registration. Copy it to use it later
    2. Navigate to the Authentication menu
    3. Fill in a Front-channel logout URL. Again, this should contain the name, like "https://tips01-ui.azurewebsites.net/signout-callback-oidc"
    4. Check ID tokens (used for implicit and hybrid flows)
    5. Click Save
    6. Next, go to the Manifest menu
    7. Add to the requiredResourceAccess node, so that it looks like this:
	"requiredResourceAccess": [
		{
			"resourceAppId": "00000003-0000-0000-c000-000000000000",
			"resourceAccess": [
				{
					"id": "e1fe6dd8-ba31-4d61-89e7-88639da4683d",
					"type": "Scope"
				},
				{
					"id": "b340eb25-3456-403f-be2f-af7a0d370277",
					"type": "Scope"
				}
			]
		}
	],
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
  1. Click Save
118register2.png

(Change the manifest of the App registration)

  1. In the manifest, copy the publisherDomain for later

Now that we have an application registration, we can deploy the migration app.

  1. Go to this link (opens new window) to start creating the migration app

    1. First, select a Resource Group
    2. Next, type in a Resource Name Prefix. This should be the name that you used earlier. So, in my case, it is "tips01"
    3. In Default Source Database Account Name, put in a name for the Cosmos DB connection that will serve as the migration source. This can be anything, and you can change it later
    4. For Default Source Database Account Connection String, type in the connection string for the source Cosmos DB. You can find this in the Azure portal
    5. Type a name for the Default Destination Database Account Name
    6. Provide the connection string for the destination Cosmos DB account in Default Destination Database Account Connection String
    7. In the Allowed Users field, provide a user that will use the migration tool. This can be an objectId or email address of a user that is in the same tenant where the application will be deployed. You can provide multiple users by separating them with the "|" character
    8. Next, provide the publisher domain from the App Registration Manifest in the Aad App Registration Publisher Domain field
    9. Finally, in the Aad App Registration Client ID field, put in the Application (client) ID from the App registration
    10. Click Review + create and then Create to deploy the migration tool
    118register3.png

    (Deploy the migration tool)

The migration tool will deploy several resources. This includes an Azure App Service Web App (opens new window) that runs the UI for the tool. Find the Web App in the Azure portal and open the UI in a browser. The URL will use the name that you provided earlier. So, in my case, it is https://tips01-ui.azurewebsites.net

  1. To start creating a migration, click Create

  2. Now fill in the source and destination details

    1. For source and destination, provide the Cosmos DB database name in the DB field
    2. Fill in the database Container name
    3. Provide the Partition key for the source and destination
    4. Click Create / Start
    118createmigration.png

    (Create a new migration)

  3. You can watch the progress of any open migrations by clicking on the List menu and refreshing your browser

  4. When all documents are migrated, click Complete to mark the migration as finished

118result.png

(Complete the migration)

# Conclusion

Migrating data between Azure Cosmos DB (opens new window) containers can be difficult. The Cosmos DB live data migrator tool (opens new window) helps to create and manage migrations. Go and check it out!


report

Recommend

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK