SAP Basis Tech Supports

Symptom
As of which SAP / R/3 release and in which configurations does SAP support the Microsoft Cluster Server (MSCS)?
Other terms
MSCS
Reason and Prerequisites

SAP and Microsoft Cluster Server (MSCS)
SAP generally only supports configurations that can be created with SAPinst and without making manual changes. This concerns the operation of the dual-node cluster, where the SAP central instance operates on one node and the database instance operates on the other.
Support refers to the software components made available by SAP (for example, installation routines). Technical support services for all other components (hardware, OS, and so on) must be provided by the respective manufacturer. SAP only documents and supports SAP’s own interfaces or configurations. SAP partners can implement other configurations or include alternative HA products on this basis. Support is delievered by partners. SAP does not analyze problems with these additional HA solutions, the basis function is supported by SAP however. SAP retains the right to request that the HA solution be deactivated to adhere to the time limit for solving prio 1 problems.
MSCS cluster solutions outside of SAP ERP systems
The SAP application server and the database can also be operated in clusters in certain other SAP solutions apart from SAP ERP (for example, CRM) (Note 437406). This way, high availability is achieved for both the central instance and the database. However, note that this does not guarantee high availability for the entire system landscape. For further system components apart from the application server, high availability must be created in another way, for example, by means of a redundant installation (as an example, see the ITS below).
Hardware and software requirements
You must meet the following hardware/software requirements if you want to use the MSCS together with SAP components (extract):
Windows 2000 Advanced ServerWindows 2000 Datacenter Server
The database and SAP releases that are released Windows 2000, the cluster service from Windows 2000 can be used. However, two Microsoft hotfixes must be implemented. Note the remarks made below.Windows 2003 Server Enterprise EditionWindows 2003 Server Datacenter EditionHardware cluster certified by Microsoft for MSCS. This means:Every single node must be certified for the hardware.You must use a shared disk subsystem that tolerates errors.A certified SAP consultant must carry out the installation.
SAP Internet Transaction Server
The SAP Internet Transaction Server (ITS) was not released for MSCS, since ITS is not a “Single Point of Failure” (SPOF). A ‘Failover-Cluster’ is therefore not a good way to improve the availability of the ITS.
Instead of this, since 4.6D Compilation 4, what is known as a “Watchdog” is delievered with the ITS, which, together with the Microsoft “Windows Load Balancing Server” increases the availability and scalability of the ITS.
You can find further measures for scaling the ITS and increasing its availability in the “Network Integration Guide”.
Alternative cluster solutions
Alternatively, other forms of clustering/high availability are also possible but installation and support must be provided by the SAP HA solution or implementation partner. SAP only supports the standard configurations detailed above on Windows and reserves the right to require that other high-availability solutions be deactivated when support is required.
Solution
Release planning for new installations (3.1I – 4.7)
(organized according to databases)

32 Bit

————————————————————————
OS DB 3.1I 4.0B@ 4.0BSR1 4.5A 4.5B 4.6 4.7
————————————————————————
W2K/Intel- Oracle 8.1.7 X@ – X@ – – X@
W2K/Intel- Oracle 9.2.0 X@ – X@ – X@ X@ X
W2K/Intel- MSSQL 7.0 – X@ X@ X@ X@ X@
W2K/Intel- MSSQL 2000 – – X@ X@ X@ X@ X
W2K/Intel- DB2 UDB – – – – – X X
W2K/Intel- Informix – – – – – X@ X
————————————————————————
OS DB 3.1I 4.0B@ 4.0BSR1 4.5A 4.5B 4.6 4.7
————————————————————————
W2003/Intel- MSSQL 2000 – – X X X X X
W2003/Intel- Oracle 9.2.0 – – X@ – X@ X@ X@
W2003/Intel- DB2 UDB – – – – – X X

