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.
John Studdert replied
Thanks Isaias, appreciate that. Yes that is exactly the issue we have but thank you for the SAP note which explicitly states it's not supported.
We do indeed use virtual hostnames for the non-clustered systems as well but I suspect the problem is that despite this, when they are registered on the same NIC Windows does not reliably resolve them.
There is a technet article that reflects this. Based on that I'm going to mark this closed and the answer is that this is not possible or supported, even if you use virtual hostnames and de-select registering with DNS on the NIC (and then manually create static DNS records instead), as we are using these on the same NIC.