Enabling Immutability

To enable immutability, you must do the following:

  1. Configure the following settings when you create an S3 bucket or Azure container:
  • Amazon S3 Storage, S3 Compatible, IBM Cloud, Wasabi Cloud — You must enable the Object Lock and Versioning features on your S3 bucket when you create the bucket.


Note that most vendors allow enabling Object Lock only at the moment of creating the bucket.

For more information on enabling the Object Lock and Versioning features, see these Amazon articles: Creating a bucket, Using S3 Object Lock and Enabling versioning on buckets.

  • Azure Storage — You must enable support for version-level WORM on the container and enable blob versioning for your storage account when you create a storage account. For instruction on how to configure your Azure storage account with the necessary settings, see this Veeam KB article.

For more information on enabling version-level WORM for a container, see Microsoft Docs.

For more information on blob versioning for a storage account, see Microsoft Docs.


When you create the storage account, by default the version-level immutability support option is enabled. You must disable it, otherwise immutability will not be applied for your Azure object storage. For more information, see Microsoft Docs.

  1. Enable the immutability option when you add an object storage repository to the backup infrastructure at the Container step (for Azure object storage repository) or Bucket step (for Amazon S3 or S3 compatible object storage repositories) of the new Object Storage Repository wizard.

Page updated 3/12/2024

Page content applies to build