HP Serviceguard Extension for SAP (SGeSAP) manual Cluster Node Synchronization

If the local executable directory only holds links, sapcpe is not configured correctly. It is not an option to manually copy the local executables in this case. The next instance restart would replace the local copies with symbolic links.

For latest information on how to utilize sapcpe refer to the SAP online documentation.

Installation Step: IS060

Clustered SAP Instances must have instance numbers that are unique for the whole cluster.

For a clustered instance with instance number <INSTNR> execute the command:

ls -d /usr/sap/???/*<INSTNR>

It should not reply any match on all nodes. Otherwise refer to the SAP documentation how to change instance IDs for the relevant instance type. It might be simpler to reinstall on of the conflicting instances.

Installation Step: IS065

If local executables are created (refer to step IS050) and failover nodes have no internal application server with local executables installed, distribute the directory tree /usr/sap/<SID>/SYS from the primary node.

Do not use rcp(1), it will follow all links and copy a lot of files from the shared disks that are not needed.

For example, on the primary node:

cd /usr/sap/<SID>/SYS

find . -depth -print cpio -o >/tmp/SYS.cpio

Use ftp(1) to copy the file over to the secondary node. On each alternate node:

su - <sid>adm

mkdir -p /usr/sap/<SID>/SYS

cd /usr/sap/<SID>/SYS

cpio -id </tmp/SYS.cpioexit

Cluster Node Synchronization

Repeat the steps in this section for each node of the cluster that is different than the primary.

Logon as root to the system where the SAP Central Instance is installed (primary host) and prepare a logon for each of its backup hosts - if not already available.

Installation Step: IS070

Open the groupfile, /etc/group, on the primary side.

If any of the groups listed in Table 3-2 - Groupfile File Groups exist on the primary node and they do not exist on the backup node, copy them from the primary node to the backup node. If any group exists, verify that it has the same GID on both the primary and backup nodes. Merge the group members lists.

Table 3-2 Groupfile File Groups

Groups	GID	Group members
sapsys

sapinst

sdba

oper

Installation Step: IS080

Open the password file, /etc/passwd, on the primary side.

If any of the users listed in Table 3-3 Password File Users exist on the primary node, recreate them on the backup node. Assign the users on the backup nodes the same user and group ID as the primary nodes.

HP-UX Configuration 51