Recommended ECS Planning
This section describes the planning of SAP NetWeaver ECSs and NAT server (SAP GUI).
The flavors are only for reference. The ECS specifications are recommended examples. Choose one based on the SAP Sizing results.
Type |
Flavor |
vCPUs |
Memory (GB) |
---|---|---|---|
High-Performance computing H1 ECS |
h1.xlarge.4 |
4 |
16 |
h1.2xlarge.4 |
8 |
32 |
|
h1.4xlarge.4 |
16 |
64 |
|
h1.8xlarge.4 |
32 |
128 |
|
Memory-optimized M3 ECS |
m3.large.8 |
2 |
16 |
m3.xlarge.8 |
4 |
32 |
|
m3.2xlarge.8 |
8 |
64 |
|
m3.3xlarge.8 |
12 |
96 |
|
m3.4xlarge.8 |
16 |
128 |
|
m3.6xlarge.8 |
24 |
192 |
|
m3.8xlarge.8 |
32 |
256 |
|
General Computing-plus ECS |
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 |
|
Memory-optimized M6 ECS |
m6.large.8 |
2 |
16 |
m6.xlarge.8 |
4 |
32 |
|
m6.2xlarge.8 |
8 |
64 |
|
m6.3xlarge.8 |
12 |
96 |
|
m6.4xlarge.8 |
16 |
128 |
|
m6.6xlarge.8 |
24 |
192 |
|
m6.8xlarge.8 |
32 |
256 |
|
m6.16xlarge.8 |
64 |
512 |
Plan the data for each ECS by referring to Table 2. For details about the hardware configuration, see section SAP NetWeaver ECS Hardware Evaluation (SAP Sizing).
Node |
Specifications |
---|---|
SAP NetWeaver ECS planning in the standard deployment mode |
Recommended configurations:
|
SAP NetWeaver ECS planning in the distributed deployment mode |
Recommended configurations:
|
SAP NetWeaver ECS planning in the distributed HA deployment mode |
Recommended configurations:
|
NAT Server |
|
Table 3 and Table 4 list the file system planning in the distributed HA deployment mode.
Partition |
Capacity (GB) |
Mounting Directory |
Description |
---|---|---|---|
sda |
10 |
N/A |
Used as the SBD disk. |
sdb |
80 |
/usr/sap/<SID>/ASCS<##> |
Partition of the active ASCS node, which is used to install the ASCS instance. |
sdc |
80 |
/usr/sap/<SID>/ERS<##> |
Partition of the standby ASCS node, which is used to install the ERS instance. |
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.
Name |
Total Capacity (GB) |
Mounting Directory |
Description |
---|---|---|---|
sapmnt |
100 |
/sapmnt |
Shared to all nodes in the SAP NetWeaver system |
usrsapsys |
10 |
/usr/sap/<SID>/SYS |
Shared to all nodes in the SAP NetWeaver system |
sapmedia |
100 |
/sapcd |
Shared to all nodes in the SAP NetWeaver system |
Name |
Total Capacity (GB) |
Mounting Directory |
Description |
---|---|---|---|
sapmnt |
100 |
/sapmnt |
Shared to all nodes in the SAP NetWeaver system |
usrsapsys |
10 |
/usr/sap/<SID>/SYS |
Shared to all nodes in the SAP NetWeaver system |
sapmedia |
100 |
/sapcd |
Shared to all nodes in the SAP NetWeaver system |
ASCS |
80 |
/usr/sap/<SID>/ASCS<##> |
Shared to the active ASCS node, which is used to install the ASCS instance. |
ERS |
80GB |
/usr/sap/<SID>/ERS<##> |
Shared to the standby ASCS node, which is used to install the ERS instance. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot