Scale-Out Systems & Host Auto-Failover

How does SAP HANA's Fiber Channel Storage Connector perform I/O fencing in a SAN scale-out setup?

How does an SAP HANA client connect to a scale-out system so it can reconnect after a host takeover?

What are the three ways tables are arranged across nodes in a scale-out SAP HANA system?

How is high availability built into a scale-out SAP HANA system, and what does the standby node do while idle?

How are all nodes of a scale-out SAP HANA system started and stopped together, and which command lists host roles?

On which node do tables without an assigned group reside in an SAP S/4HANA scale-out system, and how are joined master/config tables handled?

How does data distribution in a scale-out SAP HANA system differ from traditional shared-disk database clusters?

What is the hardware recommendation for nodes in a distributed SAP HANA system, and how do takeover groups support heterogeneous hardware?

What does the SAP HANA Storage Connector API enable in different scale-out storage scenarios (NFSv3, NFSv4/GPFS, SAN)?

Why does SAP recommend scale-up over scale-out for SAP HANA when feasible?

What are the host-count requirements when combining SAP HANA system replication with a distributed (scale-out) system?

From a cost perspective, why might an SAP HANA scale-out deployment beat a single large scale-up host?

What is the difference between NAS and SAN storage for an SAP HANA scale-out cluster?

After a master name server fails and the system later restarts, which host becomes the master, and what happens to index server roles?

What roles can the SAP HANA name server take in a scale-out system, and how many masters can there be?

In SAP HANA host auto-failover, at what level is a takeover triggered, and what happens when only a single service fails?

What are the SAP S/4HANA scale-out node minimums and maximum cluster size?

Why is the scale-out architecture transparent to SAP HANA client applications, with one caveat?

What roles do heartbeats and fencing play in SAP HANA host auto-failover?

In a scale-out SAP HANA system, how is the system database distributed versus tenant databases?

Besides the index server, which SAP HANA components have worker/standby roles in a scale-out system?

How does SAP NetWeaver AS configure takeover support for connecting to a scale-out SAP HANA system?

What roles can the SAP HANA index server take in a scale-out system, and what is special about a STANDBY index server?

Why must a standby host be able to access all data volumes in an SAP HANA scale-out system?

Which SAP HANA lifecycle manager action reconfigures the network for internal communication, and when is it used?

What external software, if any, does SAP HANA host auto-failover require, and what is the key infrastructure prerequisite?

What is host grouping used for in a scale-out SAP HANA system?

Which SAP HANA system view shows the configuration and status of a multiple-host system, and which columns reveal name-server roles?

For a distributed SAP HANA system, what must `listeninterface` be set to, and which section maps internal hostnames?

What is the difference between scaling up and scaling out an SAP HANA system?

What are the network-based and storage-based heartbeats used in SAP HANA host auto-failover?

What is the standard SAP sizing data footprint for hot data, and how is it relaxed for warm data?

In a scale-out SAP HANA system, which directory is local per host and which is shared (NFS) across all hosts?