Description of the RKS Procedure
To keep any adverse effects on business operations to a minimum when importing a new kernel version, instances are restarted one after the other. This means that during the RKS procedure, at least one application server instance is always available for business operations. The order in which individual instances are restarted enables you to import a new kernel version without system downtime. Details of the RKS procedure are described below.
Component | Virtual Hostname | Operating System | HA Cluster | CPU/RAM | HDD |
SAP ASCS/ERS Node 1 | ozsap-ascs | SLES for SAP 15 SP4 | Yes | 1CPU/2Gb | The disk for the ASCS and ERS instances need to be shared and assigned to the cluster nodes ozsap-ascs and ozsap-ers /usr/sap/SID/ASCS00 - 10Gb /usr/sap/SID/ERS10 - 10Gb SBD DISk - 7Mb |
SAP ASCS/ERS Node 2 | ozsap-ers | SLES for SAP 15 SP4 | Yes | 1CPU/2Gb | |
SAP Primary Application Server (PAS) | ozsap-app1 | SLES for SAP 15 SP4 | No | 2CPU/8Gb | |
SAP Additional Application Server (AAS) | ozsap-app2 | SLES for SAP 15 SP4 | No | 2CPU/8Gb | |
SAP Database(DB- SyBase) | ozsap-db | No | 4CPU/16GB | ||
10CPU/36Gb |
We can combine DB and APP1 + NFS Server on one VM
0 Comments