Categories: APM

Upgrading a high availability configuration

Posted: January 30, 2019 Modified: August 13, 2019


You can upgrade a high availability configuration of IBM Application Performance Management (APM) version 8. You can upgrade from version 8.1.3 to 8.1.4, but also from minor releases.

Design options

There are several options to consider when designing your HA configuration for APM. The main differences are the DB2 setup and determining if you want to use Virtual IPs or use proxy servers.

DB2 options

For DB2 we recommend DB2 HADR which has a Primary server and Standby server. Both servers have a complete copy of the database. One is the primary and the other is the standby database. The standby database is kept in sync with the primary database so the standby can quickly take control if the primary fails. DB2 HADR requires Virtual IPs or manually updating the APM configuration files to configure ACR. You can manually failover DB2 HADR or you can automate it by adding TSAMP (Tivoli System Automation for Multiple Platforms). TSAMP is include in the DB2 package and DB2 can be configured using db2haicu. This configuration will require 3 VIPs (WAREHOUS, DATAMART, SCR32) or ACR. If you do not use TSAMP you can manually failover the database by running db2 takeover for the 3 database and manually moving the VIP or VIPs to the other server.

Another DB2 option is to use one set of databases that reside on shared storage. For example, RAID storage could be used. In the event of a failure the filesystems are unmounted on the failed server and mounted on the standby server and the VIP is moved to the standby server. DB2 with shared filesystems can be automated using TSAMP and configured using db2haicu. When using this configuration all the filesystems are moved together and all 3 databases are moved together. This configuration requires 1 VIP and ACR is not supported. Using a single database on a shared filesystem takes longer to failover but it saves the cost of the duplicate database and only requires one VIP for DB2.

APM options

For APM you have the option to use a Virtual IP to direct agents to the primary APM server or you can use a proxy server to direct agents to the primary APM server. The advantage of using a proxy server is that a proxy server can redirect the agents to an APM server on another subnet or even another data center.

Whether you use a VIP or a Proxy Server you must use firewalls to prevent both APM servers from accessing the database at the same time. If APM server “A” is the primary, then APM server “B” must be blocked from accessing the database. You do not need to change the firewall rules during an APM failover if you use a VIP on the APM server to redirect connections to DB2.
An alternative to VIPs is using DNS entries and updating the DNS during a failover. Some customers use this option but we do not provide documentation for it here.

Upgrade options

When upgrading your existing APM HA environment there are two methods to consider. You can upgrade in place which means you use the same 4 servers that are currently running 8.1.3 and APM is down while you do the upgrade. The advantage with this method is that a second system is not required for the upgrade. Customers with small to medium environments usually choose this method.

Customers with larger environments may want to create a new set of servers (side-by-side upgrade) and then run a backup from the 8.1.3 servers and restore to the new 8.1.4 servers. In a side-by-side upgrade the 8.1.3 servers continue to run while the 8.1.4 servers are being setup. After the new servers are setup a backup is performed using the 8.1.3 servers and restored to the 8.1.4 servers.

In this .pdf we are focusing on doing an in place upgrade of APM 8.1.3 to 8.1.4.


Released: 29 Jan 2019
Revision: 4.3
Cost: No Charge
Support: Not Supported




This package is subject to the terms and conditions displayed upon download.

This download has been prepared and reviewed by IBM. It is offered “AS IS” to existing customers. Support is not provided for this download.

Resource Tags