LPAR Migration Profile Retention for Failover Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing LPAR migration protocols in IBM AIX environments are incompatible with failover protocols, leading to disruptions in application availability and mobility, as they delete essential information needed for failover functionality.
Innovation Solution
The method involves creating a profile for a logical partition on a host system, mapping a client port of a virtual SCSI adapter to a server port of a VIOS, and setting the server port to accept any virtual SCSI adapters, ensuring that disk mappings are retained during migration, thus maintaining compatibility with cluster management failover protocols like Veritas Cluster Server.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If LPAR migration protocol deletes profile and disk mappings from source computing resource, then migration can be completed, but failover protocol compatibility is lost and application availability is disrupted
Solution Approach 1:
The patent extracts the disk mapping information from the source computing resource during migration, separating it from the LPAR profile deletion. By maintaining disk mappings independently in the VIOS, the system allows migration to proceed while preserving failover capability through retained mapping information.
Solution Approach 2:
The VIOS acts as an intermediary between the LPAR migration process and the failover protocol. It maintains disk mappings and provides them to both migration and failover protocols, enabling both to function simultaneously without conflict. The VIOS mediates the information flow so that migration can delete source mappings while failover retains access to mapping data.
2Duration of action of stationary object
If LPAR profile is migrated to second computing resource, then application continuity is maintained, but disk mapping information is deleted from source resource
Solution Approach 1:
The patent creates and maintains copies of disk mapping information in the VIOS, which serves as a centralized repository accessible by both source and destination computing resources. This copying mechanism ensures that disk mapping information is preserved in the VIOS even when deleted from the source resource, enabling both application continuity and information retention.
3Productivity
If migration protocol deletes underlying disk mappings from source computing resource, then migration is finalized, but other features and services involving LPARs are adversely affected
Solution Approach 1:
The VIOS is designed as a universal platform that serves multiple functions: it supports LPAR migration by providing disk mapping information, maintains failover protocol compatibility, and preserves other LPAR features and services. By centralizing disk mapping management in the VIOS, the system achieves multi-functionality where a single component supports diverse LPAR operations simultaneously.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method and system for LPAR migration including creating a profile for a logical partition on a host system comprising one or more LPARs, wherein the profile is associated with a first name. Also, within the profile, a port of a client virtual small computer system interface (SCSI) adapter of the LPAR is mapped to a port of a server virtual SCSI adapter of a virtual input/output server (VIOS) of the host system. The server port of the VIOS is set to accept any port of virtual client SCSI adapters of the one or more LPARS of the host system. Within the VIOS, the server port of the VIOS is mapped to a device name (i.e., LPAR) and to a target device (i.e., a disk of shared storage), for purposes of proper failover implementation of the LPAR, wherein the target device comprises an operating system for the LPAR.