Alternatively, the NFS shares may be mounted as Network Attached Storage (NAS), and these mount points may also be protected by your high-availability software.
In these cases, the SAP file systems can be mounted on each cluster node using the service, which may in turn be protected by your high-availability software if it offers this functionality.
Once you have completed the process to upgrade your SAP cluster to version 2 of the Enqueue Server Framework, you can then set up shared file systems for ASCS and ERS. Setting Up Shared File Systems for ASCS and ERS So another important step is to follow any vendor-specific SAP Notes provided by your high-availability software provider. There may be additional configuration steps that must be performed within the high-availability software itself. The ENSAv2 documentation link within this note provides for a thorough explanation of the upgrade process. When completing the upgrade process, it is also important to follow SAP Note 2711036, which can be accessed at and pertains to using Standalone Enqueue Server 2 in a high-availability environment. You should then make any necessary vendor-specific changes within your high-availability software that are required to support the upgraded ASCS and ERS instances. Edit the ASCS and ERS instance profiles as documented by SAP to use the new binaries and instance parameters for Enqueue Server and Replication Server version 2.The details of this step will depend on the file-sharing mechanisms in use. If the ERS instance was previously installed locally on each cluster node, a new shared ERS file system may need to be created.Perform a rolling kernel switch to a version of the SAP kernel that supports version 2 of the Standalone Enqueue Server Framework (i.e., SAP kernel 7.51 or later).If you decide to upgrade to version 2 of the Standalone Enqueue Server Framework, which is the recommended approach, here are the basic high-level steps to follow: Upgrading to Version 2 of the Standalone Server Framework This is critical because processes from different versions are not compatible with each other. The versions for the Enqueue Server and Replication Server must match. ERSv2: enq_replicator, Enqueue Replicator 2.Here are the process-name outputs you will see depending on which version of the Enqueue Server you are using for each ASCS instance:Īnd here are the process-name outputs for each version of the Replication Server for each ERS instance: Call… sapcontrol -nr -function GetProcessList.Switch to the SAP administrative user adm, where is the lower-case SAP System Identifier for the SAP installation:.To confirm the version number, view the output for each SAP instance and follow these two steps: You might also want to read: It’s 6 Years From Now: Do You Know Where Your SAP S/4HANA Migration Is? If you initially installed your SAP system using SAP kernel 7.53 or later, version 2 of the Standalone Enqueue Server Framework is installed by default. If you are on version 1, it’s best to upgrade to version 2.
How to create shared file systems for ASCS and Enqueue Replication Server instancesīefore undertaking these two tasks, first determine the version number of Standalone Enqueue Server Framework installed on your SAP clusters.How to test ASCS clusters for Enqueue lock table consistency.This article provides technical guidance on two key steps in the process to implement high availability for SAP ERP systems:
Power outages will occur, and a natural disaster may strike at any time.
But the importance of high availability in keeping companies “open for business” can’t be overstated. Implementing high-availability capabilities for SAP ERP systems can be a complex undertaking.