Leveraging the cloud and in particular object storage has transitioned from being simply desirable to a necessity. Infinite storage for On-Premises infrastructures it is now a reality. This article as part of the series dedicated to the wasabi cloud, covers the steps on how to create a wasabi cloud Veeam SOBR (Scale Out Backup Repository).
What’s a Veeam SOBR?
Since individual storage systems (think about DAS, SAN, Shares, Tapes, DeDupe..) can be seen as single point of failure when used on their own, Veeam has created the concept of SOBR which is a logical pool of multiple storage systems even different from each other. Should any of these extents (as part of the logical pool or group) fail or be full it does not affect the ability to perform backup and recovery jobs. Veeam SOBRs can be configured for different purposes and now have the ability to further extend to the cloud object storage. In this case this article refers how to create a wasabi cloud Veeam SOBR. It will serve to automatically move data to a different tier upon data aging.
Wasabi cloud Veeam SOBR setup
From the main Veeam Backup & Replication console (requires 9.5 update 4 or higher) and navigating to Backup Infrastructure > Scale Out Backup Repository the wizard to create one. First step is to add a name (possibly descriptive one) and a general description.
Next is populate the Performance Tier section with the local storage system available. This is the storage where the data for immediate restore and SLA requirements is sitting. For example with a 30 days retention on Disk or a SMB share, these are exactly the ones that should be added as the first or most performing tier.
In the advanced section for the Performance Tier it is possible to specify also how backup data will be written. Per-VM backup files is enabled by default for better performances. In addition, the option to select a Full Backup (on a separate extent) should the current one be offline.
The Veeam SOBR configuration allows to choose a Placement Policy based on Data Locality and Performance. Whereas the former will automatically use the same extent for Full and Incremental backups the latter gives the option to separate the Full from Incremental backup files.
When selecting the Performance Placement and the advanced option, it is also possible to dictacte which extent will hold the Full and or the Incremental backup files. For example Full backups could leverage a SATA storage whereas the Incremental (generally more frequent and smaller in size) can sit on a SSD or Flash Storage.
At this point it is possible to further extend the storage configuration by enabling the checkbox option in the Capacity Tier which will show the available and configured Repositories based on object storage. In this case a wasabi cloud Veeam SOBR.
In addition, it is possible to specify extra criteria when moving data to a different tier like reaching capacity limits on the “local storage”
At this point everything is ready to progress the wizard and save the current configuration. Next step is to use the wasabi cloud Veeam SOBR as target for the Backup or Backup Copy Jobs. Data will be stored on the local storage (extents) before getting moved based on data aging or local capacity criteria. Next article covers this in more detail.