Implement high-availability solutions with HP Instant Capacity - easily and effectively
10
Figure 5. HP TiCAP example after failure and one day after activations on Sys2
When the failure on Sys1 is resolved, you can stop the use of TiCAP on Sys2 by deactivating the 12
processor cores:
Sys2> icapmodify -d 12
OR
OA> icapmodify –p 2 –d 12
You can also redeploy the applications to Sys1.
HP Serviceguard considerations
The TiCAP solution can be automated using the Serviceguard product. The basic steps include:
• Configuring a Serviceguard cluster with packages set up to fail over automatically to the standby server
(adoptive node).
• Purchasing and applying TiCAP to the standby server.
The amount of TiCAP to purchase depends on:
– The number of additional processor cores that need to be activated on the standby server to run the package
– The amount of time needed to cover downtime
• Creating scripts that provide customized processing on the startup and shutdown of the package to activate and
deactivate the use of TiCAP, as necessary. In this scenario, failback (either automatic or manual) is essential to avoid
continuous consumption of TiCAP.
Preparing for the next potential failure. After a successful failover and subsequent failback to the primary server or
servers, additional TiCAP should be purchased and applied to the standby servers in preparation for potential failures.
2 blades, 4 active
and 12 iCAP cores
(12 units of TiCAP)
2 blades, 16 active
cores
SD2 – Sys1 SD2 – Sys2
A A
A A
A A
A A
A A
A A
A A
A A
78 days
A
Active core
Inactive (iCAP) core due to failure