Greetings friends, we are approaching the last entries of this interesting series on how to protect the VMs using SLA policies, we have seen previously from the beginning of how to raise this protection system and to begin to create them in vSphere, how to create the policies in Veeam Backup & Replication, to assign the vSphere tags to the VMs that we want to protect and a very useful basic report for the administrators of each application.Today we are going to see in detail, how the Backup Infrastructure Administrators don't get their fingers caught in the resources, and how to create reports that help them understand which environment is busiest.

Veeam ONE Heatmap - A quick look at how busy our environment is

One of the best bird's eye views we have is the one called HEATMAP, which can be found in Veeam ONE Reports, in the Dashboards section. With a simple glance we can see that it is in amber or red, besides being able to see it by each component of the Infrastructure:

Greetings friends, we arrive at the fourth installment of this interesting series that you are enjoying very much. We have already seen in previous posts all that is needed to deploy backups using SLA policies, and it is now time to generate different reports and different views so that the different owners and managers of each application can know if their VMs are protected.

Using the Veeam Enterprise Manager Plugin with VMware vSphere Client (HTML5)

More than a year ago I wrote about how you could install the Veeam Enterprise Manager plugin on our VCSA to display information on the vSphere Web Client, and on the new vSphere Client (HTML5).Starting from the fact that we have already followed these simple steps, or if we were absent-minded, here is a screenshot where it is shown in a quick way:

Greetings friends, we come to the third entry on this interesting topic on how to protect a vSphere environment using Veeam Backup & Replication with SLA policies, we have seen in previous entries, how to design and create SLA policies in vSphere, and how to create the entire Veeam Backup & Replication infrastructure, today we will see how the owners or managers of each department can assign the policies to their workloads.

Create or Edit Roles in VMware vSphere

The first thing we will have to do is to grant the role of vSphere Tagging to the role that the different users or responsible of the workloads are using, for example, I have a very limited role, that only allows to do some operations in the VMs, and to this role, I have added the following permission:

Greetings friends, I already told you in the previous post about how to deploy a backup system using SLA policies, and in that first post, the first steps were mentioned, especially creating the SLA architecture and policies in VMware as vSphere Tags.In this second entry, we're going to see how to create the Veeam architecture we mentioned in the first post, something similar to the following:

Greetings friends, for a long time I have found in more and more places the need of IT Departments to offer the backup as a service internally to the rest of the departments.This means that the IT and Backup managers create the entire infrastructure and backup possibilities, and it is the different managers of each application or group of applications who are responsible.

Create an SLA policy plan according to our business

The first thing we will have to do is sit down and create these SLA plans, according to the needs and obligations of our company. For example, let's imagine that we have three different levels of protection for our environment.