Skip to Content
SAP HANA

SAP Hana TDI setup - VMware 5.1 (part 2)

Tags:

Hello this is the second part on my document SAP Hana TDI setup - VMware 5.1, i'll explain how to configure HSR for Hana.

You can check the first part of the document for the previous deployment scenario from the link below

SAP Hana TDI setup - VMware 5.1 (part 1)

Configure and setup for scenario 3 – Disaster Recovery (HSR)


An important point when doing a HRS configuration before set things up is that we must have the same topology on both sites, the standby node is optional.


Quick sum of activities not documented in this section:

  • Deployment of vm from template
  • Adjustment of parameters
  • File system mount for new system
  • Secondary Hana installation

From a technical stand point in order to make it happen, several network and server consideration needs to be take care, to realize this configuration the following step needs to be proceed as below:

  • Have both Hana system deploy and up and running
  • HSR configured between Hana systems
  • Take over test
  • Configure SLES11 SP3 Cluster
  • Set the SAP Hana integration

HSR configuration

Since my 2 Hana landscape are up and running for my 2 site, I can start the setup of the replication process.

On the primary site enable the replication


Now I stop the secondary site in order to register it


Note: do not provide fqdn

While Site2 is starting check out Site1


After a minute the replication is “Active”

And the secondary system become unavailable for connection with all service up and running

HSR Takeover testing

Now that my systems are setup for replication, I will create user and some package on Site1 and validate after taking over to Site2 if all my change has been taken in consideration.

In order to perform the takeover, from Site2 proceed as following

Disable the replication from the former primary site

And stop it and register it as secondary now

Once done we can see that the Site2 became the primary and Site1 the secondary, also I can now see my user and package created earlier are on the second host

All the action performed above trough the studio can also be done by command line tool with: hdbnsutil .

In the next part of my documentation I’ll explain how to configure SLES in order to configure Hana with it.

SLES and Hana setup for DR

In this section I’ll explain how to control the failover process automatically with Hana on SLES Cluster, in order to make it happen I first configure SLES as a cluster with the two servers (hana01 and hana02)

On the 2 servers install the “ha_sles” package

Once installed, run the initial cluster config on the first node by using “sleha-init” command

Now done, go on the secondary node and register it into the cluster y running “sleha-join”

And do a check at the HAWK interface from the address provide during the first node install, i can see my 2 servers clustred now

In order to make Hana embedded in my Linux Cluster, I did install at the beginning the package “SAPHanaSR”, I’ll then use the HAWK to set it up.

Once the wizard done I check the status (The red errors are because at this moment I did not have installed the host agent)

Once the problem fixed I make a test on the virtualip define earlier for the cluster “192.168.0.145” and see which node I’m on

I'm on the first node

The configuration is completed ...

On my next blog i'll focus on the testing scenario with SLES Ha/DR.

Williams