Protected VMs

This report analyzes backup protection of VMs in your virtual environment.

A VM is considered to be Protected if there is at least one valid backup or replica restore point that meets the designated RPO for it. A VM is considered to be Unprotected if it has an outdated or missing backup or replica restore points.

The report examines whether VMs have valid backup and replica restore points created within the specified time range (RPO period), shows the total number of restore points available for each protected VM, and provides information on the completion status of recent backup and replication job sessions.

The report helps you identify which VMs in your environment function without proper protection and make sure the existing backups and replicas meet established RPO requirements.


  • VM replicas protected by any Veeam Backup & Replication job are not accounted in this report. For example, if you protect a VM replica with a backup job, this replica will not be considered a backed up VM in the report.
  • Infrastructure topology view in Veeam ONE and Veeam Backup & Replication must match. Otherwise, Veeam ONE Reporter might show invalid data for Veeam Backup & Replication reports and dashboards.

Protected VMs Report
Protected VMs Report
Protected VMs Report

Use Case

When you set up your backup, replication and backup copy jobs based on VI containers (such as folders, hosts or datastores) or employ complex exclusion parameters in job properties, some VMs may turn out to be excluded from the containers and therefore will lack proper protection.

This report displays a list of VMs protected by up-to-date backups and replicas, as well as a list of unprotected VMs which have outdated or missing backup or replicas. This information helps you validate the state of backup protection in your organization.

Report Based on

To create the report, Veeam ONE Reporter retrieves and analyses data from the following sources:

  • Historical data on backup, backup copy job, and replication sessions for the specified RPO period (gathered from Veeam Backup & Replication servers)
  • List of VMs in virtual inventory (gathered from VMware vSphere, Microsoft Hyper-V management servers and vCloud Director)

Report Parameters

You can specify the following report parameters:

  • Scope (VMware VM folders): defines a list of VMware folders to include in the report (applies to VMware vSphere environments only). VM folders view is an alternate way to present the virtual infrastructure. If VMs in your infrastructure are grouped into folders according to their profile, you can limit the report scope by specifying the necessary folders only.
  • Scope (VI): defines a virtual infrastructure level and its sub-components to analyze in the report.
  • vCloud Director: defines vCloud Director components to analyze in the report.
  • Business View objects: defines Veeam ONE Business View groups to analyze in the report. The parameter options are limited to objects of the Virtual Machine type.
  • RPO (Recovery Point Objective): defines the maximum amount of data that you may accept to lose, expressed in time. RPO defines the age of the latest backup or replica files required to resume normal operation if system failure occurs. For example, to compile a list of VMs protected on a daily basis, you need to set the RPO value to 1 day.
  • Exclusion mask: defines a list of VMs that should be excluded from the report scope. You can enter VM names explicitly or create a wildcard mask by using the asterisk (*) to replace any number of characters. Multiple entries are separated by semicolon. Usage example: the following string will exclude machines with the _R&D suffix from appearing in the report: “*_R&D”.
  • Job type: defines a job type to evaluate in the report (Backup jobs, Replication jobs, Backup Copy jobs, All items).
  • Include VM templates in this report: defines whether VM templates should be included in the report.
  • Exclude Jobs: defines a list of backup and replication jobs to exclude from the report.
I want to report a typo

There is a misspelling right here:


I want to let the Veeam Documentation Team know about that.