Node Planning

Updated on 2022-03-04 GMT+08:00

View PDF

Before applying for SAP S/4HANA ECSs, evaluate the SAP Application Performance Standard (SAPS) value based on the standard SAP Sizing method. Then apply for the ECSs based on the evaluation results. For details, see SAP Quick Sizer.

For details about the minimum hard disk space, RAM, and minimum software requirements of each component in SAP S/4HANA, see SAP note: 1953429 and SAP Installation Guides.

SAP S/4HANA Node Planning

Follow the descriptions in Table 1 to conduct SAP S/4HANA node planning. HUAWEI CLOUD provides SAP-certified ECSs with various specifications. Configure the actual hardware usage based on the SAP Sizing result.

**Table 1** Recommended SAP S/4HANA node planning
Item	Specification
OS	SUSE Linux Enterprise Server for SAP Applications 12 SP3 SUSE Linux Enterprise Server for SAP Applications 12 SP4 SUSE Linux Enterprise Server for SAP Applications 12 SP5 SUSE Linux Enterprise Server for SAP Applications 15 SUSE Linux Enterprise Server for SAP Applications 15 SP1
Specification	m6.2xlarge.8 (8 vCPUs and 64 GB memory)
Disk	System disk: ultra-high I/O, 100 GB Following the descriptions in Table 3 to plan the data disk created on the ASCS node. After a data disk is created, bind it to the ERS node. Only one system disk needs to be created for the ERS node. NOTE: In the cross-AZ HA scenario, you do not need to create the data disk. EVS disks cannot be shared across AZs. For details about how to create and configure a shared disk in a cross-AZ HA scenario, see Configuring iSCSI (Cross-AZ HA Deployment).

Table 2 describes the specifications of SAP-certified ECSs.

**Table 2** Recommended ECS specifications
ECS Type	Flavor	vCPUs	Memory (GB)
Memory-optimized	m6.large.8	2	16
	m6.xlarge.8	4	32
	m6.2xlarge.8	8	64
	m6.4xlarge.8	16	128
	m6.8xlarge.8	32	256
General computing-plus	c6.large.4	2	8
	c6.xlarge.4	4	16
	c6.2xlarge.4	8	32
	c6.3xlarge.4	12	48
	c6.4xlarge.4	16	64
	c6.6xlarge.4	24	96
	c6.8xlarge.4	32	128

File System Planning

Table 3, Table 4, and Table 5 describe the file system planning.

**Table 3** File system planning
Partition	Capacity (GB)	Mounted To	Description
sda	10	N/A	Used as the SBD disk.
sdb	80	/usr/sap/<SID>/ASCS<##>	Partition of the active node, which is used to install the ASCS instance.
sdc	80	/usr/sap/<SID>/ERS<##>	Partition of the standby node, which is used to install the ERS instance.

NOTE:

In the cross-AZ HA scenario, three ECSs are required and Internet Small Computer System Interface (iSCSI) is used to create a shared disk for Split Brain Detection (SBD). For details, see Configuring iSCSI (Cross-AZ HA Deployment). The disks used to install the ASCS instance and the ERS instance are provided by the SFS Turbo file system. Table 5 describes the planning of the SFS Turbo file system in the cross-AZ HA scenario.

**Table 4** Planning of the SFS Turbo file system
Name	Total Capacity (GB)	Mounted To	Description
sapmnt	100GB	/sapmnt	Shared to all nodes in the SAP S/4HANA system
usrsapsys	10	/usr/sap/<SID>/SYS	Shared to all nodes in the SAP S/4HANA system
sapmedia	100	/sapcd	Shared to all nodes in the SAP S/4HANA system

**Table 5** Planning of the SFS Turbo file system in the cross-AZ HA scenario
Name	Total Capacity (GB)	Mounted To	Description
sapmnt	100GB	/sapmnt	Shared to all nodes in the SAP S/4HANA system
usrsapsys	10	/usr/sap/<SID>/SYS	Shared to all nodes in the SAP S/4HANA system
sapmedia	100	/sapcd	Shared to all nodes in the SAP S/4HANA system
ASCS	80GB	/usr/sap/<SID>/ASCS<##>	Shared to the active node, which is used to install the ASCS instance.
ERS	80GB	/usr/sap/<SID>/ERS<##>	Shared to the standby node, which is used to install the ERS instance.

Parent topic: Resource Planning

Previous topic: Resource Planning

Next topic: Network Plane Planning

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot