SLT based HANA replication-FusionOps activity

This article uses as To perform SLT based replication in hana with ecc system

Login to D1H and execute LTRC T-Code

Automate SAP HANA System Replication with SLES for SAP Applications

SAP HANA System Replication on SLES for SAP Applications

What is this solution about?

The solution created by SUSE is to automate the takeover in SAP HANA system replication setups.

The basic idea is that only synchronizing the data to the second SAP HANA instance is not enough, as this only solves the problem of having the data shipped to a second instance. To increase the availability you need a cluster solution, which controls the takeover of the second instance as well as providing the service address for the client access to the database.

HANA SDI | Smart Data Integration 2.0 – H2H Real-time Replication: Lessons Learned

In this blog entry I would like to convey some of the experiences we made throughout an SDI HANA to HANA (H2H) implementation project. To gather an understanding of the context, we will start off with the scenario description and solution architecture.

These are the items that will be covered throughout this blog:

Hana DR – Replication of INI parameters

Before Hana SPS12 we always have to manually setup the INI parameters on the secondary site after a change in the primary. It is not a tough thing to do nevertheless SPS12 introduced a feature to get a synchronization between the systems in a DR scenario also for INI parameter changes. One more step in the Hana synchronization and in my opinion it’s welcome.

I’ll not go into the replication configuration steps just describe my findings on the INI replication subject. Hope you get it useful.

SAP HANA 2.0 SPS 00 What’s New: High Availability

Introduction

we will be posting new videos to the SAP HANA Academy to show new features and functionality introduced with SAP HANA 2.0 Support Package Stack (SPS) 00.

Replication setup using HANA cockpit 2.0 and testing Active/Active Read Enable

Prerequisites:

• You have installed and configured two identical, independently-operational SAP HANA systems – a primary system and a secondary system.
• The required ports must be available.
• The same instance number is used for primary and secondary systems. The instance number +1 must be free on both systems, because this port range is used for system replication communications.
• You have added both systems in the SAP HANA cockpit.
• You have verified that the log_mode parameter in the persistence section of the global.ini file is set to normal for both systems.