Implement high-availability solutions with HP Instant Capacity - easily and effectively
23
End-to-end time for Group Manager failover consists of:
• Serviceguard failover time
• The time needed for a standby to take control
The time needed for a standby Group Manager to take control depends on the number of:
• Groups
• Members in the groups
• Members in the groups that are not contactable
Remember that during failover to a standby Group Manager, the members of the group can still operate normally with
the usage rights they have, they just cannot borrow or lend usage rights within the group.
Automate member failover using core usage rights seizure
Automated (Serviceguard) member failover from a partial outage with
nPartitions
The initial configuration, shown in figure 12, includes a GiCAP group consisting of a single Group Manager (no standby
Group Manager) and two servers with OAs OA1 and OA2, each with two partitions. Partitions Db1 and Db2 are also part of
a Serviceguard cluster. Db1 is defined to be the active node for the package, while Db2 is the adoptive (failover) node.
The package requires 16 active processor cores to run, so Db1 is configured with usage rights for 16 cores. Db2 has been
configured with 12 inactive cores. No temporary capacity is being used in this group.
There are 24 inactive cores (cores without usage rights) in this configuration. 24 GiCAP sharing rights are configured to
create this group.