VM backup performance troubleshooting

Hello @Boyi 

Please let me know the following: 

1. What is the commserve version and vddk version?
2. How many VM’s are impacted? 
3. What is the transport mode being used?
4. If you double click on a job, which component out of (read, network, write) is taking the most time?
5. Can you share and check vsbkp.log on the access node and check for stat id and look for stats where exactly is the bottleneck.
6. Also, you can watch this informative video and can run a test against the datastore: 

Best,

Rajiv Singal

Hi Rajiv,

What is the commserve version and vddk version? Commserve is at 11.24.112. I don't have access to customer’s vCentre/ESX so I dont know about vddk.
How many VM’s are impacted? this is a new setup so we only tested the backup on one VM. But there are other VMs in the same/different ESXs that are within the same vCentre.
What is the transport mode being used? NBD
If you double click on a job, which component out of (read, network, write) is taking the most time? Read and DDB.
Can you share and check vsbkp.log on the access node and check for stat id and look for stats where exactly is the bottleneck. I looked into vsbkp.log and cannot find info for bottlenet. Can you give me an example? In the CVPerfMgr.log I see that it is the disk read as I posted originally.

Hello @Boyi 

If disk is taking time to read its probably a datastore issue, for example higher IOPS. Were you able to run the test as mentioned in the video I shared above? DDB can take time if its a fresh/first backup.

In vsbkp.log you should see something with stat-id and check the disk performance there. Also, you can find the VDDK version in the vsbkp.log itself.  If you can share the log here as an attachment, I can check and share the result with you here. 

If you would need proper assistance in getting this rectified and resolved, you can raise a case with us and we can assist you further.

Best,

Rajiv Singal