Cosmos DB Backup

When processing a Cosmos DB account added to a backup policy, Veeam Backup for Microsoft Azure uses continuous backup — a native Microsoft Azure capability that allows you to eliminate consumption of extra provisioned throughput without affecting the database performance and availability.

Every 8 hours, Veeam Backup for Microsoft Azure runs configuration sessions to check the continuous backup retention period defined in Microsoft Azure for all the Cosmos DB accounts added to the backup scope. If the retention period differs from the retention period specified in the backup policy settings, Veeam Backup for Microsoft Azure redefines the retention period in Microsoft Azure.

For each configuration session, Veeam Backup for Microsoft Azure saves its date and time in the configuration database. This information is then used to calculate the restore window for the protected Cosmos DB accounts. For more information on how continuous backup is performed, see Microsoft Docs.

Backup to Repository

If you enable backup to a repository, Veeam Backup for Microsoft Azure performs the following steps:

  1. Launches a worker instance in an Azure region where the database of the processed Cosmos DB for PostgreSQL account resides.

By default, Veeam Backup for Microsoft Azure launches worker instances using virtual networks created automatically. However, you can add specific worker configurations. For more information, see Managing Worker Instances.

  1. Uses the worker instance to create a dump file of user data contained in the database, transfers the data to the target backup repository and stores it in the native Veeam format.

Note

Veeam Backup for Microsoft Azure does not include any metadata such as credentials in the dump file.

  1. Deallocates the worker instance when the backup session completes.
  1. If you enable the backup archiving mechanism, Veeam Backup for Microsoft Azure performs the following operations:
  1. Launches a worker instance in an Azure region in which the target backup repository resides.
  2. Retrieves data from the target backup repository and transfers it to the target archive repository.
  3. Deallocates the worker instance when the archive session completes.

Related Topics

Backup Chain