Implementing a Virtual Server Environment: Getting Started

Sweet Spots
• Excellent choice for application stacking. Can run multiple instances of the same application
on the same OS while maintaining application isolation and resource-level guarantees.
• Allows for resource-level control and application isolation without requiring a separate
instance of the OS.
HP Utility Pricing Solutions:
Why choose Instant Capacity (iCAP)?
Key Benefits
• Allows you to defer the cost of system components (processors, memory, cell boards) until you
need the capacity.
• Simplifies capacity planning; reduces the need to overprovision.
• nPars can be flexed with iCAP cores on the same server or across servers with Global Instant
Capacity (GiCAP).
• Cell-board iCAP allows you to activate a complete cell. Starting with HP-UX 11i v3, you can
dynamically add a cell to an nPar without rebooting the OS.
Trade-offs
• Available only on cell-based systems.
• To activate the usage rights of an iCAP core for a partition, the core must physically be in the
same nPar.
• Prior to HP-UX 11i v3, rebooting is required to activate an iCAP cell board.
Sweet Spots
• Provides a cushion or safety net for capacity planning.
• Provides inexpensive spare capacity that can be activated online.
• Allows you to flex the size of partitions in a failover situation.
• Provides the ability to flex nPars.
Why choose Temporary Instant Capacity (TiCAP)?
Key Benefits
• Allows iCAP cores to be activated for limited periods of time.
• When purchasing TiCAP (in 30-day increments), you can activate one or more iCAP cores
against the balance (measured and tracked in 30-minute intervals).
Trade-offs
• Available only on cell-based systems.
Sweet Spots
• Excellent choice for responding to short-term spikes in the workload; preferable to use with
WLM or gWLM.
• Cost-efficient way to provide high-capacity test environments for short periods of time.
• Allows you to lower the cost of a failover server because the cores need to be activated only
during the failover period.
9