Setting up Scale Out, High Availability and Monitor HANAHANA scale out is unlike other database platforms, it can be simple but complex at the same time. Depending on the scenario, the in-memory nature of HANA services, the persistence layers and optional multi-tenancy (Multi-tenant Database Container - MDC), it can get complicated pretty fast. The table distribution across systems and table partitioning can further add to the complexity. In the next several publications, we'll set out to cover the installation, configuration, testing, and SAP HANA monitoring in scale out, HA, DR with HANA System Replication, and Extended storage management with HANA Dynamic Tiering.
In our previous three part series BW Migration to HANA blogs, we built and migrated BW 7.5 from ASE to HANA as a single-node system. For this next series, we added several more systems to the same database to cater for the multiple scenarios as well as converting our storage subsystem to shared storage. These infrastructure planning, building and migration tasks were non-trivial but we've excluded details out since preparation steps may vary depending on your environment.
HANA Distributed System
Interested to learn more about our HANA expertise and services?