Bladed Server Software Failover via Virtual Instance Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current bladed server systems with PAN architecture face high system costs and resource underutilization due to the need for redundant blades, additional licenses, and multiple IP addresses for application failover, which increases maintenance complexity and costs.
Innovation Solution
A system and method for managing software failover on bladed servers that allows for application failover without requiring additional licenses, disks, or IP addresses, utilizing a diskless and stateless architecture with shared storage and virtual I/O, enabling automatic failover through PAN management software that monitors and reallocates resources dynamically.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a redundant passive failover blade is used for application failover, then high availability is achieved, but system cost increases and resource utilization decreases
Solution Approach 1:
The patent merges the failover capability into the existing active blade by allowing the same blade to dynamically host multiple application instances. Instead of requiring a separate passive blade, the system combines the failover function with the active blade's resources, eliminating redundant hardware while maintaining high availability through software-based instance migration.
Solution Approach 2:
The patent makes the active blade universal by enabling it to serve both as the primary application host and as a failover candidate. The blade can dynamically assume multiple roles - hosting the original application instance and subsequently hosting a failed application instance from another blade, thereby eliminating the need for dedicated passive failover blades.
2Reliability
If multiple licenses and software installations are maintained for failover blades, then application failover capability is ensured, but maintenance complexity increases
Solution Approach 1:
The patent uses virtualization to create a software-based copy of the application instance rather than requiring physical software installations on multiple blades. The failed application instance is captured as a virtual image or snapshot and can be migrated to any available blade, eliminating the need to maintain identical software installations across multiple physical systems.
Solution Approach 2:
The system implements automated failover management where the virtualization layer handles instance migration, resource allocation, and software deployment automatically. When an application fails, the system self-manages the recovery process by migrating the instance to another blade without requiring manual software installation or configuration on the target blade.
3Reliability
If dedicated disks are allocated for failover boot and data storage, then application continuity is maintained, but storage resource utilization decreases
Solution Approach 1:
The patent merges storage resources by using shared network-attached storage (NAS) or storage area network (SAN) instead of dedicated local disks on each blade. Application instances and their data are stored centrally in the network storage infrastructure, allowing any blade to access and host any application instance without requiring local storage duplication.
4Reliability
If multiple IP addresses are assigned for primary and failover blades, then application accessibility is maintained during failover, but network configuration complexity increases
Solution Approach 1:
The patent introduces a virtualization layer as an intermediary between the application instances and the network. This virtualization layer manages IP address allocation and network connectivity dynamically, allowing application instances to be migrated between blades while maintaining consistent network access through the virtualization intermediary that handles address translation and routing.
Data Source
AI summary
A system for managing software failover on a bladed server is provided. The system includes a plurality of bladed servers, including a first bladed server and a second failover bladed server. The system includes a server control, a storage device, and software. The server control is in communication with the plurality of bladed servers, and the storage device is accessible by the plurality of bladed servers. The software is stored on the storage device. The system also includes a management component that is operable on the server control. The management component monitors execution of the software on the first bladed server. The management component is operable in response to detecting failure of the software on the first bladed server to promote execution of the software from the external storage device by the second failover bladed server. A method for automated software failover is also provided.