Veeam Backup & Replication allows you to prohibit deletion of data from the extents of the scale-out backup repository by making that data temporarily immutable. It is done for increased security: immutability protects your data from loss as a result of attacks, malware activity or any other injurious actions.
You can enable the immutability feature for any tier of scale-out backup repository.
To learn how immutability works with performance tier of the scale-out backup repository, see Immutability for Performance Tier.
To learn how immutability works with capacity tier of the scale-out backup repository, see Immutability for Capacity Tier.
To learn how immutability works with archive tier of the scale-out backup repository, see Immutability for Archive Tier.
In order to use immutability, you must specify the following settings for your object storage:
- Amazon S3 Storage and S3 Compatible
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 and Enabling versioning on buckets.
- Azure Storage
You must configure immutability policies for blob versions and enable blob versioning for your storage account when you create a storage account.
For more information on enabling immutability 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.
For considerations and limitations on immutability, see Considerations and Limitations.