With SUSE High Availability Extension (HAE), we can manage MaxDB database resources and build an automated, highly available solution. Application layer is managed by the SAP’s sapcontrol service. In this blog, we are using SAP MaxDB database as the storage layer. The storage layer could either be a file system or MaxDB database.
The SAP Content Server consists of an application layer and a storage layer. This includes identifying its single points of failure and building a resilient system spread across Availability Set or Availability Zones. To match the Availability SLA for the SAP Content Server with that of the OLTP systems on Microsoft Azure, we must understand the architecture of SAP Content Server. Also, MaxDB database can be replaced with File System as SAP content server repository which is not covered in this blog. Though we are using SUSE High Availability Extension tool set (pacemaker) for this blog, similar set up can also be achieved for Red Hat Enterprise Linux based systems. It uses SUSE High Availability Extension tool set (Pacemaker) for the cluster solution. In this blog, we will provide steps to configure Highly available SAP Content Server 7.53 with MaxDB database version 7.9 on SUSE Linux in Microsoft Azure Cloud using Azure NetApp Files (ANF) as storage platform for database.
0 kommentar(er)
