Skip to Content
Information
Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

BMC ProactiveNet Performance Management high availability

High availability for BMC ProactiveNet Performance Management (BMC ProactiveNet) requires configuring various components of the product in high availability. The following topics list the critical components of the product:

High availability for the BMC ProactiveNet Server

BMC ProactiveNet works in Active-Passive mode to achieve high availability. You can install the BMC ProactiveNet Server in high availability using clustering technology provided by the OS vendor. For example, Microsoft provides Windows Cluster Service and Oracle provides cluster software Oracle Solaris.

BMC ProactiveNet in high-availability mode consists of two servers with identical configurations: the primary node and the standby node (also referred to as the secondary node). Both these servers share a logical IP address and cluster name, and have access to a shared storage disk.

You must install the BMC ProactiveNet Server on the shared storage disk and the logical IP/host name must be enabled on the primary node. When the primary node is down, the secondary node picks up the installation from the shared storage disk.

High availability for the BMC ProactiveNet Agent

You can install the BMC ProactiveNet Agent in high availability using clustering technology provided by the OS vendor. When the Agent is added to the BMC ProactiveNet Performance Management Server, two servers that have the same virtual IP address are required. No shared disk is required between the two servers.

High availability for the BMC ProactiveNet Integration Server

The BMC ProactiveNet Integration Service consolidates data from multiple BMC PATROL Agents. You can configure BMC PATROL Agents (version 3.8.50 and later) to specify primary and secondary Integration Services. When the primary Integration Service is not reachable from the BMC PATROL Agent, the agent automatically connects to the secondary server and vice versa. The order of preference to implement Integration Server in High availability is:

  1. Deploying the Integration Service on a virtual machine using VMWare High availability option.
  2. Operating System Cluster Setup.
  3. Out of the box capability.

For more information on Integration Server on High Availability, see the Integration Service topic in the BMC ProactiveNet documentation.

High availability for the BMC ProactiveNet Remote cell

The BMC ProactiveNet Remote cell is responsible for collecting events and impact information. You can configure Remote cells in the high availability mode. A configuration file on the server in which the remote cell is running needs to reflect the primary and secondary cell.

High availability for BMC ProactiveNet Report Engine

The BMC ProactiveNet Performance Management system propagates events and component status changes from BMC ProactiveNet servers to BMC ProactiveNet Report Engine. The Report Engine then aggregates and summarizes the events and component status changes and stores the processed data in the Oracle database. A BusinessObjects server is then configured to access the Oracle database for producing reports. No high availability solution is available for the Report Engine component.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Cloud Lifecycle Management 3.0