Serviceguard package startup policies

[kaushikbramesh]

Hi,

We are using HA Serviceguard on a IA 7620 based systems. What we have is 3 Serviceguard packages - Oracle, App-A and App-B. On all 3 packages the AUTO_RUN option is enabled, and also the AUTOSTART_CMCLD is set to 1 in the /etc/rc.config.d for automatic startup of the cluster and the packages in the event of a cluster restart/node failover. We need to acheive some kind of a control over the sequence in which these packages start in the event of node failover. The order being, Oracle package should start first followed by package App-A and followed by App-b. How can we achive this ?

Thanks in advance for all your suggestions.

Kaushik

[RAC_1 · Accepted solution]

I myself never did it, but see a way to do it.

1 With customer defined scripts in packages. these script will check for dependence and start if dependant package is up or not.

[melvyn burnard]

currently there is no standard built in dependencies for SG packages in the way you require.
You need to add something in to the customer_defined_run_functions to check for the package you are dependant upon.

[Cem Tugrul]

Hi,
i am agree with Rac & Melvyn
i have also MC/SG and my pkts (appl+oracle)
i am using my own start/stop scripts where locates "customer define scripts"

Good Luck,

[kaushikbramesh]

Hi,

Thanks for all your suggestions.
On Tru64 Unix we can control the order in which the cluster resources start. Having a bit of exposure to Tru Clusters, I was thinking it might be possible on HP-UX too but was not sure how. Once again Thanks for all your suggestions.

Kaushik

[Duncan Edmonstone]

This functionality was on the roadmap for SG11.17 (due 'real soon now'), but due to all the changes relating to cluster file systems with Veritas integration, its been pushed out, presumably to the next release.

So this functionality will be there - just not yet...

HTH

Duncan

[kaushikbramesh]

Hi all,

Thanks very much for all your suggestions.

Regards
Kaushik