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

Figure 11 shows this state when the failover from Server 1 to Server 2 is complete.
Figure 11: GiCAP failover after usage rights seized (complete outage example)
Note that the Group Manager still has two available core usage rights. This is because the rights
seizure from db3 made four core usage rights available, but only two additional usage rights were
needed to run the application on db4. These available core usage rights could be used by other
members of the group (if the group contained more members), or the administrator could choose to
fully activate all cores on db4.
The main difference in this failover sequence from the partial outage sequence is that the seized
usage rights are only conditionally assigned to Server 2 and will expire at the end of ten days. If
Server 1 does not reconnect to the GiCAP group within those ten days, the seized usage rights will
revert to Server 1 automatically; and, if cores are not deactivated on Server 2, Server 2 will start
consuming TiCAP for the additional cores activated during failover.
22