Skip to Content

Install a non-clustered SAP instance on a Windows cluster

Any SAP installation uses a sapmnt share of course. On a Windows cluster, this needs to be set up as a clustered fileshare with a virtual hostname/IP. Has anyone managed to install a non-clustered SAP system on a server that is a cluster node that co-exists with a clustered SAP installation? This in effect would mean you have two sapmnt shares on the same Windows server - one a local fileshare, one a clustered fileshare.

So let's say we have D11 installed on a 2-node Windows cluster. It is properly installed with the ASCS and ERS instances being installed as part of the SAP cluster service group and on a clustered disk, with sapmnt created on that as a clustered file share.

We also have D12, which is installed on a local disk on node A. That local disk has a local fileshare called sapmnt that D12 uses.

Ignore for a second the questions about why you would want to do this :-)

I've actually got this much working, but my issue is when I fail over from node A to node B or vice-versa. When the clustered SAP system starts back up, sapcpe runs to sync binaries. sapcpe's start profile specifies the source kernel directory. What happens quite a lot here is that it picks the wrong sapmnt share and either copies the wrong kernel or can't find the file path at all and the startup fails.

Just wondering if anyone has looked at this type of set up before. The primary reason for this setup is due to a local web dispatcher being installed alongside the clustered SAP installation.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Best Answer
    Apr 11, 2016 at 11:50 AM

    Hello John,

    The failover issue occurs because of the conflicting sapmnt shares.

    This is discussed at the item 5 from the SAP note 112266.

    In order to make this work, I believe that you would need to use a virtual hostname for the non-clustered system as well.

    There is a section about using multiple SAP systems at the same server, at the SAP Installation Guides. I believe that could help in this case.



    Add comment
    10|10000 characters needed characters exceeded

  • Apr 09, 2016 at 08:21 AM

    Hi John.

    In which Windows Server OS ? If it is Windows 2008 and above you can install the one more instance on either one of the cluster nodes based on your hardware resources and it should conflict existing cluster instance number.



    Add comment
    10|10000 characters needed characters exceeded

    • Yes that pretty much describes what we've installed and what I've been trying to describe in this thread. However, it doesn't work - at least not reliably.

      When the SAP cluster service group is on the same node as the local installation, there are then two sapmnt shares on the same server: one a local fileshare, one a clustered fileshare. When that happens, Windows resolves the UNC path to the fileshare unreliably (i.e. we can't force it to point to the clustered fileshare or the local fileshare reliably).