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

Figure 9 shows the state after the core activations on Server 2, when the failover from db1 to db2 is
complete.
Figure 9: GiCAP failover completed (partial outage example)
Most importantly, note that because partition db3 on Server 1 was still running during the rights
seizure from db1:
• The rights seizure was effective immediately and without a time expiration constraint.
• After more than twelve hours of inactivity on db1, the Instant Capacity software on db3 defaults to
an assumption that all cores might become active on cells configured for partition db1. This may
result in additional TiCAP consumption or in activation restrictions. For more details, see the
“Recovery from a failure involving one or more nPartitions
” sub-section.
• When the problem on db1 is fixed and db1 is rebooted, only two cores will be active on db1. To rerun
the application on db1 at that time (fail back), cores must be deactivated on db2 and activated on
db1.
Or, there is a restore command (icapmanage -z) you can use to automatically restore seized usage
rights to the original nPartition before rebooting. The restore command does not provide the
deactivation step however; unless core usage rights have been made available in the group (through
deactivations), the restore command will fail. In this example, deactivate cores on db2, on ap1 issue the
restore command targeting db1, and then reboot db1.
19