Remarks (@) for SAP releases on 32-Bit:
1. For “4.0B SR1″, the MSCS support is contained in the installation package. Refer to SAP Note 138765 in addition.For 4.0B/Informix you can find the files required for MSCS support on SAP Service Marketplace.
For information about terminology and the installation options under 4.0B, see Note 138765.In Release 3.1I and as of Release 4.5A, MSCS support is supplied in an installation kit.2. We recommend that you use MS SQL Server 2000 instead of MS SQL Server 7.0. See also Microsoft Knowledge Base Article 274446.
The installation guide for Cluster Support for Release 4.0B and 4.5A under SQL Server 7.0 is available on SAP Service Marketplace. http://service.sap.com/instguides -> SAP Business Suite Applications -> SAP ERP -> SAP R/3 -> -> 4.5A -> Conversion to Microsoft Cluster Server: MS SQL Server
For Release 3.1I use the R/3 installation guide and the conversion CD SQL Server 6.5 / 7.0 that was sent to you.
Also refer to Notes 140960 (3.1I), 138765 (4.0B) and 117305 (4.5A).
3. Generally, in SAP R/3 Release 3.X, you can use a 3.1I kernel in connection with 3.0F or higher. However, any restrictions described in this note are still valid.4. On the 3.1I international installation CD you will find the following:Downward-compatible kernelDatabase (cluster-enabled)Migration guideline for the migration of systems without MSCS5. On Windows 2000 you need at least Service Pack 4.6. On Windows 2000, only Oracle 8.1.6 (or higher) is released. Therefore you can only install SAP releases released for this database version. At present, these are SAP 4.6C SR1, 4.6C SR2, 4.0B_COM and 3.1I SR1. Support for 4.5B and 4.6B will follow if necessary.7. MS SQL Server 2000 on MSCS on Windows 2000 is supported for various SAP releases. The installation is described in a document that is available on SAP Service Marketplace under http://service.sap.com/msplatforms ->SQL Server -> “Installation of MS SQL 2000 in an SAP Environment”.8. SAP DB is only available as of Version 7.2. SAP DB 7.2 is used by default as of R/3 Version 4.6C. SAP DB 7.2 is currently not supported for R/3 Versions 4.5A/B, 4.6A/B. MSCS support is contained in the installation package as of R/3 4.6C SR1. For SAP DB/MaxDB installations as of R/3 Version 4.7, refer to Notes 760137 and 728879.9. If MSCS is to be used on Windows 2000, Informix Version 7.31TD2X6 or higher must be applied, since only these versions have been released for Windows 2000 Cluster.10. You can use the CD from R/3 Enterprise 4.7 to cluster the Web Application Server 6.20. At present, this is only possible for SQL Server (Note 496210) and Oracle (Note 496227).11. Oracle Failsafe Version for Oracle 9.2.0: 3.3.312. Oracle 9.2.0.3 (Oracle 9.2.0 plus Patchset 9.2.0.3 or higher) is a prerequisite from supported by Windows 2003.13. For installation support for Oracle 9.2.0 see Note 578004.14. To operate Informix and MSCS on Win2000, Win2000 SP4 must be installed.15. All of the above-mentioned availability specifications refer solely to 32-bit versions.

Release planning for new installations (3.1I – 4.7)
(organized according to databases)

64 Bit

————————————————————————
OS DB 4.6c 4.7
————————————————————————
W2003/IA64 – SQL 2000 X X*
W2003/IA64 – Oracle 9.2.0 X* X*
W2003/x64 – SQL 2005 X*

Remarks (*) for 64-bit SAP releases:
1. Use the MSCS installation options that are on the SAP NetWeaver 04 SR 1 Installation Master CD/DVD during the MSCS installation. Do not use the MSCS options on the installation CD for your SAP Release.2. Oracle 9.2.0: In a 64-bit system, first install the 64-bit Fail Save Server software. Further information about installing this software is available in the installation guide: You can find further information about the installation in the installation guide: “SAP Web Application Server 6.40 SR1 on Windows : Oracle, Part II”, in the chapter “Microsoft Cluster Installation”. The guide is available on SAP Service Marketplace.3. You must use the 51031444 CD to install Enterprise 4.7 on an x64 platform with SQL Server 2005. This CD installs the central instances and database instances. To convert the A and B nodes in MSCS, use the SAP NetWeaver 04 SR1 installation master CD or DVD.