MC/SG OPS - Can unshared VG be in the same package as shared VG's ?

[Robert Gamble]

We have a cluster running MC/SG OPS Edition for an Oracle Application.

The cluster was configured by an HP Consultant.

For archiving purposes, there is a VG in each node's package that gets mounted in the customer_defined_run_cmds function instead of the normal functions because of the $VGCHANGE setting for all the shared volumes is set to 'vgchange -a s'.

This became a problem over the weekend when a TOC was required, when the server came back up,the unshared VG couldn't be mounted because the two lvols required a fsck before being mounted.

1) I was curious if this type of setup is supported by HP. My collegue is placing a support call, but I was curious if anyone else has run across this.

2) If we decide to leave things alone, I would like to add a check to the pkg.cntl script to check to see if the two lvols need to be fsck'd. Does anyone have something similar I could use there ?

Thanks!

[Pierce Byrne_1]

If the filesystems only get mounted on package start I see no reason why it is not shared and inluded as a proper service guard volume.

If are needed all the time then they should not be part of service guard at all, rather include as an entry in /etc/fstab to fsck and mount at boot up

[Stephen Doud · Accepted solution]

Hello Robert,

1. In short, HP does not support items added to the customer_defined_run_cmds or customer_defined_halt_cmds sections.
To HP, "support" means tested by the manufacturing division and final responsibility for problems with the object lies with the division.
Your custom configuration that activates a private volume group as part of the package customer_defined_run_cmds therefore is not "supported". Does this mean that the HP Response Center will not even discuss it? It becomes a best-effort call in that case, but the division is not obligated to assist the RCE in resolving the issue.

2. You may want to observe the the check_and_mount function in the package script to see how you can adapt the customer_defined_run_cmds section to resolve the mount issue of the private volume.

-s.