VM is stuck during Veeam backup and host becomes unresponsive

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms: 

• VM is stuck during Veeam backup
• VM vmware log stops during the Snapshot consolidation without error
• The ESXi host upgraded recently
• ESXI host goes into unresponsive state 

Environment

VMware vSphere ESXi 8.x

 

Cause

This issue occurs when snapshot-based backups (or snapshot consolidations) overlap with Continuous Data Protection (CDP) replication.

Running these two heavy processes at the same time or shortly after CDP replication cycles creates a bottleneck. Because the ESXi host has to process all the snapshot data through the active CDP (VAIO) filters, the host management agents become overloaded.

This combined resource exhaustion directly leads to the following symptoms:

• Delayed snapshot consolidations

• Extended VM stuns (freezes)

• Unresponsive ESXi hosts

Cause Validation: 

• ESXi hostd log keeps showing:  
  
  Log path : less /var/run/log/hostd.log

Wa(164) Hostd[2100035]: [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/####/#####.vmx opID=WorkQueue-73ac4477-c7-3195 sid=52ea2007 user=vpxuser:<no user>] File - failed to get objectId, '/vmfs/volumes/####/####/####.vmx': Operation not supported (11)
In(166) Hostd[2100035]: [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/####/####/####.vmx opID=WorkQueue-73ac4477-c7-3195 sid=52ea2007 user=vpxuser:<no user>] Error retrieving file layout : N3Vim5Fault8Timedout9ExceptionE(Fault cause: vim.fault.Timedout
In(166) Hostd[2100035]: [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/####/####/####.vmx opID=WorkQueue-73ac4477-c7-3195 sid=52ea2007 user=vpxuser:<no user>] Skip caching of external disk paths due to incomplete layout.

• The createSnapshot task is timedout from vCenter vpxd log:

          Log path : less /var/log/vmware/vpxd/vpxd.log

error vpxd[06121] [Originator@6876 sub=Default opID=393ddb6] [VpxLRO] -- ERROR task-1224485 -- 522fb330-######0d5d(52c0a4b2-f2bc-48a5-b741-656fb10feccd) -- vm-### -- vim.VirtualMachine.createSnapshot: :vim.fault.Timedout
--> Result:
--> (vim.fault.Timedout) {
-->    faultCause = (vmodl.MethodFault) null, 
-->    faultMessage = <unset>
-->    msg = ""
--> }
--> Args:
--> 
--> Arg name:
--> "VEEAM BACKUP TEMPORARY SNAPSHOT"
--> Arg description:
--> "Please do not delete this snapshot. It is being used by Veeam Backup."
--> Arg memory:
--> false
--> Arg quiesce:

 --> false 

   (Or) Another task is already in progress. 

      2026-03-03T00:54:23.327+11:00 warning vpxd[2799588] [Originator@6876 sub=Vmomi opID=72e99a2b] VMOMI activation LRO failed; <<#######c, <TCP '127.0.0.1 : 8085'>, <TCP '127.0.0.1 : 52756'>>, snapshot-200975, vim.vm.Snapshot.remove, <vim.version.v8_0_2_0, official, 8.0.2.0>, (null)>,              N3Vim5Fault14TaskInProgress9ExceptionE(Fault cause: vim.fault.TaskInProgress
   --> )
   --> 
   2026-03-03T00:54:23.333+11:00 info vpxd[2799588] [Originator@6876 sub=vpxLro opID=72e99a2b] [VpxLRO] -- FINISH task-3174510
   2026-03-03T00:54:23.333+11:00 error vpxd[2799588] [Originator@6876 sub=Default opID=72e99a2b] [VpxLRO] -- ERROR task-3174510 -- ########) -- snapshot-200975 -- vim.vm.Snapshot.remove: :vim.fault.TaskInProgress
   --> Result:
   --> (vim.fault.TaskInProgress) {
   -->    faultCause = (vmodl.MethodFault) null,
   -->    faultMessage = <unset>,
   -->    task = 'vim.Task:haTask-147-vim.vm.Snapshot.remove-214349'
   -->    msg = "Another task is already in progress."
   --> }
   --> Args:
   -->
   --> Arg removeChildren:
   --> false
   --> Arg consolidate:

• The VM is protected by Veeam CDP:
  
  ####.vmdk:ddb.iofilters = "veecdp"
####vmdk:ddb.sidecars = "veecdp_1,####33ed2.vmfd"

Resolution

• If the CDP filter fails to detach or if the VMs remains in an "invalid" state, engage Veeam Support to investigate within the CDP metadata or the veecdp filter's interaction with the vSphere APIs for I/O Filtering .
• Contact Veeam to delete the CDP and check if any issue on iofilters.
• Recommend to schedule maintenance window as VM may be stuck during the CDP deleting process.