Veeam Backup for Microsoft Office 365: An object storage decision guide

Its getting hot … and cheap !

Welcome back after a longer break since the last blogpost.
Meanwhile I`m one of the main responsible german counterparts for Veeam Backup for Microsoft Office 365. Over the last month I saw a lot of different environments with various challenges, while there is a big transformation from on-premise repositories to object storage as well.
Today I want to share my experience with the community.
Whenever I`m involved in bigger projects, at some point in time we have a price discussion about repository costs with the customer. With the flexibility in Veeam you can choose whatever you want as a repository. There is no „vendor lock-in“ or any risk in loosing data if you want to change f.e the backup software in future.
For sure there are some pros & cons when you are choosing your object storage repository. So let me start what you need to consider and why:


  • Size (always matters 😉):
    Your very first step to start your decision journey: Please use our calculator to figure out how much capacity you need for backing up your data:
  • Price :
    Some vendors offer different pricings depending on the needed repository space. The price will be charged on a monthly basis and depends on the GBs you store. But there is a huge difference between vendors, country and additional costs. You will get the pricing information on the providers website. (Or check out our pricing calculator
  • Additional costs:
    Whenever we are using object storage in the cloud there are a lot of ingress/egress/API-calls and a lot of providers will charge them extra. Dont be afraid! we are NOT talking about 1000 of dollars. But you also can`t neglect them. There are some vendors without additional API billing to keep it as simple and transparent for you as possible. But sometimes they can be more expensive.
    There also exists transfercosts (f.e. If you run your VBO-environment i.e. in Microsoft Azure and you are using your object storage on AWS the transfer-costs from the VM will be charged additonally.
    When you are using Azure VM with Blob, or AWS EC2 with S3 within the same datacenter no additional transfer costs will be charged.
  • Performance:
    The performance part is not that important when we look into object storage. Our data flow (VBO) is through a local cache which should be a fast (SSD) disk. The object storage is the secondary tier and will receive the data from the local chache. So there is no need to use a „hot“ storage. You can use a cold storage with infrequent access. Archive-repositories are not supported as a primary  target.
  • Archive:
    We introduced our new archive feature for version 6 (Beta will come soon). This archive tier can be used as a secondary target for long term retention copys. Not all vendors do offer an archive storage and for sure it must be supported also from Veeam side. Please consider this in your decision.
  • Connection:
    The connection of an object storage or their providers can be ignored. If we see a bottlneck, it`s mostly the customers WAN link or the throttling when we are backing up data through the Microsoft-API.  

Its getting hot

Wasabi ( is one of my favorit object storage providers because they fulfill nearly each of my requirements with a very easy and good pricing.

DISCLAIMER: This is a private blog and this is an unpaid advertising ! I just like products with an easy to use and reliable approach … like Veeam 😉

Wasabi has a „flat rate“ pricing : $5.99 per TB/month . Each started TB will be charged completely.
There are NO additonal API-Call costs or any other hidden costs. 5.99$ and everything is included. You can make your pricing comparision by your own:
Start with a free trial – 1 TB space for 30 days. You can extend this trial by contacting their support if you need more time for testing.

Wasabi setup guide

Here is a short walk through how to setup:

  • Login to wasabi:
  • Go to Buckets an klick on „create bucket“
    • Select bucket name and region
    • Click „Create bucket“
  • Go to Access Keys
    • Click „Create new access key“ (root user)
    • Download CSV or copy Access key
  • Go to Veeam Backup for Microsoft Office 365 -> Backup Infrastructure
  • Click on Object Storage Repositories and add a new repository
  • Type a name
  • Select „S3 Compatible“
  • Enter the Servicepoint adress. You can find the wasabi Servicepoints here: (depending on location you selected when created the bucket). Enter the right date center region ! And add your access key + secret key from the downloaded CSV-File or your clipboard when we created the bucket.
    The format of the CSV is „ ,ACCESSKEY,SECRETKEY „
  • Define the folder where you want to store your backupdata. In bigger environments it make sense to create different folders for different Services (Mail, Onedrive, Sharepoint etc.) or different Jobs. When you create a seperate repository folder for each service, it is necessary to add an own caching folder !
  • Go to Backup Repositorys and create the Cache-repository:
  • Define a name and select the path where the cache folder should be placed
  • Check „Offload backup data to object storage“ and select your wasabi repository. If you want you can additional add object storage encryption by entering a password (DO NOT LOOSE IT !)
  • Select your prefered retention and click finish

    Now you are ready to point your backupjobs to the new repository and start testing your wasabi object storage!
    Enjoy you new hot object storage!

1 thought on “Veeam Backup for Microsoft Office 365: An object storage decision guide”

  1. Whats your take on configure azureblobs. Would you recomend a seperate blob for each service? (Exchange, SP, OD, Teams?) for easy to controll size growth

Leave a Comment

Your email address will not be published. Required fields are marked *