In HANA HA/DR design, a database virtual host is used as the logical SQL connection point for applications such as Netweaver ABAP or JAVA. For SAP monitoring management, automation of normal state HANA monitoring is only half the coverage, the failover event and post-failover monitoring should also be automated.
This presentation focuses on ITC’s monitoring of the HANA HA/DR when the HANA system replication (HSR) is not defined with operation mode ‘logreplay_readaccess’, using the ’virtual hostname’.
Sites normally use virtual hostname for failover/takeover purposes.
In prior posts, we have covered several topics on HANA HA/DR, System Replication, Scale-out and Dynamic Tiering. Please visit these for additional background:
Registering a HANA DB to ITC (1) - Physical
Registering a HANA DB to ITC (2) - Virtual
Registering a HANA DB to ITC (3)
Registering the Linux host
Registering a HANA DB to ITC (4)
Registering a HANA DB to ITC (5)
System Takeover from Secondary System (1)
Performing a system takeover from secondary system, either through HANA Cockpit or hdbnsutil command
System Takeover from Secondary System (2) - Simulating the Virtual Host FailoverThis step can be automated with Linux Pacermaker
System Takeover from Secondary System (3)
Summary – HA/DR and SR monitoring
IT-Conductor can monitor both the primary and secondary sides of an HA/DR landscape is configured with SR operation_mode ‘logreplay_readaccess’ - see HA/DR and System Replication monitoring with logreplay_readaccess mode
If the landscape is not defined with logreplay_readaccess, ITC can still monitor the primary system AND automatically ‘shifts’ its monitoring to the secondary system after a takeover, by registering the objects (HANA DB, Linux host) using virtual hostname