Skip to Content
author's profile photo Former Member
Former Member

SAP system over MS SQL Failover Cluster


I´m with big doubts regarding the SAP installation that we want to perform!

We want to install a SAP system (ERP) in one application server/host (message server) and the database of this SAP system in other host (Database server) configured with MS SQL Failover Cluster.

It´s possible to do that? Because I want to perform a SAP distributed installation but the database is in MS SQL Failover Cluster... so my question is what is the installation option that I must choose in Software Provisioning Manager?

Best regards,

samid raif

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • Posted on Feb 12, 2015 at 07:27 PM

    Hello Samid,

    Of course it is possible to install SAP system on MS Failover Cluster. And I advise you to install your production system on a cluster /High Available) system.


    And in this guide follow planning, preperation, Installation and Post Installation sections in order.

    The information about failover cluster is in section "8 High Availability with Microsoft Failover Clustering".

    Below figure is taken from the mentioned guide. You can built up your system like this. DB runs on one node and SAP MS runs on another node of the cluster.


    Yuksel AKCINAR

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Feb 12, 2015 at 09:19 PM

    Hi Samid

    Yes, You can install the CI, DI & DB in all three different systems

    1. CI & DB - you can refer the SAP distributed installation guide. During the SAP installation DB you have to select the Cluster Virtual name.

    2. DI normal additional application server installation steps

    In our environment we have do it all Dev & Qty system single DB in the cluster.



    Add a comment
    10|10000 characters needed characters exceeded

    • Hello samid,

      Yes, of course it's possible.

      You have to choose the "High Availability" option for the phase "Database Instance" in the database server (with the Microsoft Failover Cluster), and choose the "Distributed Installation" option for the all the other phases "ASCS Instance" and "Primary Application Server Instance" in the application server (where you want to install the SAP instances).

      Best regards,

      João Dimas

  • Posted on Feb 16, 2015 at 01:29 PM

    Hello Hamid,

    Why would you do such a configuration ? The reason I think ASCS (or SCS) is included in the cluster is to ensure that when your DB fails over to secondary node, your message server and enqueue information fails over too, to maintain consistency, since although at higher level the cluster name maybe used for db connection. I doubt that at operating system call level cluster name/groups may not be used, all files are treated as file handle numbers at operating system level.

    I would suggest you raise this to SAP via OSS and ask them for advice.



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Feb 24, 2015 at 01:28 PM

    Hi all,

    The scenario described by Samid is valid, and there is no need to mix the 2 SWPM installation methods. You should use only the "Distributed Installation" method.

    I think that you biggest concern was related to the fact that on a SQL Server AlwaysON Availability Group, there is no shared volumes and in case of failover how SAP folders will be replicated, right?

    I just finished a lab to probe that there is no SAP folders/files installed by SWPM on the SQL Server nodes. Please see my document here: SAP NetWeaver on SQL Server 2012 AlwaysON for HA and DR



    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.