In this example, two virtual machines (VMs) with Windows Server 2016 (uswiniqdb1 and uswiniqdb3) are configured with Windows Server Failover Cluster. To understand more about failover cluster resources/resources type and what they do, see Windows Server 2016/2019 Cluster Resource / Resource Types. Instead Generic Service (clusres2.dll) resource type can be leveraged, which manages SAP IQ database service. But for SAP IQ, there is no such dedicated resource type available. Traditionally for SAP NetWeaver running on highly available WSFC, a SAP Resource type is implemented using a dynamic library plug-in DLL (saprc.dll) called cluster resource DLL, which is loaded by the Windows cluster resource monitor process. If a node fails, WSFC calculates the number of failures that can occur and still maintain a healthy cluster to provide applications and services. A failover cluster is a group of 1+n independent servers (nodes) that work together to increase the availability of applications, database, and services. Windows Server Failover Cluster (WSFC) is the foundation of a high availability for critical applications on Windows. This blog will provide insights into a SAP IQ NLS high availability architecture on Windows Server. This blog discusses a SAP IQ NLS high available solution using Azure shared disk on Windows Server 2016. But SAP IQ NLS high availability can be achieved using custom solutions, which may require additional configuration or open-source component like Pacemaker, Microsoft Windows Server Failover Cluster, shared disk etc. On the other side, SAP does not provide any features or procedures to run the SAP IQ simplex architecture in a high availability configuration. Technically SAP IQ high availability can be achieved using the IQ multiplex architecture, but the multiplex architecture does not suffice our requirement for NLS solution. But for the NLS solution, only the simplex architecture is available/evaluated. SAP IQ supports both a simplex and a multiplex architecture. The integration of SAP IQ makes it possible to separate frequently accessed data from the infrequently accessed data, thus resulting in less resource demands for the BW system. The adapter of SAP IQ as a near-line solution is delivered with the SAP BW system. To reduce the size of HANA hardware, customer can leverage an option to migrate their data to near-line storage (NLS). Over the years, the size of SAP BW system database grew exponentially, which leads to increase in hardware cost when running the system on HANA.
0 kommentar(er)
