Figure 1 shows the single-node scenario where HA is not required.
Figure 1 Single-node scenario where HA is not required
The concepts involved in the preceding figures are as follows:
- VPC network: All SAP HANA nodes are deployed within a VPC network, and all nodes in the HANA system belong to the same AZ to ensure network security.
- Public subnet:
- Network Address Translation (NAT) instance ECS: allows you to access SAP HANA nodes using SSH.
- SAP HANA Studio ECS: runs the SAP HANA Studio software. You can use RDP or SSH to access the SAP HANA Studio ECS and manage the SAP HANA system.
- Private subnet:
node: used for deploying the SAP HANA software. An SAP HANA server has the following disks attached:
- OS disk: provides the directory for installing the OS.
- Data volume: periodically stores the data transmitted from the SAP HANA IMDB (a database running in high-performance memory). The period is 5 minutes by default.
- Log volume: stores the data triggered by an event. When an event, for example, a record or a batch of records are updated, is triggered for the server IMDB, the system will write the latest IMDB data into the log volume.
- Shared volume: stores the SAP HANA installation software and SAP HANA database log files.
- Backup volume: stores SAP HANA database backup files.
- Usr/sap: used to mount to the /usr/sap directory.
- Swap volume: Linux swap space.
Figure 2 shows the deployment flowchart in the single-node scenario where HA is not required.
Figure 2 Single-node scenario where HA is not required
SAP HANA nodes can use Elastic Volume Service (EVS) disks.
The concepts involved in this scenario are the same as those involved in Figure 1. The difference of this deployment scenario is that the backup volume is provided by the SFS.
Figure 3 shows the deployment flowchart.
Figure 3 Single-node scenario where HA is not required