Hello,
We are a cloud service provider, and we are currently testing immutability on our infrastructure with the goal of enabling it for all our clients.
We mainly use backup copy jobs for the second copy. The issue with using backup copy jobs with immutability is that, regardless of the immutability period configured on the S3 repository, immutability will apply for the entire GFS retention period. If a client terminates their service, we would still retain their backups for 12 months (we use S3 compliance mode), which is unacceptable for us.
Therefore, we plan to deploy new SOBRs with a capacity tier (copy policy). Immutability will be enabled only on the capacity tier. This would allow us to enable immutability for all our clients without having to worry about retaining immutable data after a potential service termination, since GFS retentions in the capacity tier are not affected by short immutability periods.
During my tests, I noticed something: even though the performance tier is not immutable, it is not possible to delete a backup from the performance tier (via the Veeam console) before the immutability period of the capacity tier has expired.
What is the technical explanation for why we must retain the backup in the performance tier until the end of the immutability period?
Thank you in advance,
Alexandre
We are a cloud service provider, and we are currently testing immutability on our infrastructure with the goal of enabling it for all our clients.
We mainly use backup copy jobs for the second copy. The issue with using backup copy jobs with immutability is that, regardless of the immutability period configured on the S3 repository, immutability will apply for the entire GFS retention period. If a client terminates their service, we would still retain their backups for 12 months (we use S3 compliance mode), which is unacceptable for us.
Therefore, we plan to deploy new SOBRs with a capacity tier (copy policy). Immutability will be enabled only on the capacity tier. This would allow us to enable immutability for all our clients without having to worry about retaining immutable data after a potential service termination, since GFS retentions in the capacity tier are not affected by short immutability periods.
During my tests, I noticed something: even though the performance tier is not immutable, it is not possible to delete a backup from the performance tier (via the Veeam console) before the immutability period of the capacity tier has expired.
What is the technical explanation for why we must retain the backup in the performance tier until the end of the immutability period?
Thank you in advance,
Alexandre
Statistics: Posted by AlexandreD — Jun 24, 2025 12:49 pm
