Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ for KVM Administrator's Guide
  3. Troubleshooting KVM backups and recovery
  4. Troubleshooting a KVM discovery or a validate operation
NetBackup™ for KVM Administrator's Guide

Troubleshooting a KVM discovery or a validate operation

Discovery or Validate operation fails for the KVM host

Recommended action: Ensure sure that the KVM host is reachable and that NetBackup services are up.

A backup of a virtual machine without a storage pool cannot be restored to the original location

If the virtual machine disk files did not reside on the storage pool during the backup, the pre-recovery check fails if the user attempts to restore to the original location. In this case, restore to an alternate location. By default for this kind of restore, the Destination storage pool and the Destination volume values are empty for the virtual machine. Select the wanted values before you continue with the restore.

A backup job fails with error 4726 - Failed to create snapshot of the specified VM.

The bpbrm logs on the media server contain the following message:

12:41:49.943 [3275984.3275984] <2> get_bpfis_msg: bpfis buff: FTL - Unable to 
quiesce VM filesystem. 
Verify the QEMU guest agent is installed and running.
12:41:49.943 [3275984.3275984] <32> get_bpfis_msg: from client alpine2: FTL - Unable 
to quiesce VM filesystem. 
Verify the QEMU guest agent is installed and running.
12:41:49.944 [3275984.3275984] <2> set_job_details: Tfile (12): LOG 1752774109 32 
bpbrm 3275984 from client 
alpine2: FTL - Unable to quiesce VM filesystem. Verify the QEMU guest agent is 
installed and running.
12:41:49.944 [3275984.3275984] <2> send_job_file: job ID 12, ftype = 3 msg len = 146, 
msg = LOG 1752774109 32 
bpbrm 3275984 from client alpine2: FTL - Unable to quiesce VM filesystem. Verify the 
QEMU guest agent is installed and running.

This error can occur if the Virtual machine quiesce option is selected without the option Perform snapshot without quiescing if quiesced snapshots fail for the backup policy.

A snapshot may fail if the virtual machine can't be quiesced. This error usually means that the QEMU agent isn't installed or isn't running on the guest system. To fix this issue, you can either resolve the QEMU agent issue on the guest VM to allow for a successful quiesce operation. Or, select the option Perform snapshot without quiescing if quiesced snapshots fail option.

A backup of a virtual machine fails if the QEMU guest agent is not installed

The KVM advanced attribute Virtual machine quiesce is enabled by default and requires that the QEMU guest agent is installed. If not, the backup fails.

Feedback

Was this page helpful?
Previous

Configuring VxMS logging

Next

Using a custom overlay path location

Feedback

Was this page helpful?