Replication job hangs in queue - never goes to running task.
no other jobs running, but this one job just sits in queue.
Several things need to be looked at.
What else is running on the vRanger server? Often we see this if Virtual Center is sharing a server with vRanger. This is NOT a recommended configuration.
How long ago was the services restarted, or the server rebooted?
Are there enough resources available? Check CPU and RAM for your configuration detailed in the vRanger System Requirements guide available on SupportLink.quest.com.
Check the My Jobs configuration settings. Deviating from the defaults can improve performance, or cause issues. Check with support for the best settings for your configuration.
First, try restarting the services and rerun the job. If this does not resolve it, reboot the server and rerun the job.
Next reset the My job configurations to default settings. Below are the default My Job configuration settings.
restart the services, and re run the job.
on vRanger (>=1) -- Default is 100.
off a LUN (1-5) -- Default is 3.
on a host (1-4) -- Default is 1.
on each repository (>=1) -- Default is 3.
locally (1 - 20) -- Default is 3.
per VA (1 -18) -- Default is 2.
Look for other software that could be interfering. vRanger support can assist you with this.
If you issue persists, please contact support and we will assist you.