After upgrading the vSphere environment to vSphere 5, there has been a noticeable increase in the backup times.
There has been a substantial change from vSphere 4 to vSphere 5 hosts hypervisor. Most of the vSphere 4 hosts contained an ESX hypervisor, and as result had a console that could be leveraged during backup times. All VSphere 5 hosts, have ESXi hypervisors, and do not contain a console.
With ESX hosts, vRanger was able to do a direct to Target backup, (i.e the backup went straight from the ESX host to the repository).
With ESXi hosts, without a console the backup needs to go through the vRanger server on the way to the repository.
To maintain the “ Direct to target” backup infrastructure with vSphere 5, consider using vRanger virtual appliances.
For more details on vRanger va’s and other backup transport methods, please review both the users and deployment guides for the relevant release of vRanger you have installed.
For other vRanger backup transport methods see
“Choosing an Architecture” in the deployment guide;
http://us-downloads.quest.com/Repository/support.quest.com/vRanger/5.5/Documentation/E/vRanger_5.5_DeploymentGuide.pdf
For more information on how to use the Virtual appliance Deployment Wizard, please see
“Configuring the virtual Appliance” in the installation and setup Guide”.
http://us-downloads.quest.com/Repository/support.quest.com/vRanger/5.5/Documentation/E/vRanger_5.5_InstallationGuide_RevA.pdf
