Installation of an SAP NetWeaver ERP based on WSFC with clustered ASCS and SAP MaxDB

This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Community Hub.

Installation of an SAP NetWeaver ERP6/EHP8 system based on WSFC with highly available ASCS and SAP MaxDB with Azure shared disks.

 

The steps for creating the VMs with Azure shared disks, join them to a Windows AD, creation of the WSFC and the Cloud Witness are described here Setup of SAP Content Server 7.54 with MaxDB in a WSFC environment based on Azure shared disks 

This documentation focuses on the SWPM based steps, the creation of the Internal Load Balancer (ILB), Probe Ports and DNS settings.

The following screen shows the cluster with 3 shared cluster disks. Additionally, there is one local disk per instance (MaxDB, ASCS and ERS). The conversion from ERS to ERS2 is not part of this blog. It's done according to SAP Note 2639281. However, the preparation steps are shown. The used values for the blog screenshots are mentioned in rounded bracket ( ).

 

SteffenMueller_0-1683231439617.png


Create Azure Internal Load Balancer

SteffenMueller_1-1683231467910.png

 

SteffenMueller_2-1683231496373.png

 

In this step three virtual host names and probe ports are created. ec9db Is used for the MaxDB database instance, ec9ascs is used for ASCS and ec9ers is defined for the potential later conversion of the locally installed ERS to a clustered ERS2 instance.

SteffenMueller_3-1683231568312.png

 

SteffenMueller_4-1683231592257.png
Health Probe for the MaxDB instance.

 

SteffenMueller_5-1683231618244.png

Health Probe for the ASCS instance.

 

SteffenMueller_6-1683231649868.png

Health Probe for the ERS2 instance.

 

SteffenMueller_7-1683231670219.png
Overview of the created Health Probes.

 

Use SWPM to create the First Cluster Node

SteffenMueller_8-1683231696131.png
Select EHP8 for SAP ERP 6.0 ABAP - MaxDB - Installation - High Availability - First Cluster Node

 

SteffenMueller_9-1683231724542.png
Choose a local drive for the installation of SAP components like SAPHOSTAGENT and the Enqueue Replication Server (ERS). Depending on your policies this can be the OS disk (C:) or an additionally installed local disk. The same setup must be done on the additional cluster nodes.

 

SteffenMueller_10-1683231750674.png
Choose Cluster Shared Disk for the cluster share configuration since Azure shared disks are used for this installation.

 

SteffenMueller_11-1683231774947.png
Provide the SID (EC9), the virtual hostname (ec9ascs) and the cluster drive (Cluster Disk 1) for the ASCS instance.

 

SteffenMueller_12-1683231794822.png
Provide the instance number (00) for the ASCS instance.

 

SteffenMueller_13-1683231814666.png
Provide the hostname (mswinnode92) and instance number (10) for the locally installed ERS instance.

 

Create Probe Port for ASCS

SteffenMueller_14-1683231836011.png

This creates the Probe Port for the ASCS instance.

SteffenMueller_15-1683231859280.png

Output of the successfully executed Probe Port PowerShell script.

 

Install MaxDB Software

SteffenMueller_16-1683231880397.png
Select EHP8 for SAP ERP 6.0 ABAP - MaxDB - Installation - High Availability - SAP MaxDB Database

 

SteffenMueller_17-1683231931144.png
To identify already installed components, the UNC path to the profile directory must be supplied.

 

SteffenMueller_18-1683231945042.png
Provide the Database SID (EC9) together with the virtual hostname.

SteffenMueller_19-1683231964923.png
Provide the Database Software destinations for local and clustered components. The MaxDB is initially installed locally (E:) and the relevant components for the cluster operation are copied to clustered disks (Cluster Disk 2) by SWPM automatically. 

 

SteffenMueller_20-1683231984050.png
Provide the passwords for the DB admin users superdba and control.

 

SteffenMueller_21-1683232006530.png
Provide the location of the MaxDB installation media.

 

SteffenMueller_22-1683232020760.png
Provide the basic parameters for MaxDB.

 

SteffenMueller_23-1683232037452.png
Choose the location of the MaxDB Log Volumes (Cluster Disk 2).

 

SteffenMueller_24-1683232052272.png

Choose the location of the MaxDB Data Volumes (Cluster Disk 3).

 

SteffenMueller_25-1683232073614.png

Provide the number and size of the individual MazDB Log Files. 

 

SteffenMueller_26-1683232089075.png

Provide the number and size of the individual MazDB Data Files. 

 

Create Probe Port for the MaxDB instance

Use the following PowerShell script to create the Probe Port (62300) for the MaxDB instance.

 

