6/4/2023 0 Comments Backblaze veeamPlease refer to the Veeam Documentation for migrating existing Object Repositories.įor further questions about the best path of migration for existing backups, please reach out to your Veeam support representative. These guides go over how to implement Wasabi with Veeam Immutable Repository from scratch. NOTE: There are multiple ways to integrate Object Lock into your existing Veeam Backup and Replication strategy. Wasabi's Veeam Object Lock Integration FAQ Veeam version 12 introduces immutability support for NAS/File Backups. NAS/File Backups are not supported with Object Lock on v10 and v11.Do not use Wasabi Object Lock Bucket Level Default settings (these are off by default).Veeam only supports Compliance Mode with Object Lock.Please reference the Veeam Documentation on Block Generation for more information.Īdditionally, please review the Considerations and Limitations for Immutability. Veeam uses a Block Generation strategy to determine the appropriate immutability expiration on objects, in order to ensure that full backups and incremental backups have the same immutability expiration time. When Veeam runs the offload process for a particular job, Veeam will upload the files and automatically set the immutability expiration for those objects. The process by which you enable Immutability is the same for both a Backup Job and a Backup Copy Job. Wasabi introduced Object Lock API support, in order to be compatible with Veeam. Veeam Backup & Replication v10, v11 and v12 have been tested by Wasabi to validate Veeam's immutability feature. Wasabi has obtained Object Storage with Immutability status in the Veeam Ready Program.
0 Comments
Leave a Reply. |