Considerations and Limitations

This section lists considerations and known limitations for object storage repositories.

General Considerations and Limitations

Consider the following immutability limitations:

• The maximum immutability period you can set in the Veeam Backup & Replication UI is 90 days. If you want to set immutability to a longer period, use one of the following Veeam PowerShell cmdlets: Set-VBRAmazonS3CompatibleRepository, Add-VBRAmazonS3CompatibleRepository, Set-VBRAzureBlobRepository.
• Immutable data is preserved as described in Block Generation.

• We recommend that you do not set the immutability period longer than the retention policy of the backup job, otherwise it will result in extra charges.

Amazon S3 Immutability Limitations

Consider the following immutability limitations for Amazon S3:

• After you have created an S3 bucket with Object Lock enabled, check that the default retention is disabled.

The default retention may result in an unpredictable system behavior and data loss. However, note that Veeam Backup & Replication will use Compliance object lock mode for each uploaded object. For more information on the retention modes, see AWS documentation. For more information on how to disable retention settings for S3 bucket, see AWS documentation.

• After you have added the buckets to the backup infrastructure, you must NOT enable or disable Versioning and Object Lock as it may lead to unpredictable system behavior and data loss.
• If you plan to use the immutability feature with the existing S3 bucket containing backups created by 9.5 Update 4, keep in mind that both Versioning and Object Lock must be enabled on the bucket simultaneously and immediately before enabling the immutability feature. Any other approach will lead to backup offload failures and inability to correctly interact with backups in the bucket.

Azure Blob Storage Immutability Limitations

Consider the following immutability limitations for Azure Blob Storage:

• Make sure that the Azure Blob storage settings meet the following requirements: when you configure an Azure storage account and an Azure container:

• When you create a storage account, make sure you enable versioning for blobs.
• When you create a storage account, do NOT enable version-level immutability. By default, this option is enabled and you must disable it. For more information, see Microsoft Docs.
• When you create a container, you must enable version-level immutability. For more information, see Microsoft Docs.
• The default retention is disabled. For more information on how to disable retention settings for Azure container, see Microsoft Docs.

• The default immutability policies are not supported.
• Do NOT enable immutability for already existing containers in the Azure portal. Otherwise, Veeam Backup & Replication will not be able to process these containers properly and it may result in data loss.

• Version-level immutability support for Azure storage accounts is not supported.

Veeam Data Cloud Vault Limitations

Consider the following immutability limitations for Veeam Data Cloud Vault:

• Immutability is enabled by default for Veeam Data Cloud Vault and you cannot disable it.
• Veeam Data Cloud Vault does not support immutability for Veeam Agents that use direct connection to transfer data to object storage repositories.