P
US7590727B1ExpiredUtilityPatentIndex 98

System and method for software failover on a bladed system

Assignee: SPRINT COMMUNICATIONS COPriority: Sep 28, 2004Filed: Sep 28, 2004Granted: Sep 15, 2009
Est. expirySep 28, 2024(expired)· nominal 20-yr term from priority
Inventors:BARNES JAMES D
G06F 11/2025G06F 11/2033G06F 11/2023
98
PatentIndex Score
57
Cited by
14
References
18
Claims

Abstract

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.

Claims

exact text as granted — not AI-modified
1. A bladed system, comprising: a plurality of bladed servers, including a global failover bladed server pool including at least one failover bladed server that is available as a failover target for any other of the plurality of bladed servers and a local failover bladed server pool including at least one failover bladed server that is available as a failover target exclusively for at least one of the other of the plurality of bladed servers; a storage device sharable by the plurality of bladed servers; software stored on the storage device; and a component that monitors execution of the software on a first bladed server of the plurality of bladed servers, wherein the component promotes execution of the software from the storage device by a second failover bladed server in one of the global failover bladed server pool or the local failover bladed server pool in response to detecting failure of the software on the first bladed server, wherein the component further shuts down the first bladed server, boots the second failover bladed server, and assigns network and storage resources assigned to the first bladed server to the second failover bladed server. 
     
     
       2. The bladed system of  claim 1 , wherein the software is further defined as an operating system. 
     
     
       3. The bladed system of  claim 1 , wherein the software is further defined as an application. 
     
     
       4. The bladed system of  claim 1 , wherein the software is further defined as an operating system and an application operable on the operating system. 
     
     
       5. The system of  claim 1 , further comprising a server control and wherein the component is a software component operable by the server control. 
     
     
       6. The system of  claim 1 , wherein the component is further defined as management software. 
     
     
       7. The system of  claim 6 , wherein the component includes application health monitoring software that executes on the first bladed server and notifies the management software if the application fails. 
     
     
       8. The system of  claim 1 , wherein the storage comprises a storage area network. 
     
     
       9. The system of  claim 1 , wherein the storage comprises network-attached storage. 
     
     
       10. A method for automated application failover on a bladed server comprising: providing a plurality of bladed servers, including a global failover bladed server pool including at least one failover bladed server that is available as a failover target for any other of the plurality of bladed servers and a local failover bladed server pool including at least one failover bladed server that is available as a failover target exclusively for at least one of the other of the plurality of bladed servers; storing an application on a storage device accessible by at least some of the plurality of blades; executing the application on a first bladed server of the bladed server from the storage device; monitoring the application during execution; detecting failure of the application; executing the application from the storage device on a failover bladed server in one of the global failover bladed server pool or the local failover bladed server pool; shutting down the first bladed server; assigning disk resources and network resources assigned to the first processing blade to the failover bladed server; and booting the failover bladed server. 
     
     
       11. The method of  claim 10 , further comprising:
 designating a second bladed server of the bladed server to be the failover bladed server. 
 
     
     
       12. The method of  claim 10 , wherein the storage device is further defined as a storage area network. 
     
     
       13. A system for managing application failover, comprising: a plurality of bladed servers, including a first bladed server, a global failover bladed server pool including at least one failover bladed server that is available as a failover target for any other of the plurality of bladed servers, and a local failover bladed server pool including at least one failover bladed server that is available as a failover target exclusively for at least one of the other of the plurality of bladed servers; a server control in communication with the plurality of bladed servers; a storage device accessible by the plurality of bladed servers; an executable application stored on the storage device; and an executable management component stored on the server control that monitors execution of the application on the first bladed server, wherein the executable management component promotes execution of the application from the external storage device by a second failover bladed server in one of the global failover bladed server pool or the local failover bladed server pool in response to detecting failure of the application on the first bladed server, wherein the executable management component further shuts down the first bladed server, assigns disk resources and network resources assigned to the first bladed server to the second failover bladed server, and boots the second failover bladed server. 
     
     
       14. The system of  claim 13 , wherein the executable management component monitors the first bladed server for failure. 
     
     
       15. The system of  claim 13 , wherein the executable management component monitors the application for failure. 
     
     
       16. The system of  claim 13 , wherein the executable management component monitors both the first bladed server and the application for failure. 
     
     
       17. The system of  claim 13 , wherein the storage device is further defined as an external storage device. 
     
     
       18. The system of  claim 13 , wherein the storage device is further defined as a storage area network.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.