• 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 – Quick overview to the Capacity Tier Offload task

15th May 2019 - Written in: veeam

Greetings friends, we have already seen during this series how to configure our Capacity/Cloud tier, the configuration within Veeam, in Microsoft Azure and of course a brief introduction to why use this new technology to store our oldest backups.

Today I leave you some aspects that will help you to better understand the Capacity Tier process, how to launch it manually, etc.

How often does Scale-out Backup Repository Offload run?

The Scale-out Backup Repository offload task runs automatically every four hours, once we have configured our Capacity Tier, as we saw in the previous entry.

This means that once we have configured everything, after four hours we will check if any of the files comply:

  • The age selected in the Capacity Tier option
  • It’s a closed chain.
  • The override option has been selected if a certain % of use is reached in the Performance Tier

This Scale-out Offload process will run indefinitely every four hours.

How to force Scale-Out Backup Repository Offload

If this job every four hours is not enough, or if we just want to launch the task manually from time to time, we can go to our Veeam Console, Backup Repositories, select our Scale-Out Backup Repository where we want to run the offload and press CTRL + RIGHT BUTTON and this menu will appear with the secret option:This will launch the task manually, and if any of the files in the Performance Tier meet the requirements to be uploaded to the cloud, so be it.

How to force the offload of a certain string of backups

If you don’t want to send all the strings and files in a Backup Repository, but want to upload that backup string that weighs several TB, we can go to Home – Backup or Backup Copy, select the string we want and right click – properties:

And then select the string we want to upload to Object Storage and right click and select the option presented to us to specifically send this string to Object Storage:

Viewing the task of Scale-out Backup Repository Offload Tier

The visualization of the offload task is very similar to that of Backup or Replica that we are used to, we can see the progress, the transfer, the files that are uploaded, the number of objects and percentage:

Email notification of Scale-out Backup Repository offload tasks

We will receive a daily email with the tasks that have been completed from the offload tier, we will be able to see something similar to this:

  • The name of the Scale-out Backup Repository
  • The status of the task
  • The space used in Performance Tier and Capacity Tier, as well as the boundary in it

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