Optimizing BDLS For HANA Large Scale Instances (HLIs)

Introduction:

The purpose of this blog post is to give the audience an overview of how I handled BDLS process in the refreshes of HANA Large Scale Instances. I will try to give as much information as possible (which is already publicly available and maybe not all be in a single place) and try to depict how I used it to build a solution.

The Motivation: 

All SAP Basis consultants had to deal with BDLS process in their careers at some point or the other, but it becomes a challenge and a pain when the size of the DB is in several TBs. The process then needs many hours or even days to run.

High Availability and DR for SAP HANA, SAP S/4HANA, and SAP Central Services

As SAP application touches many critical parts of a company such as its’ ERP, manufacturing, business processes, customer service etc. it has become the lifeline of many enterprises that depends on it for their business to operate properly. As such, high-availability has became one of the top concerns of company managements when it comes to their SAP systems.

In this article, we will discuss at a high-level what is HANA system replication, how it works, what are the limitations when it comes to high-availability, and how we can overcome them. We will also discuss about the options for SAP HANA, SAP S/4HANA and SAP Central Services’s high-availability and what are the key differences, so that you can choose the right tool for the right job.

HANA – Linux staging

A lot of customers asking for the optimal operation strategy regarding Linux/HANA and how it will change their current operational processes. So, we talk about lifecycle management – patching of the different components of a system.

Your SAP on Azure – Part 4 – High Availability for SAP HANA using System Replication

In the today’s post, I would like to present you a solution for protecting the HANA database server.

SAP HANA database offers two solutions that are designed for High Availability:

a) Host Auto-failover – in this solution you need to deploy additional host to the current HANA database and configure it to work in standby mode. In case the active node failures, the standby host can automatically switch operations to the secondary node. This solution requires a shared storage, which we already know is a small problem for Azure