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

Figure 14 shows the result.
Figure 14: GiCAP failover from Server 1 to Server 2 completed (virtual partition example)
As in the previous ”complete outage” example with nPartitions, the seized usage rights activated in
vp3 and vp4 will expire in ten days. At that time, the usage rights revert to vp1 and vp2 and unless
cores are deactivated in vp3 and vp4, TiCAP will be consumed because more cores will be active
than available usage rights.
However, because virtual partitions are involved, it is important to restore the seized usage rights
before trying to boot vp1 or vp2. If vp1 or vp2 start to boot before the end of the ten days and before
any restore operation, the seizure of rights is committed for the nPartition db1 on Server 1, leaving
two core usage rights (one for each of the two virtual partitions of Server 1). If this happens, the
vp1/vp2 boot may fail and the nPartition must be booted to fix the vPars partition database
assignments. To avoid this, always deactivate the cores activated during the failover and perform the
restore operation before attempting to reboot virtual partitions that have been affected by rights
seizure. You can perform this task with the following commands:
vp3> icapmodify -d 3
vp4> icapmodify -d 3
ap1> icapmanage -z vp1
27