This is part 5 of a 5 series post on VEEAM installation and configuration. In this section I will show how to troubleshoot performance issues with the Virtual VEEAM Backup and Replication server.
Read my other posts on this topic:-
Part 1 (Introduction and Pre-requisites)
Part 2 (VEEAM Installation steps)
Part 3 (VEEAM Configuration)
Part 4 (Creating backup jobs)
But the network was hardly being utilized.
The Windows resource manager showed moderate to high I/O on the backup drive (which is understandable and acceptable, considering that we were running two backup streams simultaneously).
The vSphere performance graphs also confirmed the stats that the Windows task manager was showing.
To further explore the issue, I looked at the VEEAM backup job logs. The logs clearly had an entry which said that the primary bottleneck in the whole process was our Proxy server (which in our case is also our VEEAM Backup and Replication server). Read the second last line in the job log screenshot below ("Primary bottleneck: Proxy").
To troubleshoot this issue I looked at the task manager performance window, the VM's performance tab in the vSphere client, and the VEEAM backup job logs. I decided to increase the number of vCPUs on the VM from 2 to 8.
After increasing the number of cores, I was able to run the job faster and without causing any performance impact on the VEEAM Backup server.
This concludes the 5 series blog on VEEAM Backup and Replication. I hope you enjoyed reading the blog. Please feel free to leave any comments and I will reply to them as soon as I can.
Thank you.Gurpreet Singh Anand