



There are some additional permissions for the IAM policy (covered below) required in order to take advantage of immutability.You can have a repository that takes advantage of both of these new features, however, because of the object lock limitation on buckets (cannot be changed after the fact), you are still going to need a new repository (S3 bucket).You will need to create a new S3 bucket to store immutable backups, and then create a new repository in Zerto. You cannot enable S3 Object Lock on an existing S3 bucket.While tiering doesn’t require any additional configuration, here are some things you’re going to need to know if you plan on using Zerto’s immutability feature with or without tiering: Customers can now specify whether or not they would like to enable immutability, which offers better protection from data either being deleted or otherwise compromised after it has been written. With Ransomware attacks continuing to rise (150% increase in 2020), the need to protect backup data via immutability becomes more important than ever. Retention Set Immutability via Amazon S3 Object Lock There are no additional configuration changes required to take advantage of this new feature. If you are upgrading from a previous version, tiering will not be enabled by default, so you’ll need to enable it on an existing Amazon S3 repository, or create a new one. The new feature is enabled by default in a fresh install. Now, when Zerto customers are backing up to Amazon S3, they can take advantage of better pricing as data ages, reducing cost and enabling more efficient use of storage. Here is what it looks like when creating a repository in Zerto: The first enhancement I want to cover here is automatic tiering of retention sets after they’ve aged, meaning Zerto will automatically move backup data from Amazon S3 Standard to Amazon S3 Standard-Infrequent Access, and then again (if desired) to Amazon S3 Glacier. Update: The latest version of the published document I wrote to accommodate this blog post titled “Deploy & Configure Zerto Long-term Retention for Amazon S3” can be found here: Īuto-Tiering for Data Backed up to Amazon S3 I will also update this post with a link to the updated document once it becomes available. While there are many new enhancements that I’m not going to cover here, this blog is specifically related to the changes made to the product to bring even more value, cost savings, and security to Amazon S3 repositories used with Zerto’s Long-term Retention (Backup).Īlong with these changes, you can sure expect an updated technical document that will cover all the steps and requirements (in detail) to take advantage of the new features. Zerto 9.0 went GA on July 13, 2021, and the official launch webinar was today (July 29, 2021), but if you missed it, you can head to the following URL and register to watch it on-demand:
