Azure Blob Storage Destination

This page describes the Azure Blob Storage destination

Duplicati supports backing up to Azure Blob Storage, which is a large scale object storage, similar to S3.

User interface

To configure Azure Blob Storage you must fill in: container name, account name and access key. To use a SAS token instead of an access key, use the advanced options.

URL format for Commandline

To use the Azure Blob Storage destination, you can use the following URL format:

azure://<container>/<prefix>
  ?azure-account-name=<account id>
  &azure-access-key=<access key>

Create container

You can create the container via the Azure portal, but if you prefer, you can also let Duplicati create the container for you. The container names are unique within the storage account and has a number of restrictions.

If you use the UI, the "Test connection" button will prompt you if the container needs to be created.

Using a Shared Access Signature (SAS) token

Instead of using a traditional Access Key, you can also use a SAS token. To use this, supply it instead of the access key, for example:

azure://<container>/<prefix>
  ?azure-account-name=<account id>
  &azure-access-sas-token=<SAS token>

Cold storage

Since Duplicati stable version 2.2, Duplicati recognizes data in cold storage and will avoid downloading these files for testing. The recommended way to use this is to set up life-cycle rules that move files into cold storage after a period. Once the files are in cold storage, Duplicati will not attempt to read them.

However, if you have retention enabled, you must set --no-auto-compact as Duplicati will otherwise attempt to download the files from cold storage, in order to compact them.

Similarly, for a restore, you must manually move files from cold storage into the bucket before attempting the restore operation.