QUICK FAILOVER OF BLADE SERVER

• US 20150006951A1
• Filed: 09/24/2013
• Published: 01/01/2015
• Est. Priority Date: 06/28/2013
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Gurram, Nagendra K., Pandey, Ajay Y.
• Granted Patent: US 9,471,445 B2
• Time in Patent Office: Days
• US Class Current: 714/4.12
• CPC Class Codes: G06F 11/2007 using redundant communication media
• CPC Class Codes: G06F 11/2025 using centralised failover control functionality
• CPC Class Codes: G06F 11/2028 eliminating a faulty processor or activating a spare
• CPC Class Codes: G06F 11/2041 with more than one idle spare processing component
• CPC Class Codes: G06F 11/2046 where the redundant components share persistent storage G06F11/2043 takes precedence

Abstract

Failover process for switching from a “failing” blade server to a “replacing” blade server. This process includes the following steps: (i) booting a replacing blade server to a set of operating system(s) including a first operating system; and (ii) subsequent to the booting of the replacing blade server, sending command data to the replacing blade server. The command data includes a command for the replacing blade server to configure itself to replace the failing blade server.

Claims

1. A process for performing, at least a portion of, a failover from a failing blade server to a replacing blade server, the method comprising:

booting a replacing blade server to a set of operating system(s) including a first operating system;

receiving, by the replacing blade server, command data while the replacing blade server in a booted state; and

responsive to the command data, configuring the replacing blade server to replace the failing blade server without any rebooting of the replacing blade server.

2. The process of claim 1 wherein the command data further includes failing server data to be used in configuration of the replacing blade server as a replacement for the failing blade server.

3. The process of claim 1 further comprising:

running, on a first adaptation layer of the replacing server, runtime services to effect the configuration of the replacing blade server as a replacement for the failing blade server.

4. The process of claim 3 wherein the runtime services are runtime abstract software services.

5. The process of claim 1 wherein the replacing blade server and the failing blade servers are both proper blade servers.

6. The process of claim 1 further comprising at least one of the following:

after the booting of the replacing server and prior to the sending of the command data, checking the replacing server for good health; and

/or

after the booting of the replacing server and prior to the sending of the command data, checking the replacing server for available computing resources.