APPLIES TO: NoSQL MongoDB Gremlin Table
This article lists frequently asked questions about the Azure Cosmos DB point-in-time restore functionality that's available in continuous backup mode.
How much time does it takes to restore?
Restore time is a function of the data size, the amount of log backup that needs to be replayed, and the number of partitions that need to be restored. Restoring 1 terabyte of data typically takes 30 to 90 minutes.
Can I submit the restore time in local time?
The restore might not happen, depending on whether key resources like databases or containers existed at that time. You can verify by entering the time and looking at a selected database or container for that time. If that is no resources exist to restore, the restore process doesn't work.
How can I track the restoration of an account?
After you submit the restore command and wait on the page, the status bar shows a message about a successfully restored account when the operation finishes. You can also search for the restored account and track its status. While the restore is in progress, the account status is Creating. After the restore operation finishes, the account status changes to Online.
For PowerShell and the Azure CLI, you can track the progress of a restore operation by using the az cosmosdb show
command:
az cosmosdb show \
--resource-group <resource-group> \
--name <account-name>
The provisioningState
value is Succeeded
when the account is online.
{
"virtualNetworkRules": [],
"writeLocations" : [
{
"documentEndpoint": "https://<accountname>.documents.azure.com:443/",
"failoverpriority": 0,
"id": "accountName" ,
"isZoneRedundant" : false,
"locationName": "West US 2",
"provisioningState": "Succeeded"
}
]
}
How can I find out whether a continuous backup mode account was restored from another account?
You can identify whether an account is restored and gets the restore details by using the Azure portal, Azure PowerShell, and the Azure CLI.
What is "instanceId" in the account definition?
At any point in time, an Azure Cosmos DB account's accountName
property is globally unique while it's alive. After the account is deleted, it's possible to create another account with the same name. If that happens, accountName
is no longer enough to identify an instance of an account.
The instance ID, or instanceId
, is a property of an instance of an account. It's used to disambiguate across multiple accounts (live and deleted) if they have same name for restore. You can get the instance ID by running either of these commands:
Get-AzCosmosDBRestorableDatabaseAccount
az cosmosdb restorable-database-account
Note
The name attribute value denotes the instance ID.
Is continuous backup supported for Azure Synapse Link-enabled accounts?
- Synapse Link for database accounts using continuous backup mode and continuous backup mode for Synapse Link enabled accounts are generally available. Currently, customers that disabled Synapse Link from containers can't migrate to continuous backup.
Next steps
- Learn more about continuous backup mode.
- Provision an account with continuous backup by using the Azure portal, PowerShell, the Azure CLI, or Azure Resource Manager.
- Manage permissions required to restore data with continuous backup mode.
- Learn about the resource model of continuous backup mode.