This report helps you to assess VMs readiness for performing backup with Veeam Backup & Replication.
The report analyzes configuration of VMs in your virtual environment, and shows potential issues and possible limitations that could cause backup process to fail or prevent VMs from being properly backed up.
|
This report is available for VMware vSphere environments only. |
The report takes into account the following criteria when analyzing VM configuration:
VMware CBT
Criterion | Description |
Existing Snapshots | The report analyzes your virtual infrastructure to find VMs with existing snapshots. To use VMware Changed Block Tracking for incremental backup, all existing snapshots should be removed. |
Hardware Version 4 or earlier | The report analyzes your virtual infrastructure to find VMs with hardware version 4 or earlier. To use VMware Changed Block Tracking for incremental backup, hardware version of VMs should be 7 or later. |
Virtual Disks
Criterion | Description |
VMs with Independent Disks | The report analyzes your virtual infrastructure to find VMs with independent virtual disks. Veeam Backup & Replication does not support independent disks; these disks are skipped from processing automatically. |
Virtual Machines with 2 TB virtual disks that are not running in vSphere 5.5 cannot be snapshotted and backed up | The report analyzes your virtual infrastructure to find VMs with 2 TB virtual disk size. For ESXi 5.0, 5.1 and 5.5, the maximum virtual disk (VMDK) size for snapshot operations is limited to 1.984492366201720 TB. For more information, see the VMware KB article. |
VMs with disks engaged in SCSI bus sharing | The report analyzes your virtual infrastructure to find VMs that use SCSI bus-sharing. VMware does not support taking snapshots of Microsoft Clustering Services (MSCS) VMs. For more information, see the VMware KB article. |
Application-Aware Image Processing
Criterion | Description |
VMware Tools Not Running | The report analyzes your virtual infrastructure to find VMs that do not have with VMware Tools installed or running. To enable backup with application-aware image processing, it is required that guest OS running inside your VMs have VMware Tools installed and running. |
Datastore Free Space
Criterion | Description |
VMs on datastores with 10% of free space | The report analyzes your virtual infrastructure to find datastores that have less than 10% of free space. When Veeam Backup & Replication backs up a VM, it triggers a VMware snapshot that is normally stored next to VM files on the source datastore. To eliminate the problem of datastores running low on free space during backup, it is required that the free space is more than 10%. |
Others
Criterion | Description |
Unsupported VM names | The report analyzes your virtual infrastructure to find VMs with names that contain the following symbols: @ / \ < >. Veeam Backup & Replication does not process VMs with names that contain mentioned symbols. If you want to back up these virtual machines, you must rename them. |
Use Case
This report allows you to obtain a list of VMs in your virtual environment that could experience potential issues with backups, and to get guidance on how to resolve these issues.
Report Parameters
Scope (VI): defines a virtual infrastructure level and its sub-components to analyze in the report.
vCD object(s): defines Virtual Cloud Director components to analyze in the report.
Business View object(s): defines Business View groups to analyze in the report. The parameter options are limited to objects of the “Virtual Machine” type.
Issues: defines VM assessment criteria to include in the report.
Skip backup replicas: defines whether to include Veeam Backup & Replication replicas in the report.
