NetBackup™ for VMware Administrator's Guide
- Introduction
- Required tasks: overview
- Configuring RBAC roles for VMware administrators
- Notes and prerequisites
- VMware vSphere privileges
- Managing VMware servers
- About VMware discovery
- Add VMware servers
- Change resource limits for VMware resource types
- Configuring backup policies for VMware
- Backup options on the VMware tab
- Exclude disks tab
- Configuring a VMware Intelligent Policy
- About the Reuse VM selection query results option
- Use Accelerator to back up virtual machines
- Configuring protection plans for VMware
- Malware scan
- Instant access
- Instant rollback
- Continuous data protection
- Backing up virtual machines
- VM recovery
- VMware agentless restore
- Restoring Individual files and folders from VMware backups
- Using NetBackup to back up Cloud Director environments
- Recover VMware Cloud Director virtual machines
- Restore virtual machines with Instant Recovery
- Protecting VMs using hardware snapshots and replication
- Best practices and more information
- Troubleshooting VMware operations
- NetBackup logging for VMware
- Snapshot error encountered (status code 156)
- Appendix A. Configuring services for NFS on Windows
- About configuring services for NFS on Windows 2012 or 2016 (NetBackup for VMware)
- Appendix B. Backups of VMware raw devices (RDM)
Test Query: Failed virtual machines
If the query rules cannot exclude a virtual machine, and that virtual machine cannot be selected for backup, it is marked as FAILED. The virtual machine is listed as not run in the job details log.
For example: the virtual machine does not have the type of name specified by the Primary VM identifier parameter (such as host name or display name). Or the virtual machine name contains invalid characters. In any case, a virtual machine that is listed as FAILED should be investigated: it may be one that you want to back up.
To see the reason for the failure, click on the virtual machine in the Test query results. An explanation appears at the bottom of the screen.
You can fix this problem in a couple of ways:
Use vSphere Client to configure a host name for the virtual machine.
To exclude the virtual machines that have no host name, construct a query with the IsSet operator.