SAP installation for HA

[Nappy_1]

I have to configure SGeSAP for an existing SAP installation.
i have seen some notes in the documentation about the SAP installation options. one of these options is HA installation.

I don't know how SAP was installed and i don't have a knowledge on SAP.

My questions: can i implement SGeSAP if SAP installation was not done in HA mode?

If no, how can i check the installation mode?

finally, can someone help me with a cookbook for SGeSAP configuration?

[Rita C Workman · Accepted solution]

I am SAP illiterate, but HA to me means High Availability and that equates to MC/Service Guard on HPUX.

So, if your SAP is loaded on disk that is 'share-able' by other servers, then I would think it can be made highly available.

Simplistically stated, you need to ensure that all of SAP was loaded on disk that can be seen by other nodes. Then you create a cluster, which can start as a single node (server) cluster. And within that cluster you create a package that controls the volume group (disk);filesystems and startup commands for the software.

So, I you might go out to the new docs area and look for High Availability and MS/SG and download and review the material.

Now if SAP has some kind of mode settings, I'm sure the folks here who are familiar with SAP can guide you.

Just a couple thoughts,
Rita

[Doug O'Leary]

Hey;

I'm in a similar boat. Basically, in charge of the clusters but limited knowledge of SAP.

First thing is to ensure that SAP is installed and running.

Next, install serviceguard s/w (if not already done) and form a cluster. Also install the SAP extensions for MCSG, assuming you've purchased them.

Once everyone's ready, create the package in the normal method. The initial package is going to do nothing but mount filesystems and plumb up IP addresses. Once this is done, ensure that your basis people can start SAP in this environment on both nodes - on all nodes required, actually. This will point out differences in users, kernels, mount points, oracle listeners, etc.

Next, copy in the files from /opt/cmcluster/sap/SID/* to /etc/cmcluster/${SID}. Have your basis people update the sap.config file. I looked at that once and couldn't make heads or tails of it... I'm reasonably sure that's why my client pays the basis people.

Once that's done, update the customer_defined_run_cmds to reflect:

. /etc/cmcluster/${SID}/sapwas.cntl start ${SID}

Note the '.' - that's important.

That's pretty much the process that I follow when creating new SAP clusters. There was an initial political battle about who's supposed to update the sap.config file which ended with me saying "If only we had a team of people that were paid to support SAP here... Oh, wait!"

Hope that helps.

Doug

[Nappy_1]

Thanks for the answers.
well, I know very well SG and i know how to create normal packages. but here it's a little bit diffrent.

anyway. your feedback is important to me, i'll use it with the documentation i have