Solaris SPARC live migration increases Oracle DB availability
By Frederic Pariente on Feb 15, 2012
One of the most significant business challenges for IT is to create and preserve value in a highly competitive environment, while keeping business applications available, improving hardware utilization and reducing costs. In particular, it is important to maximize application availability during planned or unplanned outages, without any compromise on resource allocation flexibility based on business needs, à la cloud computing.
Orgad Kimchi and Roman Ivanov at Oracle ISV Engineering describe in a new whitepaper "Increasing Application Availability by Using the Oracle VM Server for SPARC Live Migration Feature: An Oracle Database Example" how the Oracle VM Server for SPARC software (f.k.a. Sun Logical Domains or LDoms) can increase application availability, using the example of the Oracle database software.
The benefits of Live Migration are :
- Shorter Maintenance
One can minimize application downtime by using the domain Live Migration feature of Oracle VM Server for SPARC. If some equipment must shut down for hardware maintenance, this feature can keep applications running by moving them to another server.
- Optimized Hardware Utilization
One can improve application performance by using the domain Live Migration feature in order to move an active domain to a machine with more physical memory, more CPU capacity, or a better I/O subsystem.
- Higher Application Availability
One can maximize application availability by using the domain Live Migration feature because there is no need to shut down the application while the migration is in process.
The whitepaper shows the complete configuration process, including the creation and configuration of guest domains using the
ldm command, the storage configuration and layout, and all software requirements that were used to demonstrate the Live Migration between two SPARC T4 systems.
Orgad and Roman tested the Oracle 11gr2 DB while migrating the guest domain from one SPARC T4 server to another without shutting down the Oracle database. The Swingbench OrderEntry workload was used to generate the load; OrderEntry is based on the OE schema that ships with Oracle 11g. This workload introduces heavy contention on a small number of tables and it is designed to stress the following scenario : 30GB DB disk size with 18GB SGA size, 50 concurrent users and 100ms time between actions taken by each user.
Throughout the testing, the Oracle VM Server for SPARC domain Live Migration proved to linearly scale across the 64 CPUs available on the SPARC T4 processor, to shorten overall migration time and deliver extremely short suspension time, as shown in the table below.
|Number of CPUs on the Control Domain||Overall Migration Time||Suspension Time||Guest Domain CPU Usage|
|8 CPUs||8 min 12 sec
||4 min 2 sec
|24 CPUs||2 min 3 sec