High Availability factors per environment (BBAS)

High availability (HA) and resiliency for the BMC BladeLogic Automation Suite is achieved on a per-product basis. Each product is configured differently for high availability. For most server types specified, a duplicate server is specified in the deployment architecture for redundancy. For database high availability, it is recommended that the vendor's technology or a third party be used (for example, Oracle Real Application Clustering or Microsoft Peer to Peer Replication).

Environment or component	Is HA recommended?	High availability options
BMC Analytics for BSM	No	Not applicable
BMC Atrium CMDB and BMC Remedy ITSM (Mid Tier)	Yes	Load balanced, redundant web servers
BMC Atrium CMDB and BMC Remedy ITSM (AR System server)	Yes	Server Groups
BMC Atrium Discovery and Dependency Mapping	No	Not applicable
BMC Atrium Orchestrator Platform	Yes	Load balanced redundant CDP and Grid
BMC BladeLogic Decision Support for Network Automation	No	Not applicable
BMC BladeLogic Decision Support for Server Automation	No	Not applicable
BMC BladeLogic Network Automation	Yes	Operating system clustering
BMC BladeLogic Server Automation (Application Server)	Yes	Load balanced application servers
BMC BladeLogic for Server Automation (File Server)	Yes	Network Attached Storage or Storage Area Network
BMC BladeLogic Server Automation (PXE/TFTP)	Yes	Operating system clustering
BMC Dashboards for BSM	No	Not applicable
BMC ProactiveNet Performance Management	Yes	Operating system clustering

The product-specific HA configuration information in this section is included as a reference from the Deployment Architecture per Product section. This information is for general purposes and is not specific to the BMC BladeLogic Automation Suite.

BMC Analytics for BSM high availability