IBM Support

Alternate or additional configurations available on Microsoft Azure

How To


This document contains information on how to configure fencing and a virtual IP with Db2 HADR Pacemaker on the Microsoft Azure platform.


To achieve high availability, IBM Db2 LUW with HADR is installed on at least two Azure virtual machines, which are deployed in an Azure availability set or across Azure Availability Zones.


Prior Implementing Db2 HADR on Azure, define the design of the Azure foundation services.  For more information, refer to the following Microsoft TechNet Article:
Microsoft Cloud Adoption Framework for Azure - Cloud Adoption Framework | Microsoft Docs

This design includes the following items:

  • Subscriptions
  • Active Directory and DNS design.
  • Network topology within Azure assignment of systems.
  • Azure role-based access control (Azure RBAC) structure for teams that manage infrastructure and Db2 in Azure.
  • Resource group topology.
  • Tagging strategy.
  • Naming conventions for VMs and other infrastructure components and/or logical names.
  • Availability Sets and Availability Zones
  • Azure Load balancer for health probes to detect the backend endpoint status (Pacemaker Node with assigned virtual IP in this case)
Refer to the following links for details about how to implement Azure fencing agents and virtual IP.
How to set up two-node Db2 HADR Pacemaker cluster with fencing on Azure:
How to set up a Db2 HADR Pacemaker cluster with Virtual IP and Load Balancer on Azure:

Document Location


[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"ARM Category":[{"code":"a8m500000008PkmAAE","label":"High Availability"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.5.6;and future releases"}]

Document Information

Modified date:
27 July 2021