!IMPORTANT: “In keeping with industry best practices, SIOS is no longer recommending installing the NFS servers/clients on the same nodes as the SAP services when setting up an SAP system (also known as “loopback configuration”). Instead, we will move towards recommending using alternate configurations such as:
• EFS in AWS
• Azure Premium File Shares with NFS
• Google NFS Share
• NFS as separate cluster
Going forward, we will not support new installations using “loopback configurations”. Existing customers will be supported to the extent that we can, if the issue is within the SIOS software and will be encouraged to move to an alternate configuration. In the next release, existing configurations will not be supported.
In this section we will create highly-available NFS shared file systems which will be mounted on each node hosting an SAP instance. Typical file systems to be shared between systems in a highly-available SAP AS ABAP environment include:
- /sapmnt/<SID>
- /usr/sap/trans
- /usr/sap/<SID>/ASCS<InstNum>
- /usr/sap/<SID>/ERS<InstNum>
See Setting up File Systems for a High-Availability System for more details.
*Note: Since the instance-specific file systems (i.e., /usr/sap/<SID>/ASCS<InstNum> and /usr/sap/<SID>/ERS<InstNum>) only need to be mounted on the system where the corresponding SAP instance is running, it is possible to replicate them using SIOS DataKeeper rather than sharing them via NFS.
*Note: These shared file systems support the highly-available AS ABAP deployment. Additional database-related file systems will vary depending on the backend database platform chosen.
The recommended implementation for exporting the NFS shares varies by cloud platform. Please follow the steps provided in the section corresponding to your cloud platform:
Post your comment on this topic.