Replication jobs have been running fine until abruptly the replication jobs are stuck in queue even if resources on the VAs are tweaked while other VAs in the environemnt appear to work fine. Replication jobs to a particular VA simply will not run after a reboot of VA and even if ESX(i) host VA is on. Vmotion of VA does not resolve issue either.
Under investigation at this time
Two options exist.
Option 1: Delete the particular VA in questions and rebuild a new one.
Option 2: Upgrade to vRanger 5.4/5.5 and you can use auto deploy to create a new VA which can also be used as a cluster VA.
Please note this has only so far been seen on VA version 1.3.0 which goes with vRanger 5.3.0 and 5.3.1. If you are running vranger 5.4 or 5.5 and VA version 1.5 this behavior should not happen if so please open case with support.