For those folks who’ve been in the continuing business of burning data for some time, we’re used to making copies of data on various kinds of media. I won’t date myself by mentioning reel-to-reel tapes, however the journey started with tape and burning data to block/file-based disk storage arrived then. More recently, a fresh kid on the market has turned into a popular destination for supported data, object storage.

Veeam began to use object storage as a target whenever we released Veeam Backup & Replication 9.5 Update 4 in January 2019 by introducing our usage of AWS S3 compliant object storage via the capability Tier. Year later a, we launched Veeam Backup & Replication v10 which featured support for object locking to supply data immutability for object storage. Immutability provides protection from ransomware attacks by locking the objects which prevents them from being modified or deleted by malicious software or humans. Today, Veeam Backup & Replication is protecting a huge selection of petabytes of customer data using object storage.

A crucial element of the success of our object storage capabilities are our Technology Alliance Partners. Amazon, Backblaze, Cloudian, Google, Hitachi, Microsoft Azure, Wasabi, and Zadara are a number of the object storage providers that Veeam has partnered with.

To greatly help our customers choose an object storage platform that is appropriate for Veeam Backup & Replication, Veeam includes a qualification program, Veeam Ready. For object storage, you can find two types of qualification:

• • Veeam Ready Object is for TAP Partners with S3-compatible object storage answers to test their compatibility with Veeam Backup & Replication object storage capabilities.

• • Veeam Ready Object Immutability can be an optional test that’s available for all those partners who support Veeam’s object immutability features. This qualification verifies compatibility with Veeam Backup & Replication implementation of S3 Object Lock abilities on object repositories, which really is a key feature for ransomware protection.

To find out more regarding these Veeam Ready tests and all of those other Veeam Ready program, please visit The Veeam Ready program for Veeam Alliance Partners .

An object storage repository is section of a Veeam Scale-out Backup Repository. Let’s have a look at what is had a need to add object storage to a Veeam Backup & Replication environment.

As you can see from the architecture slide above, you could have different repository types that define a Scale-out Backup Repository (SOBR). This technique can be created by us simple by following from left to right.

Adding object storage-backed Capacity Tier to your Veeam infrastructure includes a few simple steps.

1. 1. Create a number of repositories to act because the Performance Tier.

1. 1. Create an object storage repository to do something as Capacity Tier.

1. 1. Create you Scale-out Backup Repository and pick the repositories you created because the Performance Tier &amp just;} Capacity Tier extents.

That you have your brand-new SOBR created now, it is possible to point your backup jobs to the SOBR now.

The steps that people discussed are for a fresh SOBR just. What if you curently have a SOBR with existing backup jobs configured to utilize it? You can include a fresh Capacity Tier to your existing SOBR simply. When you do that, Veeam Backup & Replication will detect the prevailing backup file in your Performance Tier extent(s). You’ll then be asked if you wish to copy all existing backups to the capability Tier or just the most recent backup chains.

If you opt to copy all of the existing backups, every backup file within the prevailing Performance Tier extent(s) will undoubtedly be copied to the capability Tier. If you opt to copy the most recent backup chain, Veeam Backup & Replication shall copy the active backup chain and then the Capacity Tier.

I like to make reference to copying all existing backups as “historical offload” and the most recent as “non-historical offload.” When offloading all of the backups to the capability Tier, you need to make certain that your Veeam Backup & Replication infrastructure has enough resources to offload the info in the right timeframe that you require.

Veeam Backup & Replication runs on the “SOBR Offload” background task to copy and/or move the backup data to the capability Tier. The SOBR Offload background task uses “Repository Tasks” to transfer the info to the thing storage. When determining the real amount of Repository Tasks, you need to follow the sizing rule that 1 Repository Task = 1 CPU core. Each core must have 2 GB of RAM assigned to it.

As well as the SOBR Offload job(s), the Repository Task slots are employed by backup jobs, restore jobs and copy jobs. Veeam Backup & Replication allocates which job gets an available repository task once the job starts in addition to although it is running. This allocation is dependant on a precedence hierarchy. Restore jobs will be the highest priority job and the SOBR Offload gets the lowest priority. So, when you have the other job types running throughout your SOBR Offload window, the SOBR Offload job(s) might not get assigned enough repository slots to complete within your preferred timeframe.

Another factor to take into account when designing your usage of a Capacity Tier may be the amount of concurrent S3/BLOB operations connections that Veeam Backup & Replication shall use to transfer data to the capability Tier via the SOBR Offload jobs. Veeam’s default setting would be to have a maximum amount of 64 S3/BLOB operations per Repository Task slot. When working with on-prem object storage, we recommend keeping the utmost amount of parallel to be significantly less than 2048 which is attained by utilizing 32 Repository Task slots. For public cloud providers like AWS S3, Microsoft Azure BLOB and Google Cloud Storage, we recommend keeping the real amount of connections below 6016, which means utilizing around 94 Repository Task slots.

In Veeam Backup & Replication v11, we added a checkbox on the thing Storage Repository wizard that allows you to limit the amount of task slots which are used concurrently by the capability Tier.

You will easily limit the utmost amount of S3/BLOB operations concerning not overload the storage systems.

The target is to have your SOBR Offloads complete transferring data to the capability Tier prior to the next day’s SOBR Offload jobs start. The mix of determining the correct amount of Repository Task slots and calculating the right amount of S3/BLOB operations that the thing storage platform are designed for are fundamental to successful SOBR Offloads, because the storage is avoided by it from running into an overload situation with degraded performance and high latency.

Most customers shall discover that these default settings will continue to work right from the box. If you want to fine-tune with the aforementioned settings to suit your performance needs and generate the very best throughput making use of your object storage platform, there are always a true amount of great resources open to help you.

      Veeam’s official documentation site           is a superb source of information to greatly help together with your planning and configuration. Addititionally there is the           Veeam Best Practice Documentation           which are guidelines from field experiences.

And don’t forget to go to your object storage provider’s website for more information. Quite a few TAP partners have “Veeam landing pages” which are chock filled with guides, solution and videos briefs to assist you use their object storage with Veeam. Several great examples are: