Difference between Simple clutser and in SGeSAP cluster

[ASIFKHAN]

Hi All,

Actually ,We have clustering over the machine rx8640 having hpux11.23 and it is running one application named SAP.
Here,first-of-all we had done the simple clustering that i know how to do and after sometime customer asked us to do the SGeSAP cluster then our senior engineer did that SGeSAP clustering.
Now i am in doubt that what was the cluster that i had done and what is the SGeSAP cluster for and why it is needed even we have done one simple clustering already.

And i am unable to do the SGeSAP cluster due to lack of knowledge of this type clustering but i am very much interested in learning it and performing it.

Can anyone please explain the diffrence between these 2 type of clustering along with objective of each and also show me the way to learn it.

Thanks
MAK

[Duncan Edmonstone]

mak,

there's no difference in the underlying clustering software, in either case its just Serviceguard. The only thing that SGeSAP brings is a thoroughly tested and highly functional integration of Serviceguard with SAP. There's (potentially) much more to SAP than just a database and one application server and SGeSAP has a lot of extra capability built into it to help you through all this. On top of this, implementation of SGeSAP is pretty prescriptive, so most SGeSAP clusters are built in much the same way, making bthem easier for HP to support.

So don't expect any difference below the package level, but SGeSAP brings customised packages specifically for SAP.

Have a look at the material here:

http://www.hp.com/go/sgesap
http://docs.hp.com/en/ha.html#Serviceguard%20Extension%20for%20SAP

HTH

Duncan

[ASIFKHAN]

Hi,

But which type of failover does SGeSAP support because simple cluster protects from sinlge point of failure.

Thanks ,
MAK

[Mel Burslan]

SGeSAP is nothing more than a set of scripts and functions to make your life easier, when you are implementing SAP under serviceguard. It does not provide any additional protection mechanisms. Failure mitigation is the function of core serviceguard cluster, with or without SGeSAP package.

Now, having said that, if you want HP to support your SAP implementation on a service guarded cluster, they will make you buy/license the package called SGeSAP. If you are willing to go with plain serviceguard support and say that you will solve your own SAP/SG related issues yourself, you can skip licensing this SGeSAP product but savings are not worth the trouble you are exposing yourself to. Take it from the experience of someone in charge of 7 clusters on 5 different SAP landscapes.

[Steven E. Protter]

Shalom,

There is actually very little difference between these two cluster types.

A simple cluster is an active-passive cluster where you create cluster configuration (nodes) and package control scripts to activate volume group on shared storage and start some process running.

A SGeSAP cluster is the same thing, except you are provided for a fee, package control scripts to start SAP as a cluster service. SAP normally runs an application that keeps its data on an oracle database, which resides on shared storage so the SAP application can run on either node of your cluster.

SEP

[Sunil Sheoran]

Hi MAK

the 1st setep or SGeSAP was done by you. for SGeSAP also you need to have Basic serviece Guard cluster & papart from this additional licenced software is installed such as HA-NFS for sharing oracle binires. This can have different ways for configuration. You can find the step by step Guide on docs.hp.com

Regds
Sunil

[Vinod Kumar Yadav]

Hi Asif,

The SGeSAP is used in SAP Landspace & SGeSAP is know as.

ServiceGuard Extension for SAP.

As you know in the SAP landscape work with DB & CI.DB know as Database & CI is Centeral Instance.

And You Suppose Configured 2 Node MCSG Cluster for the DB & CI.

Frist you configured the MCSG Cluster with 2 pkgs DB & CI

Then For Secure Movment of DB & CI from Node1 to Node2 in the any failure thats what the customer need the SGeSAP Integration the DB & CI pkg with SGeSAP & the all active user connection will from Node 1 to Node2.

SGeSAP is Intorduce by SAP & HP

Mutual Failover Scenarios Using the Two Package Concept: dbSID, ciSID

Dedicated NFS Packages: sapnfs

SAP instance, the Central Instance has an Instance Name. Traditionally it is called DVEBMGS. Each letter represents a service that is delivered by the instance. The â Eâ and the â Mâ stand for the Enqueue and Message Service that were identified as SPOFs in the system. Therefor, the most important package type of SGeSAP is the Central Instance package (ci).


SGeSAP product requires the usage of HPâ s High Available NFS product, the NFS Toolkit (B5140BA). This product has to be purchased separately when customer need to SGeSAP Integration.

And Create the HANFS for pkg form the Application server and shared the 3 below mount points & mount in the application server.The user acess the DB via Application server.

/usr/sap_TU4
/export/sapmnt/global
/export/sapmnt/profile

Serviceguard Extension for SAP (SGeSAP) expands HP Serviceguard's powerful failover capabilities to SAP environments. Backed by world-class support from both HP and SAP, Serviceguard Extension for SAP is fully tested, approved and endorsed by SAP to minimize implementation risks. Customers can also integrate SAP with HP Serviceguard Solutions for disaster tolerance.


Serviceguard Extension for SAP extends the powerful failover capabilities of Serviceguard to SAP environments. It continuously monitors the health of each SAP node and automatically responds to failures or threshold violations. SGeSAP protects the SAP central instance and databaseâ business-critical pieces in an SAP environmentâ within a Serviceguard cluster.

Serviceguard Extension for SAP can be purchased online from HP

Note:- If any more information requried related Serviceguard Extension for SAP pls let me know.


Thanks
Vinod Kumar Yadav