I've been a fan of Vizioncore's vRanger Pro for a long time now, having used it for several years to backup a VMware 3.x farm I managed.  So I've been particularly eager to try out the recently-released version 4.0 (<a href="http://www.vizioncore.com/products/vRangerPro/">http://www.vizioncore.com/products/vRangerPro/</a>)

A clean installation of version 4.0 went flawlessly, but I was surprised when I encountered problems running backup jobs.  A call to Vizioncore Support revealed a suprising undocumented fact: running vRanger Pro 4.0 on your vCenter server is not a supported configuration.  It's been reported in a few isolated cases that rebooting the vCenter server while the vRanger Pro 4.0 gui is open can sometimes prevent the vCenter services from starting properly.  Vizioncore has a KB article on the issue that can be found by searching for KB Article 00000296 at this link: <a href="http://www.vizioncore.com/support/knowledgebase/index.php">http://www.vizioncore.com/support/knowledgebase/index.php</a>

In my case, I reinstalled on a new vm and it's working great.  Some other tips gleaned from the call:
<ul>
	<li>Version 4.0 is supported on Windows Server 2008, but Windows 2003 might be more stable for this first release</li>
	<li>Using the local Administrator account instead of a domain account to run the vRanger Pro services will provide the best stability</li>
	<li>vRanger Pro 4.0 was released without support for VCB (but VCB support will be released soon)</li>
</ul>