The business categorisation feature available in Veeam ONE offers a solution for managing and organising virtual machines (VMs) within virtualised infrastructures, such as stretched cluster environments. By leveraging the underlying ESXi host information, this feature allows IT administrators to create a seamless and dynamic approach to VM management, ensuring optimal backup and recovery strategies.
In a stretched cluster scenario, where VMs can move between different data centres for improved availability and disaster recovery capabilities, the ability to group VMs based on their current location can be quite important. For example, if there is a need to ensure transient VMs are protected to a local backup repository.
Leveraging Veeam ONE’s business categorisation means we can tag VMs according to the specific ESXi host they are running on. Tags can then be configured as the source for a Veeam backup job.
Step 1. Create the category,
Step 2. Pick ‘Grouping expression’ as the Categorisation method.
During a recent Veeam ONE deployment I configured Veeam Intelligent Diagnostics (VID), a great feature that was introduced in Veeam ONE v9.5 Update 4. VID allows Veeam ONE to automatically detect known issues in the configuration and performance of Veeam backup infrastructure. It does this by parsing logs from Veeam Backup & Replication servers, analyses the logs against a known list of issue signatures and triggers an alarm with detailed information about what the issue is, and how it can be fixed.
I recently experienced an issue while deploying Veeam ONE, all backup proxy servers were failing to display CPU/Memory statistics with the following error, “Failed to collect performance data for object %servername%. The RPC Server is unavailable. (Exception from HRESULT: 0x800706BA)”.
One of the lesser known features of Veeam ONE is its ability to divide the virtual environment into various groupings and categories, essentially creating a view that is easier to digest from a business standpoint. This view can be valuable when you consider that most tools we would use such as vSphere client or SCVMM/Failover Cluster Manager are often configured to present information and data, for say, a more a technical perspective, something which might not be relevant or even make a whole lot of sense for all business stakeholders.
Both Veeam ONE Monitor and Veeam ONE Reporter will use this categorization provided by Business View. Veeam ONE Reporter, enables us to generate reports and build dashboards based on the categorisation created in Veeam ONE Business View. While Veeam ONE Monitor, we can monitor Veeam ONE Business View groups of VMs, hosts, clusters and storage objects.
By leveraging Veeam ONE Business View to group and categorise these objects into a hierarchy that makes more sense from a non-technical perspective such as office departments, projects, SLAs and much more we can easily review and report on resource allocation and utilisation based on these groupings.
Now that part is out of the way, I wanted to demonstrate how Veeam ONE Business View can be configured to help automate this process. We can configure set & forget rules and policies that organise objects into these group and categories. I’ve written this article to dive further into how one can configure Veeam ONE to categorise our infrastructure.
Did you know that Veeam ONE has a tool called deployment projects that has the ability to simulate how a task such as adding or evicting hosts and VMs impacts your virtual infrastructure? These simulations help us to review predicted resource capacities against future resource demand, provide practical recommendations and help identify potential resource shortages. It’s a quick and easy way to check your resources before making small or large changes. Think of it as a way to perform due diligence and gain insight before making any changes to your virtual environment.
Deployment Projects can be found under Veeam ONE Reporter, to access Veeam ONE Reporter we browse to the URL of the Veeam ONE Reporter website. This website runs on the machine where the Veeam ONE Web UI component is installed. Assuming you have are using the default port it would look similar to https://veeamoneip:1239