$ProbePort = 62300 # ProbePort of the Azure internal load balancer Clear-Host $SAPClusterRoleName = "MaxDB" $SAPIPresourceName = "MaxDB IP-Address" $SAPIPResourceClusterParameters = Get-ClusterResource $SAPIPresourceName | Get-ClusterParameter $IPAddress = ($SAPIPResourceClusterParameters | Where-Object {$_.Name -eq "Address" }).Value $NetworkName = ($SAPIPResourceClusterParameters | Where-Object {$_.Name -eq "Network" }).Value $SubnetMask = ($SAPIPResourceClusterParameters | Where-Object {$_.Name -eq "SubnetMask" }).Value $OverrideAddressMatch = ($SAPIPResourceClusterParameters | Where-Object {$_.Name -eq "OverrideAddressMatch" }).Value $EnableDhcp = ($SAPIPResourceClusterParameters | Where-Object {$_.Name -eq "EnableDhcp" }).Value $OldProbePort = ($SAPIPResourceClusterParameters | Where-Object {$_.Name -eq "ProbePort" }).Value $var = Get-ClusterResource | Where-Object { $_.name -eq $SAPIPresourceName } Write-Host "Current configuration parameters for SAP IP cluster resource '$SAPIPresourceName' are:" -ForegroundColor Cyan Get-ClusterResource -Name $SAPIPresourceName | Get-ClusterParameter Write-Host Write-Host "Current probe port property of the SAP cluster resource '$SAPIPresourceName' is '$OldProbePort'." -ForegroundColor Cyan Write-Host Write-Host "Setting the new probe port property of the SAP cluster resource '$SAPIPresourceName' to '$ProbePort' ..." -ForegroundColor Cyan Write-Host $var | Set-ClusterParameter -Multiple @{"Address"=$IPAddress;"ProbePort"=$ProbePort;"Subnetmask"=$SubnetMask;"Network"=$NetworkName;"OverrideAddressMatch"=$OverrideAddressMatch;"EnableDhcp"=$EnableDhcp} Write-Host $ActivateChanges = Read-Host "Do you want to take restart SAP cluster role '$SAPClusterRoleName', to activate the changes (yes/no)?" if($ActivateChanges -eq "yes"){ Write-Host Write-Host "Activating changes..." -ForegroundColor Cyan Write-Host write-host "Taking SAP cluster IP resource '$SAPIPresourceName' offline ..." -ForegroundColor Cyan Stop-ClusterResource -Name $SAPIPresourceName sleep 5 Write-Host "Starting SAP cluster role '$SAPClusterRoleName' ..." -ForegroundColor Cyan Start-ClusterGroup -Name $SAPClusterRoleName Write-Host "New ProbePort parameter is active." -ForegroundColor Green Write-Host Write-Host "New configuration parameters for SAP IP cluster resource '$SAPIPresourceName':" -ForegroundColor Cyan Write-Host Get-ClusterResource -Name $SAPIPresourceName | Get-ClusterParameter }else { Write-Host "Changes are not activated." }

 

 

SteffenMueller_27-1683232111245.png
Output after the successful Probe Port creation.

SAP Max DB Configuration

 

This is the installation of MaxDB on the Second Cluster Node. This step must be performed on the Second/Additional Server Node.

 

SteffenMueller_28-1683232128761.png

Select EHP8 for SAP ERP 6.0 ABAP - MaxDB - Installation - High Availability - SAP MaxDB Database Configuration

 

SteffenMueller_29-1683232151012.png

Provide the location of the MaxDB installation media.

 

SteffenMueller_30-1683232165428.png

Use the same input here as used for the First Cluster Node installation assuming the local drive uses the same drive letter (E:).

 

SteffenMueller_31-1683232183636.png
Since this is an initial local installation, you must provide the same passwords for the MaxDB admin users superdba and control which have been used on the First Cluster Node. Don't touch any of the created MaxDB cluster resources. They will be handled by SWPM.

 

Create Database Instance

 

SteffenMueller_32-1683232204075.png

Select EHP8 for SAP ERP 6.0 ABAP - MaxDB - Installation - High Availability - Database Instance

 

SteffenMueller_33-1683232224457.png

To identify already installed components, the UNC path to the profile directory must be provided.

 

SteffenMueller_34-1683232243436.png

Confirm the preselected Database SID (EC9) and the virtual hostname (ec9db) for the database cluster role.

 

SteffenMueller_35-1683232266662.png
Provide the location of the Database Export (Installation Export 1 ECC 6.0 EHP8).

 

SteffenMueller_36-1683232282897.png
Provide the passwords for the MaxDB users supedba and control.

 

SteffenMueller_37-1683232300594.png
Provide a password for the ABAP schema user (SAPEC9).

 

SteffenMueller_38-1683232316253.png

Confirm the drive letters for the MaxDB client installation.

 

Install Additional Cluster Node

This step must be performed on the Second/Additional cluster node. SWPM handles the identification and move of existing cluster resources.

 

SteffenMueller_39-1683232332805.png

Select EHP8 for SAP ERP 6.0 ABAP - MaxDB - Installation - High Availability - Additional Cluster Node

 

SteffenMueller_40-1683232350979.png

Choose the same drive letter (E:) as for the First Cluster Node.

 

SteffenMueller_41-1683232366245.png

Provide the passwords for user <sid>adm and SAPService<SID> (ec9adm and SAPServiceEC9).

 

SteffenMueller_42-1683232383760.png
Provide the instance number (10) and hostname for the local ERS instance on the Second/Additional Node.

 

SteffenMueller_43-1683232399937.png

Confirm the automatic restart option.

 

SteffenMueller_44-1683232423403.png
Disk configuration for Primary Application Server. Here with drive E: as local drive for SAP components.

 

Use SWPM for Primary Application Server installation

SteffenMueller_45-1683232440899.png
Select EHP8 for SAP ERP 6.0 ABAP - MaxDB - Installation - High Availability - Primary Application Server Instance

 

SteffenMueller_46-1683232459653.png
To identify already installed components, the UNC path to the profile directory must be provided. Additionally, the local drive (F:) for the application server instance must be specified,

 

SteffenMueller_47-1683232485637.png

 

Pride message server port (3600).

 

SteffenMueller_48-1683232502421.png

Validate and confirm the drive letters for the MaxDB client installation.

 

SteffenMueller_49-1683232515671.png
Provide the instance number and hostname for the Primary Application Server (00 and mswinnode94).

 

SteffenMueller_50-1683232532932.png

Confirm ABAP Message Server Ports and Transport Host location.

SteffenMueller_0-1683900940586.png

 

SteffenMueller_1-1683900969770.png

This concludes the installation.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

This site uses Akismet to reduce spam. Learn how your comment data is processed.