Home » Backup & Recovery » Wasabi S3 Veeam Repository in 3 easy steps

Wasabi S3 Veeam Repository in 3 easy steps

The process to setup Wasabi S3 Veeam Repository is a very simple and straight forward process. All the shopping list requires is working Veeam Backup & Replication server (any edition) and a valid trial from wasabi cloud which can be used for 30 days up to a 1 TB of storage. This is a follow up article for the first one covering the steps to create a wasabi trial along with a “bucket”. Actually this bucket will be used as a target for the Veeam Backup Repository leveraging the object store with “S3 format”.

Veeam Backup & Replication added this capability since version 9.5 update 4. In particular, it allows to extend the S.O.B.R. (Scale Out Backup Repository) to use object storage as well. It is a great advantage for companies extending their “on-premises” storage to virtually infinite space. Simply by  taking advantage of the cloud resources. In addition, Wasabi is making this offer very attractive also for low budgets with a very competitive pricing model.

Cloud object storage represents a valid and “modern” alternative to Tapes. Far from saying Tapes are dead. Surely the object storage has a long way to go. And at this rates, chances are Tapes might become a management of the past. Air-Gap vs. Immutable storage: it is definitely an interesting duel!

Veeam supports the latest “S3 signature V4” and so does Wasabi. This means it is possible to create S3 buckets in Wasabi and use them as target Backup Repositories. Ideally for long term retention.

 

Hot to setup Wasabi S3 Veeam Repository

From the Veeam VBR Console > Backup Infrastructure > Backup Repositories the wizard to create a new Repository. The choice is Object storage.

domalab.com wasabi S3 Veeam Repository

From the Object storage section in this case the S3 Compatible needs to be selected.

domalab.com wasabi S3 Veeam Repository

A new wizard is starting. First information to fill in would be the friendly name and a description for the Wasabi S3 Veeam Repository.

domalab.com wasabi S3 Veeam Repository

Next is to provide the Service Point and region Name. Both details are available when creating the Wasabi trial.  By default it points at the Data Centers in the US. The credentials will be created though the usual Veeam Cloud Credential Manager in the Veeam main Console.


When changing Service Point it is important it is matching the Region name as well. Again both info are available at the time of creating the account with Wasabi. In addition, it is also possible to specify the Veeam Gateway Server that will connect to the Wasabi Data Centers. Internet connectivity is required from the Veeam Gateway Server.

domalab.com wasabi S3 Veeam Repository

At this point when connection is successful will automatically show the existing buckets available. It allows to browse and eventually create the folder where the data and metadata folder structure will be created.

A quick window to explore the current folder structure.

Upon folder selection it is now time to review the main details and confirm before committing. Everything is now ready to add this Wasabi S3 Veeam Repository to a SOBR and extend the storage from on-premises to the cloud. More details on next article.

domalab.com wasabi S3 Veeam Repository

About the author

Michele Domanico

Passionate about Virtualization, Storage, Data Availability and Software Defined Data Center technologies. The aim of Domalab.com is sharing with the Community the knowledge and experience gained with customers, industry leaders and like minded peers. Always open to constructive feedback and new challenges.

2 Comments

Click here to post a comment

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Browse articles

September 2023
M T W T F S S
 123
45678910
11121314151617
18192021222324
252627282930  

Articles by Category

Archives

error: Content is protected !!
%d bloggers like this: