• Skip to main content
  • Skip to secondary menu
  • Skip to primary sidebar
The Blog of Jorge de la Cruz

The Blog of Jorge de la Cruz

Everything about VMware, Veeam, InfluxData, Grafana, Zimbra, etc.

  • Home
  • VMWARE
  • VEEAM
    • Veeam Content Recap 2021
    • Veeam v11a
      • Veeam Backup and Replication v11a
    • Veeam Backup for AWS
      • Veeam Backup for AWS v4
    • Veeam Backup for Azure
      • Veeam Backup for Azure v3
    • VeeamON 2021
      • Veeam Announces Support for Red Hat Enterprise Virtualization (RHEV/KVM)
      • Veeam announces enhancements for new versions of Veeam Backup for AWS v4/Azure v3/GVP v2
      • VBO v6 – Self-Service Portal and Native Integration with Azure Archive and AWS S3 Glacier
  • Grafana
    • Part I (Installing InfluxDB, Telegraf and Grafana on Ubuntu 20.04 LTS)
    • Part VIII (Monitoring Veeam using Veeam Enterprise Manager)
    • Part XII (Native Telegraf Plugin for vSphere)
    • Part XIII – Veeam Backup for Microsoft Office 365 v4
    • Part XIV – Veeam Availability Console
    • Part XV – IPMI Monitoring of our ESXi Hosts
    • Part XVI – Performance and Advanced Security of Veeam Backup for Microsoft Office 365
    • Part XVII – Showing Dashboards on Two Monitors Using Raspberry Pi 4
    • Part XIX (Monitoring Veeam with Enterprise Manager) Shell Script
    • Part XXII (Monitoring Cloudflare, include beautiful Maps)
    • Part XXIII (Monitoring WordPress with Jetpack RESTful API)
    • Part XXIV (Monitoring Veeam Backup for Microsoft Azure)
    • Part XXV (Monitoring Power Consumption)
    • Part XXVI (Monitoring Veeam Backup for Nutanix)
    • Part XXVII (Monitoring ReFS and XFS (block-cloning and reflink)
    • Part XXVIII (Monitoring HPE StoreOnce)
    • Part XXIX (Monitoring Pi-hole)
    • Part XXXI (Monitoring Unifi Protect)
    • Part XXXII (Monitoring Veeam ONE – experimental)
    • Part XXXIII (Monitoring NetApp ONTAP)
    • Part XXXIV (Monitoring Runecast)
  • Nutanix
  • ZIMBRA
  • PRTG
  • LINUX
  • MICROSOFT

Veeam: Cloud Tier/Capacity Tier in Microsoft Azure Blob – Introduction

12th May 2019 - Written in: veeam

Greetings friends, a few weeks ago we saw the new functionality included for free in the latest Veeam Availability Suite v9.5 Update 4, Cloud/Capacity Tier, which allows us to move our backups that are already in retention policy to the Cloud to save disk space.

Today I bring you the beginning of a series on Microsoft Azure Blob, and how to use this Cloud platform as one of the best candidates for this cloud storage of backup files.

Diagram of how it works

I would like to show you this diagram so that we understand the Veeam workflow between our local data center and Microsoft Azure Blob:

We already saw in the article about Cloud/Capacity Tier, that only backup files that no longer have dependencies are susceptible to be uploaded to the cloud, this means that there are no other files as they can be incremental, or synthetic full backups depending on them, in the cases of GFS is easier to understand, since the files are Full, so they can be uploaded directly.

System Requirements

In order to elaborate this procedure we will have to have ready all the following at software level:

  • A valid license of Veeam Backup & Replication v9.5U4 with Enterprise or Enterprise Plus.
  • A valid Microsoft Azure subscription to create VMs, Storage, Networking, etc.
  • Copy jobs that no longer have dependencies, closed job chains. This means GFS, or previous weeks where a syntethic or full has already been performed.

Comments about the process

Veeam’s Offload Tier process works like silk, automatically for files that are already closed and meet the age we select in the Capacity Tier.

If we have a line to the Internet not very powerful is likely that we want to control the bandwidth, for that I leave the following article:

  • Veeam: How to control the bandwidth in Veeam Cloud Tier when we send copies to AWS S3

The Offload Tier process puts metadata in the object storage repository, which always checks the chunks to be sent, and if they are already available in the object storage will only create a pointer to them, thus saving disk space and data transfer of course.

I would like to leave you the list of articles that we will see throughout the series:

  • Veeam: Cloud Tier/Capacity Tier in Microsoft Azure Blob – Introduction
  • Veeam: Cloud Tier/Capacity Tier in Microsoft Azure Blob – How to create a Microsoft Storage Account and Azure Blob
  • Veeam: Cloud Tier/Capacity Tier in Microsoft Azure Blob – How to configure a Veeam Backup & Replication Scale-Out Backup Repository
  • Veeam: Cloud Tier/Capacity Tier in Microsoft Azure Blob – Quick overview to the Capacity Tier Offload task
  • Veeam: Cloud Tier/Capacity Tier in Microsoft Azure Blob – Microsoft Azure Blob Monitoring with Veeam ONE
  • Veeam: Cloud Tier/Capacity Tier in Microsoft Azure Blob – Microsoft Azure Blob Monitoring with Azure Monitor and Grafana

Filed Under: veeam Tagged With: veeam, veeam azure, veeam backups to azure, veeam blob, veeam capacity tier azure, veeam cloud tier azure

Reader Interactions

Leave a Reply

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

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

Primary Sidebar

  • E-mail
  • GitHub
  • LinkedIn
  • RSS
  • Twitter
  • YouTube

Posts Calendar

May 2019
M T W T F S S
 12345
6789101112
13141516171819
20212223242526
2728293031  
« Apr   Jun »

Disclaimer

All opinions expressed on this site are my own and do not represent the opinions of any company I have worked with, am working with, or will be working with.

Copyright © 2025 · The Blog of Jorge de la Cruz