On a Linux VM in Azure, as any Linux user, you can use the following to see the name of the physical host on which your VM is running:
In this case, we take the first 3 chars to be “Dublin”, which is in the EU North Azure region.
The remaining characters consist of the rack and physical hostname.
If you have 2 VMs in the same rack on the same physical host, then you will have minimal latency for networking between them.
Conversely, if you have 2 VMs on the same physical host, you are open to HA issues.
Therefore, you need a good balance for SAP.
You should expect to see SAP S/4HANA application servers and HANA DBs in the same proximity placement groups, within the same rack, even potentially on the same host (providing you have availability sets across the tiers you will be safe).
awk -F 'H''{ sub(/ostName/,"",$2); print $2 }' /var/lib/hyperv/.kvp_pool_3
Example output: DUB012345678910In this case, we take the first 3 chars to be “Dublin”, which is in the EU North Azure region.
The remaining characters consist of the rack and physical hostname.
If you have 2 VMs in the same rack on the same physical host, then you will have minimal latency for networking between them.
Conversely, if you have 2 VMs on the same physical host, you are open to HA issues.
Therefore, you need a good balance for SAP.
You should expect to see SAP S/4HANA application servers and HANA DBs in the same proximity placement groups, within the same rack, even potentially on the same host (providing you have availability sets across the tiers you will be safe).