- VP, Product Management
- Posts: 1071
- Liked: 239 times
- Joined: Jan 01, 2006 1:01 am
Which aspects do you wish to Cluster? Because nworks v5 has its own built-in High Availability.
You install our nworks Management Center; then you deploy two (or more) nworks Collectors (the component that does the actual gathering of monitoring data)
nworks Management Center will watch heartbeat of the Collectors, and will automatically fail-over the monitoring Jobs if one Collector fails.
You don't need to use Microsoft Clustering, as our Management Center will perform this task.
Hope that answers your question!
Vice President, Product Management
- Posts: 3
- Liked: never
- Joined: Sep 18, 2009 12:29 pm
Really I want to know what is teh best way to install nwoks over OMW 8.10 in a cluster environment?...maybe first inactive node and after this in the other, etc.
- Veeam Software
- Posts: 89
- Liked: never
- Joined: Apr 09, 2009 9:09 pm
- Full Name: Nick Kordich
The SPI for VMware follows the same install as other SPIs (as per HP's Install and Upgrade Guide for the SPI DVD): install the SPI on Node A in a cluster, then install it again on Node B, Node C, and so on, until you've installed the policies and instrumentation to every node in the cluster.
The SPI for VMware has several components - including a collector service, UI, and license/monitoring job server component. The only component we recommend installing on the OMW management server is the one installing the policies and instrumentation, which we call the Management Server Component (the file is VmspiOmwSetup.msi). Please install this component on each node in the cluster.
The other components should be installed to other systems. The nworks management center component (nMC) handles the licensing and provides HA/load balancing among collectors, as Alec mentioned, and it's usually installed on the same system as the UI component. These components can be installed on one of the collector components, or on a separate system (or systems - the nMC and UI don't even need to be on the same system). Our Deployment Guide has additional information on the architecture that you may find useful.
Users browsing this forum: No registered users and 1 guest