vCenter Heartbeat and nWorks

Unleash the power of System Center for vSphere and Hyper-V | Veeam Task Manager for Hyper-V

vCenter Heartbeat and nWorks

Veeam Logoby kavanaghsteve » Thu Sep 27, 2012 12:50 pm


I'm looking at implementing nWorks in an environment that uses vCenter Heartbeat to provide HA of the vCenter service.

Does anyone have any experience with a deployment like this, and know if there are any issues I need to be aware of?

I'm assuming that seeing as the collectors talk to the API on port 443 all that should be required is configuring them to talk to the Heartbeat 'public' cluster IP or DNS name so that when Heartbeat flips between vCenter nodes nWorks always connects to the active instance?


Posts: 6
Liked: never
Joined: Wed May 11, 2011 1:57 pm
Full Name: steve w

Re: vCenter Heartbeat and nWorks

Veeam Logoby Alec King » Mon Oct 01, 2012 11:53 am

Hi Steve,

We have not done extensive testing of this scenario; but essentially you are correct - our monitoring connection via the vCenter API would simply be re-directed (with all other traffic) through the VC-Heartbeat connection.
As I understand it VC-Heartbeat (akak NeverFail) actually does app-specific packet filtering to direct traffic to the 'live' instance of vCenter in the cluster. As long as our API 443 (default) traffic is correctly directed and authentication also passed correctly then nworks should have no issues.

Alec King
Veeam Software
Posts: 848
Liked: 147 times
Joined: Sun Jan 01, 2006 1:01 am

Return to Veeam Management Pack for Microsoft System Center

Who is online

Users browsing this forum: No registered users and 1 guest