You can restore Azure Cosmos DB for NoSQL database containers to a Cosmos DB for NoSQL account on a different Azure subscription. You can also restore the database and containers with the same name or a different name.
Procedure
-
From the navigation page, click Protect > Databases > Cosmos DB for NoSQL instance.
-
In the Backup History section, select a date that contains a backup, and then click Restore.
Dates with a grey circle indicate that a backup exists for that day. You can also select the time range or a specific time of the backup.
The Backup content page appears.
-
Select the backups to restore.
-
To use the latest backup, in the upper-right corner of the page, click Show latest backups.
-
To use a backup from a specific date, in the upper-right corner of the page, click Show backups as of a specific date, and then select the backup.
-
To use a backup from a specific date range, in the upper-right corner of the page, click Show backup for a date range, and then select the backup.
-
-
Select the data that you want to restore
-
To restore all of the data, select the check box next to instance name.
-
To restore individual containers, click the instance name > database name, and then select the check box next to each container that you want to restore.
-
-
Click Restore.
The Restore options page appears.
-
From the Destination account list, select the Azure cloud account where you want to restore the Cosmos DB for NoSQL containers.
-
To redirect the selected containers to a different Cosmos DB for NoSQL account in Azure, move the Redirect all containers toggle key to the right, and then select a destination Cosmos DB for NoSQL account.
By default, redirect is enabled. If you are restoring to a Cosmos DB for NoSQL account with the same name as in the source cloud account, move the Redirect all containers toggle key to the left.
-
To increase the Request Units per second (RU/s) on the destination container, move the Adjust write capacity toggle to the right, and then select the number of RU/s. By default, the restore operation uses the RU/s value you specify in the user interface.
Notes
-
The software will increase the number of RU/s of the container only if the given value is higher than the provisioned RU/s of the source container at the time of the backup.
-
If the containers have autoscale throughput enabled, the software will increase the RU/s during the restore, but only if the given value is more than the maximum RU/s.
-
If you want to restore containers that had shared throughput during the backup, do not enable the Adjust write capacity toggle setting for the restore. For more information about shared throughput, go to Set throughput on a database on Microsoft's website.
-
You can also use the bCosmosDBBoostContainerThroughput setting if you want to increase the throughput RU/s of the destination container automatically to an optimal value based on the number of physical partitions at the source.
-
When the data restore is complete, the software sets the throughput on the destination container to be the same as that of the source container at the time of the backup.
-
-
In the Number of parallel writers box, type the number of streams to be used by the restore operation.
-
If you want to restore containers that already exist on the destination, move the Overwrite destination containers toggle key to the right.
If you do not enable this option and a container already exists on the destination, the restore jobs may fail.
-
To restore a container with a different name, under Content, in the Actions column, click the Edit icon for the container that you want to change the name.
The Edit dialog box appears.
-
To change the database name, in the Destination database box, type a new name.
-
To change the container name, in the Destination container box, type a new name.
-
Click Submit.