SAP on AWS · SAP HANA on AWS

HANA system replication can be multi-tier or multi-target. Which one chains replication sequentially, and why does that distinction change your failure exposure on AWS?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in SAP HANA on AWS

An architect provisions slow st1 HDD for /hana/data on a production HANA node, reasoning that HANA runs in memory so disk speed is irrelevant. Why is this wrong?

What are the four main SAP HANA deployment offerings on AWS?

You must size an AWS EC2 target for an existing on-prem SAP HANA system versus a brand-new greenfield implementation. Which sizing input do you reach for in each case, and what's the trap?

In a typical HANA EC2 storage layout, why is /backup placed on st1 (throughput-optimized HDD) while /hana/data and /hana/log sit on gp3 or io2 Block Express?

You've outgrown a single HANA host. What decides whether you go scale-up (bigger box) versus scale-out (more nodes) on AWS, and what extra dependency does scale-out drag in?

For production HANA you can choose gp3 or io2 Block Express, and you can stripe volumes with RAID 0. Which volume do you pick for production, and what caps the RAID 0 gain?

Start learning today

Free to start — download the app or use it in your browser.