Getting started with object storage

We heard a lot about object storage during the Veeam Backup & Replication v12 launch event. Although support for object storage is not new to the Veeam Data Platform, the ability to utilize it as a primary landing zone for backups is new in V12. Even though the list of new features and enhancements is astonishingly long for our latest release, anticipation around this capability has been a part of almost every conversation regarding V12.

Object storage is a hot topic for many IT departments, and rightfully so. It brings many benefits to organizations in a streamlined, easy-to-use fashion. At the top of the list for many IT professionals are the “three abilities”: immutability, scalability and durability. Because of the immediate impact to an organization’s security posture, immutability is likely first and foremost in many customers’ minds. With V12, it can be enabled by simply checking a box during a backup repository setup.

This isn’t restricted to a single location, either. For example, direct-to-object storage can be a part of traditional backup repositories backed by on-premises storage. Similarly, on-premises object storage can be used in the performance tier of a Scale-out Backup Repository (SOBR), or even from a public cloud — whether it’s offered by a partner or a Veeam Service Provider.


Adding your first object storage repository

If you have not worked with object storage yet, the process for adding an object-storage-backed repository is essentially the same as traditional methods: Start by going to Backup Infrastructure à Backup Repositories à Add Repository à Object Storage:

On the next screen, you’ll get a glimpse of the breadth of object storage solutions that Veeam Backup & Replication supports. If you have an account with any of the partners listed, you can select them from the list. In my case, I will be using storage from Object First, so I will go with S3 Compatible.

Tip: If you are not the storage admin, be sure to reach out to obtain service point, region and access credential information from the team responsible.

Selecting an option will launch the New Object Storage Repository wizard. Like other repositories, the first step will be to assign a name for the repository, along with enabling a limit on concurrent tasks, if you choose to do so.

The next step will be to enter the service point, which can be a host with a resolvable DNS name or an IP address. Additionally, you’ll need to enter the region where the storage is located, as well as select the credentials required to access it. If you need to set up new credentials, you can click on the “Add” button to add these details.

Once your connection details are in place, hit Next to select which bucket you would like to use, followed by which folder within that bucket. Something you may have noticed in the screenshot: Based on the names, some buckets are immutable, while others may not be. You will want to make sure you work with your storage teams to understand where immutability is or is not enabled. Additionally, make sure you do the math! The last thing you want is to consume large amounts of storage for an unneeded period of time, incurring costs and being unable to reduce consumption footprint.

From here on out, the wizard’s remaining steps will be very familiar to Veeam Backup & Replication users. The process is relatively self-explanatory.


Adding object storage to a Scale-out Backup Repository

SOBRs can now take advantage of direct-to-object storage as well. Configuration is straightforward in that object-storage-backed repositories can be used in the Performance Tier. As part of the configuration, you can easily set thresholds to move backups older than the period you choose to another repository.

The great thing about using object storage as part of a SOBR is that you can precisely obtain the granularity required to fit your needs. For example, if you want your Performance Tier to be backed by immutable storage for a set number of days and then moved off to mutable storage, that’s possible. The same is true if you want all locations to be immutable, or only the Capacity Tier or Archive Tier. This level of flexibility allows you to choose a strategy that best fits your workload. Just be sure your plan adheres to best practices when it comes to keeping your data cyber-resilient.


What’s next?

Object storage is another tool in the IT professional’s toolbelt. Whether you are looking for immutability, scalability or durability, object storage brings with it many benefits. Object storage, coupled with the fact that Veeam Data Platform supports it as a target in a variety of fashions, makes this V12 addition particularly powerful.

So, what sorts of backup jobs can take advantage of this enhancement? Well, the list is quite extensive:

  • Backup copy jobs for database log files (Microsoft SQL, Oracle and PostgreSQL)
  • Network-attached storage (NAS)
  • Veeam Agent for AIX
  • Veeam Agent for Linux
  • Veeam Agent for Mac
  • Veeam Agent for Microsoft Windows
  • Veeam Agent for Solaris
  • Virtual machines (VMware, Hyper-V, AHV, RHV)
  • Veeam Backup & Replication configuration backup (not supported with immutability)

As you can see, there is immense power and flexibility when it comes to object storage in the Veeam Data Platform. So, take the time to plan and implement the best strategy for you and your organization.

If you haven’t had a chance yet to experience the V12 launch event, or even if you want to watch it again, be sure to check out the replay. Additionally, if you want to try out Veeam Data Platform, you can download a trial with a 30-day license.

Similar Blog Posts
Business | March 5, 2024
Technical | February 5, 2024
Business | December 7, 2023
Stay up to date on the latest tips and news
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam’s Privacy Policy
You're all set!
Watch your inbox for our weekly blog updates.
Veeam Data Platform
Free trial
Veeam Data Platform
We Keep Your Business Running