Cost-Effective High-Availability Solutions with HP Instant Capacity on HP-UX

Example: Automated (Serviceguard) partial outage member failover and group manager failover

This configuration is similar to the previous example, except for the addition of a standby Group

Manager and the additional Serviceguard cluster and package that includes the active and standby

Group Managers. Note that this example shows two separate clusters but the group manager could

be contained in the same cluster and managed by another package.

Figure 18: Initial Serviceguard configuration with standby Group Manager

For this scenario, imagine that the Group Manager ap1 fails, followed by a db1 partition failure. As

in the previous examples, customized scripts are used to provide the necessary shift of resources on

the startup and shutdown of each of the Serviceguard packages.

For the Group Manager failover, the startup script associated with the standby Group Manager needs

only to issue the icapmanage -Q -n command to take control. Use of the -n option is recommended

within scripts because it prohibits the prompting for passwords that might occur if the standby

manager had not previously contacted all member host systems.

Note:

This is why it is important to pre-establish SSL communication with all

member hosts before any failures, since use of this option also means that

any such systems will remain out of contact with the group as a result.