VDDK thread timeout, possible VDDK deadlock encountered.

Hello @Ersi 

Is the VM up and running? Are you able to take a manual snapshot from the vCenter with “Quiescing option enabled” ? 

Are you able to run the backups using NBD mode?

If the snapshot of vCenter works fine, is the communication from access node to the Esxi over port 902 is working? Could you please confirm it using telnet? 

If the telnet is also working, would you be able to do a storage vMotion of the VM and retry the backups? 

Best,

Rajiv Singal

Hello @Ersi 

Please update us on the below things to help you further, 

1. What is the version of the ESXi host that hosts the VM vm.srvfs3?
2. What is the VDDK version used in the affected backup job? You can get this from the vsbkp.log. 
3. Based on the answer of qn.1 and qn.2, we can help you further.

Regards,

Kalaivanan.

Hello @Rajiv 

Thank you for the response.

The VM is running, i can take a snapshot of the vm with the option Quiescing option enabled.

The backups are using NBD mode.

The telnet on port 902 works fine.

I cant do a storage vMotion of the VM because the vm is on and i dont have a licence to do that.

i change the resources of the vm but it is the same problem.

Hello @Kalaivanan 

Thank you for the response.

The esx version is VMware ESXi 7.0.1 build-17325551

And vddk version is 11.28.56.

thank you,

Ersi

Hello @Ersi 

11.28.56 is the Commvault version. 

You can find the VDDK version from the vsbkp.log in the access node. 
If you need any assistance to check VDDK version, you can upload the vsbkp.log of the affected job.
Else, you can raise a support case so that we’ll get on a remote session and check this issue. 
 

Hello @Kalaivanan 

i have uploaded the file vdbkp.log 

i hope this will help solve my problem

Thank you!

[Edited to remove attachment - Commvault moderator]

​@Ersi How did you solve the problem? We are having the same problem and no solution yet.

​@mischko86 given the fact that the case from ​@Ersi is more than a year old I would assume that the surroundings are completely different. Big chance that his case was solved via a hotfix. Anyhow what version are you running and please share some environmental information and log sections.