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.

High Availability Factors per Environment

A highly available deployment ensures resilience for the service offered by the product deployment. The need for a highly available deployment depends on business needs. If the service availability is considered critical, a highly available deployment might be important. This ensures that the service stays available despite failures in either the software (like the application servers or the operating system), or hardware (like network cards or power systems).

The following table lists of methods for achieving high availability (HA) for BMC products: 

Environment or component

High availability options

BMC Atrium CMDB and BMC Remedy ITSM (Mid Tier)

Load balanced, redundant web servers (Active/Active)

BMC Atrium CMDB and BMC Remedy ITSM (AR System server)

Server Groups (Active / Active)

BMC Atrium CMDB and BMC Remedy Cloud (AR System server)

Server Groups (Active / Active)

BMC Atrium Orchestrator Platform

Load balanced redundant CDP and Grid

BMC Network Automation

OS clustering (Active / Standby)

BMC BladeLogic Server Automation (Application Server)

Load balanced application servers (Active / Active)

BMC Platform Manager (OSGI )

OS clustering (Active / Standby)

BMC ProactiveNet Performance Management

OS clustering (Active / Standby)

Microsoft SQL Server 2008 R2 Enterprise 64-bit (Database)

OS clustering (Active / Standby)

Oracle Enterprise Database

Oracle RAC (Active/Active)

BMC Capacity Optimization (BCO) Console

Load balanced (Active / Active)
OS clustering  (Active / Standby)

BCO Data hub

OS Clustering (Active / Passive)

BCO ETL Engine

OS Clustering (Active / Passive)

This following topics provide information about high availability for the BMC products:

Was this page helpful? Yes No Submitting... Thank you