Greetings friends, we have already seen in the previous posts that Veeam had launched Veeam Backup for Microsoft Azure Free Edition, the solution to protect workloads in Microsoft Azure without the need of agents. Also, and as we all like it, with a free version of up to 10 Instances. In addition, we have seen how to deploy it step by step, and its subsequent configuration as well, today we are going to see how to configure Veeam Backup & Replication to access the backups created by Veeam Backup for Microsoft Azure and stored in Azure Blob.If we look at the following diagram, we would be talking about points 5, 6, and 7:
Greetings friends, we have already seen in the previous entry that Veeam had launched Veeam Backup for Microsoft Azure Free Edition, the solution to protect workloads in Microsoft Azure without the need of agents. Also, and as we all like it, with a free version of up to 10 Instances. Besides, we have seen how to deploy it step by step, today we are going to see how to configure and create policies in Veeam Backup for Microsoft Azure.
Greetings friends, we have already seen in the previous entry that Veeam had launched Veeam Backup for Microsoft Azure Free Edition, the solution to protect workloads in Microsoft Azure without the need of agents. Also, and as we all like it, with a free version of up to 10 Instances. Let's see the step by step to deploy Veeam Backup for Microsoft Azure.
Deploy Veeam Backup for Microsoft Azure Free EditionBefore deploying Veeam Backup for Microsoft Azure Free Edition we will need to have several instances of Azure VM running, security groups created, VPC, etc. I guess we are interested in this solution and I consider all this done.We will go to the Microsoft Azure Marketplace and if we search "veeam" we will find the product, we will click on Create to continue:
Greetings friends Veeam has announced its free version for the protection of workloads in Azure, Veeam Backup for Azure, now available in the Azure Marketplace.
What is Veeam Backup for Azure Free Edition?Veeam Backup for Azure Free Edition is a native Azure VM workload protection solution. This means that Veeam snapshots the volumes of each instance and allows us to later launch a copy to a Blob Storage repository, for much longer retention.Veeam Backup for Azure Free Edition provides unlimited restores of any Veeam Backup for Azure, and allows backups of up to 10 Azure VMs. Veeam Backup for Azure provides secure, cost-effective, native cloud-based backup and recovery of Azure VM instances. Easily recover any data loss scenario in the cloud, whether due to disruption, accidental deletion, malware, and more, in minutes.
Greetings friends, a few weeks ago I was showing you everything we need to know about Veeam Backup for Microsoft Azure, in case you haven't been paying attention, I'm posting the blog series here (in Spanish):
- Veeam anuncia Veeam Backup for Azure Free Edition
- Cómo Desplegar Veeam Backup for Azure – paso a paso
- Vistazo en profundidad al nuevo Veeam Backup for Azure – Creación de Políticas de Backup y Restauración
- Cómo conectar nuestro Veeam Backup & Replication a Veeam Backup for Azure
Greetings friends, the series on Microsoft Azure Blob comes to its last post, I hope you liked it and you find it useful when selecting an Object Storage for your Veeam Backups.We still have this last entry about Microsoft Azure Blob monitoring with Grafana. Let's go to it, after we follow all the steps we will be able to have a result like this:
Greetings friends, we are in the penultimate post about this great series on Veeam Cloud/Capacity Tier in Microsoft Azure Blob, and today we are going to see how we can monitor this repository in our Veeam ONE.Veeam ONE, we can now monitor the size, and the information we have sent to our Object Storage Repositories, for this we will go to Veeam ONE Monitor, and in the Data Protection View - Backup Repositories - your Object Storage section, we can see the following: It is a fairly complete monitoring that will help us understand the consumption of this Repository, and monitor it in case it is in the cloud and we have a certain budget.If we also want to see the growth of this repository, predictions, etc, we can go to Reports and see the following.
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
Greetings friends, now that we have seen an introduction to this great series and have created the Microsoft Azure Blob, we can go to Veeam and create everything relevant to Cloud/Capacity tier.
Scale-Out Backup Repository - BasicsBefore we go any further, it is important that we understand what we intend to do. Cloud/Capacity Tier builds on Veeam's Scale-Out Backup Repository to combine Performance Tier and Capacity Tier.If we saw it in a very simple diagram, we would have the following, a combination of local extents (Backup Repositories) called Performance Tier, to which is added a Capacity Tier based on Object Storage to which are sent the copies we don't need to have in the performance tier:
Greetings friends, in the previous post we could see the introduction to this great series on Microsoft Azure Blob Storage, and how to send there our backups.In today's chapter we are going to see a comfortable step by step on how to create our container of Microsoft Azure Blob, for it before we will see a bit of theory.Before moving on to the content, I would like to show you the different components that make up Microsoft Azure Blob:
- Storage Account: It is in this component where we will have to select if we want the Storage Account to be General Purpose V1, v2 or Blob directly, as well as selecting if we want it to be Hot Tier or Cool Tier, finally in the Storage Account we can also select how we want Microsoft Azure to protect this account, with geo-distribution, or locally in the region, and so on.
- Container: In this component, which is a logical resource within a Storage Account, you can grant them access permissions, and make them public if you want.
- Blob: It will be the content that is inside the container, content that is specially prepared to store PB of information exposing a RESTfulAPI.