Sample Picture – Single SAP system in the MSCS Cluster
6 Node cluster configuration – Windows 2003 Enterprise edition.
This is one of the SAP’s recommended HA configuration.
Node1 – Oracle 10G installed – 6GB RAM,Dual Xeon 16 cores – Oracle Binaries in F Local Drive and Datafiles/logfiles/controlfiles in O Shared drive for Oracle Datafiles – Called O Drives 300GB
Node2 – Oracle 10G installed – 6GB RAM,Dual Xeon 16 cores – Oracle Binaries in F Local Drive and Datafiles/logfiles/controlfiles in O Shared drive for Oracle Datafiles – Called O Drives 300GB
Node1 – First MSCS node – Running SCS – 4GB RAM – Shared Drive for SAP mount point – Called S Drive – 100GB
Node2 – Second MSCS node – Standby SCS – 4GB RAM – Shared Drive for SAP mount point –
Called S Drive
Node3 – MS Active Directory – Primary server – 2GB RAM – Local Drive
Node4 – SAP First DI instance – Local Drive F
Node5 – SAP Second DI instance – Local Drive F
You can further enhance this HA architecture more protection.
Enqueue replication server for HA.
LBR to Load balance between available DI instances.
Oracle RAC for HA and scalling purpose.
SAP Services running on the First Node (SUBSCRIBE) and MSCS running on Second Node (ECC6)
Sample Picture – Multiple SAP systems in the MSCS Cluster
1.Shared Drives for Oracle and SAP mount point
2.MSCS installed and fully functional.
3.MS AD installed and fully functional.
4.DNS configured for all hosts
5.Linkd installed and configured if Multiple SAP to be suppored in the MS Cluster.
SAP NetWeaver 2004s SR2 and higher ABAP+Java (kernel 7.00)used.
6.Oracle Fail safe – Optional
SAP services moving to the second Node
SAP services completely moved to the second Node
All nodes are already configured with Linkd shared mount points.
1.Install Oracle binaries on node1
2.Install SAP SCS on the First node- node2 – instance # 00.S Drive
3.Install ASCS on the First node – node2 – instance # 01. S Drive
3.SAP configuration prepare on the first SCS node – node2
4.Configure the second node for the MSCS – node3
5.Install Database instance – O Drive
Test the Fail over by moving MSCS groups from node2 to node 3. All the services SCS,ASCS and Oracle will be move to the second stand by node2.
6.Install the first DI instance on node5
7.Install the second DI instance on node6
8.Check the SAP connectivity using the two DI with SAP system on Primary (active) cluster.
9.Switch over the SAP system from node2 to node3.repeat the step 8.Since the Network name (say sapcluster) and IP also switches to node3 , there should not be any problem in connecting.
10.Configure the SAP logon group for the two DI instances
11.For more HA you can configure enqueue replication server.
12.Complete the TMS and other initial configurations
13.Backup the SAP instance using BRTOOLS tools
This completes the basic overview about the SAP Active/Passive cluster implementation.