Some of the causes include, but are not limited to:
1. There are too many jobs scheduled to start at the same time every day.
2. Contention during jobs due to configuration of the backups/environment.
3. vRanger requests more information from the vCenter or Host, and that can cause the request operation to take more time than what vRanger is configured to wait. For example, the creation of a VMware Snapshot is taking too long or another backup solution is running simultaneously.
4. The response times from the SQL server are slow.
Other tasks could be running at the same time on the vRanger Server, vCenter Server, or SQL server where vRanger DB is located.
Resolution 1:
Extend the amount of time vRanger will wait for the operation to get complete by following the steps below.
1. Go into vRanger directory (C:\Program Files\Quest\vRanger):
2. Copy the file Vizioncore.vRanger.Service.exe.config to have a backup of it and open it with an administrative notepad.
3. Find and change them from 60 to 300.
4. Save this file.
5. Restart the vRanger services by following these steps will resolve this issue:
a. Stop the Quest vRanger Services from top to bottom.
b. Once all the services are stopped please start the services from bottom to top.
6. After the vRanger services have been restarted please run the backup job or jobs again.
Resolution 2:
Stagger jobs to reduce the number of jobs running simultaneously.
1. In the vRanger UI | go to Tools | Options | My Jobs - Configuration. Reduce the maximum number of tasks running per resource. This adjustment of settings will be a trial and error process, it is recommended to start with conservative numbers, then tune them up.
The default values are:
2. Go to My Jobs | Scheduled Jobs | Increase the time between jobs.
Resolution 3:
1. Reboot the SQL server.
2. A script can be run to the SQL database to reduce its size.
This script with its description and instructions can be found in KB article 315807.
