Implement high-availability solutions with HP Instant Capacity - easily and effectively

17
Consider the same GiCAP group as shown in figure 7, except this time there are two critical applications on server 1
(OA1); one running in partition Db1, and the other running in partition Db3. The application running in Db3 requires
12 active cores, so only 12 core usage rights were purchased and allocated to that partition. On server 2 (OA2) Db2 and
Db4 are running low-priority tasks and have only 4 and 8 active cores respectively. Temporary capacity is not being used
in this group.
In this example, there is a more serious problem, and the entire server 1 has failed. The critical applications in Db1
and Db3 must be moved to Db2 and Db4, respectively. In this case, the system administrator chooses to seize usage
rights from server 1 to free up enough usage rights to run both applications on server 2. To seize the usage rights from
Server 1, the commands to run on ap1 (the group manager) are:
ap1> icapmanage -x OA1
Figure 10 displays the state after the administrator has issued the command to seize usage rights from the complex.
Figure 10. HP GiCAP failover after commands have been issued to seize usage rights (complete outage)
Db1: 2 blades, 1
reserved core
Server 1
A
Active core
Inactive (iCAP) core
Db2: 2 blades, 4
active and 12 iCAP
cores
Server 2
A A
A A
Db4: 2 blades, 8
active and 8 iCAP
cores
Reserved core usage right
ap1: Group Manager
A A
A A
A A
A A
A
A
A
A
A
R
Db3: 2 blades, 0
active core
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
R