VM does not meet the requirements for storage snapshot based jobs

Before You Begin

Review the following tasks and documentation:

• Rescan the vCenter.
• Rescan the Storage System.
• Review the Backup from Storage Snapshot Prerequisites.
• Review the VMware Integration documentation.
• Review the requirements and limitations documentation:
  • General Requirements and Limitations
  • Kerberos Authentication for Storage Systems
  • Cisco HyperFlex Requirements and Limitations
  • Dell VNXe, VNX, SC Limitations
  • NetApp Data ONTAP/Lenovo Thinksystem DM Limitations

Scenarios and Solutions

The section below is divided into subsections based on the ending of the error message. Identify the ending of the error you are encountering, then review the corresponding subsection for potential scenarios and solutions.

This section was created based on previous support cases and may only cover some possible scenarios and solutions. If you have encountered a scenario and solution not included here and resolved it, please send  KB feedback with the details and the associated support case number.

its virtual disks are not located on supported storage

• The VM is encrypted, and backup from storage snapshots cannot be used to back up encrypted VMs.
• If the issue is isolated to a new datastore that was recently added, rescan the vCenter from within the Veeam Backup & Replication Console to force update the configuration database with information about the new datastore.
• The NetApp .snapshot directory has not been made visible. Review NetApp NFS volumes and Veeam — configuration best practices to get you started for more information.
• The Storage System associated with the VM has been added to Veeam Backup & Replication, but the vCenter or ESXi host has not been added to Veeam Backup & Replication. Per the user guide, You must add to the backup infrastructure vCenter Server or ESXi hosts with VMs whose disks are hosted on the storage system.
• If using a MetroCluster and running Veeam Backup & Replication 12 GA or P20230223, upgrade to the latest Veeam Backup & Replication 12 release.
  A fix was included in Veeam Backup & Replication 12 P20230412 that corrected an issue documented in the initial version 12 GA release notes: "During the rescan of NetApp MetroCluster systems, target SVMs in an inactive state fail to be scanned. That results in integration failing for those systems. Only affects environments with newly added MetroCluster systems to Veeam Backup & Replication or new SVMs added to MetroCluster after the upgrade to Veeam Backup & Replication 12. Existing unchanged installations are not affected."

its files are located on datastore with multiple extents

• The VM is located on a datastore with multiple extents backing it, and you cannot perform a snapshot-only backup of VMs residing on a VMware datastore that comprises several extents. Check the datastore's 'Device Backing' in the vSphere client.

not all VM disks can be processed using storage snapshots as a source

• Rescan of ONTAP storage results in error:
  

  Failed to rescan ONTAP storage <name> Error: Api lun-get-iter failed:
  Reason: Node <node_name> has not finished the cluster create/join process.
  

  This error appears to be related to:
  • https://kb.netapp.com/onprem/ontap/os/Cluster_join_is_not_complete
  • https://kb.netapp.com/onprem/ontap/os/Api_call_export-policy-get-iter_failed_due_to_incomplete_cluster_join
• One or more VM disks are located on a volume that has been excluded from scanning when the Storage System was added to Veeam Backup & Replication.
  Note: The ability to specify which volumes should be scanned is only available for some storage systems.
• Veeam Backup & Replication is unaware of a recently created volume, rescan both the storage system and the vCenter.