Method for clustering software applications

• US 6,134,673 A
• Filed: 10/01/1997
• Issued: 10/17/2000
• Est. Priority Date: 05/13/1997
• Status: Expired due to Term

• Current Assignee: Round Rock Research LLC
• Original Assignee: Micro Electronics Incorporated
• Inventors: Chrabaszcz, Michael
• Primary Examiner(s): HUA, LY
• Application Number:
  US08/942,318
• Time in Patent Office: 1,112 Days
• Field of Search: 714/13, 714/10, 714/4, 714/3, 714/2, 714/17, 714/16, 714/20, 709/200, 709/201, 709/213
• US Class Current: 714/13
• CPC Class Codes: G06F 11/1658 Data re-synchronization of a redundant component, or initial sync of replacement, additional or spare unit
• CPC Class Codes: G06F 11/203 using migration
• CPC Class Codes: G06F 11/2038 with a single idle spare processing component
• CPC Class Codes: G06F 11/2046 where the redundant components share persistent storage G06F11/2043 takes precedence
• CPC Class Codes: G06F 11/2097 maintaining the standby controller/processing unit updated initialisation or re-synchronisation thereof G06F11/1658 and subgroups
• CPC Class Codes: H04L 41/0663 Performing the actions predefined by failover planning, e.g. switching to standby network elements
• CPC Class Codes: H04L 41/0816 the condition being an adaptation, e.g. in response to network events
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

A method for fault tolerant execution of an application program, in a server network having a first and second server, wherein the method includes: executing the application program in the first server; storing an object which represents the program in a cluster network database, wherein the object contains information pertaining to the program; detecting a failure of the first server; and executing the application program in the second server upon detection of the failure of the first server, in accordance with the information in the object. The information may include: a host server attribute which identifies which server is currently executing the program; a primary server attribute which identifies which server is primarily responsible for executing the program; and a backup server attribute which identifies which server is a backup server for executing the program if the primary server experiences a failure.

Claims

1. A method for fault tolerant execution of an application program in a server network having a first server and a second server, comprising:

executing, in the first server, the application program;

storing an object which represents the application program into a cluster network database, wherein the object contains information pertaining to the application program;

detecting a failure of the first server;

determining whether the second server has sufficient resources to execute the application program; and

executing, in the second server, the application program upon detection of the failure of the first server, in accordance with said information in said object.

2. The method of claim 1 wherein the act of storing the object comprises:

promting a system operator for the information, wherein the information comprises;

a host server attribute which identifies which server is currently executing the program;

a primary server attribute which identifies which server is primarily responsible for executing the program; and

a backup server attribute which identifies which server is a backup server for executing the program if the primary server experiences a failure.

3. The method of claim 2 wherein the information further comprises:

an identification field which identifies the program;

a program type field which indicates whether the program is cluster capable or cluster aware; and

a command field which controls a protocol for loading the program and subsequently executing the program.

4. The method of claim 2 wherein the act of executing the program in the second server comprises:

reading the backup server attribute in the object with the second server;

determining whether the backup server attribute names the second server as the backup server;

if the backup server status names the second server as the backup server, loading the program in the second server.

5. The method of claim 4 further comprising changing the host server attribute to name the second server as the host server of the program.

6. The method of claim 5 further comprising:

detecting when the first server is once again operational; and

resuming execution of the program in the first server upon detecting that the first server is once again operational.

7. The method of claim 6 wherein the act of detecting when the first server is once again operational, comprises:

tranmitting packets at periodic intervals from the second server to the first server; and

waiting for an acknowledgement signal in response to each packet for a specified period of time, wherein if the acknowledgement signal is received within the specified period of time, the first server is determined to be operational.

8. The method of claim 7 further comprising changing the host server attribute to name the first server as the host server of the program.

9. The method of claim 8 wherein the step of resuming execution of the program in the first server comprises:

unloading the program from a random access memory in the second server;

verifying that the program has been unloaded from the second server; and

loading the program in a random access memory in the first server after the program has been unloaded from the second server.

10. The method of claim 9 wherein the act of verifying that the program has been unloaded from the second server comprises reading the host server attribute and determining that the host server status indicates the first server as the host server of the program.

11. The method of claim 1 wherein the act of detecting a failure of the first server comprises:

tranmitting packets at periodic intervals from the second server to the first server; and

waiting for an acknowledgement packet in response to each packet for a specified period of time, wherein if the acknowledgement packet is not received within the specified period of time, the failure of the first server is detected.

12. The method of claim 1 wherein the act of detecting a failure of the first server comprises:

monitoring communications between the first server and a network resource; and

detecting a termination in the communication between the first server and the network resource.

13. The method of claim 1 wherein the act of detecting a failure of the first server comprises:

successively transmitting first and second command signals from the first server to a device coupled to the first server, wherein the first command signal places the device in a first status condition and the second command signal places the device in a second status condition; and

monitoring a status condition of the device with the second server, coupled to the device, wherein a change in the status condition of the device indicates that the first server is operational and a constant status condition indicates the failure of the first server.

14. The method of claim 1 further comprising:

detecting when the first server is once again operational; and

resuming execution of the program in the first server upon detecting that the first server is once again operational.

15. The method of claim 14 wherein the act of detecting when the first server is once again operational, comprises:

tranmitting packets at periodic intervals from the second server to the first server; and

waiting for an acknowledgement signal in response to each packet for a specified period of time, wherein if the acknowledgement signal is received within the specified period of time, the first server is determined to be operational.

16. The method of claim 14 wherein the step of resuming execution of the program in the first server comprises:

unloading the program from a random access memory in the second server;

verifying that the program has been unloaded from the second server; and

loading the program in a random access memory in the first server after the program has been unloaded from the second server.

17. The method of claim 1 wherein the act of storing an object which represents the program in a cluster network database is performed automatically by the program as it is executed in the first server, wherein the information is contained within the program and is automatically written into the object stored the cluster network database.

18. The method of claim 17 wherein the information comprises:

a host server attribute which identifies which server is currently executing the program;

a primary server attribute which identifies which server is primarily responsible for executing the program; and

a backup server attribute which identifies which server is a backup server for executing the program if the primary server experiences a failure.

19. The method of claim 18 wherein the information further comprises:

an identification field which identifies the program;

a program type field which indicates whether the program is cluster capable or cluster aware; and

a command field which controls a protocol for loading the program and subsequently executing the program.

20. The method of claim 18 wherein the act of executing the program in the second server comprises:

reading the backup server attribute in the object with the second server;

determining whether the backup server attribute names the second server as the backup server;

if the backup server status names the second server as the backup server, loading the program in the second server.

21. The method of claim 20 further comprising changing the host server attribute to name the second server as the host server of the program.

22. The method of claim 21 further comprising:

detecting when the first server is once again operational; and

resuming execution of the program in the first server upon detecting that the first server is once again operational.

23. The method of claim 22 wherein:

the act of executing the program in the second server comprises;

determining a first location within the program where execution of the program by the first server ceased; and

commencing execution of the program by the second server at the first location; and

the act of resuming execution of the program by the first server comprises;

determining a second location within the program where execution of the program by the second server ceased; and

commencing execution of the program by the first server at the second location.

24. The method of claim 23 wherein:

the act of determining the first position comprises;

updating a pointer within the program as it is executed by the first server; and

determining the location of the pointer prior to execution of the program by the second server; and

the act of determining the second position comprises;

updating the pointer within the program as it is executed by the second server; and

determining the location of the pointer prior to resuming execution of the program by the first server.

25. The method of claim 24 further comprising:

determining if the second server has access to specified resources necessary to execute the program; and

if it is determined that the second server does not have access to the specified resources, sending an error message to a system operator.

26. The method of claim 25 wherein the specified resources are identified in a list of resources which is part of the information contained within the object.

27. The method of claim 26 wherein the act of determining if the second server has access to specified resources necessary to execute the program, comprises comparing the list of resources to a list of resources initialized by a BIOS program stored within the second server.

28. The method of claim 26 wherein the act of determining if the second server has access to specified resources necessary to execute the program, comprises comparing the list of resources to a configuration file stored within the second server.

29. The method of claim 21 wherein the act of detecting when the first server is once again operational, comprises:

tranmitting packets at periodic intervals from the second server to the first server; and

waiting for an acknowledgement signal in response to each packet for a specified period of time, wherein if the acknowledgement signal is received within the specified period of time, the first server is determined to be operational.

30. The method of claim 29 further comprising changing the host server attribute to name the first server as the host server of the program.

31. The method of claim 30 wherein the step of resuming execution of the program in the first server comprises:

unloading the program from a random access memory in the second server;

loading the program in a random access memory in the first server;

pausing execution of the program in the first server until it is verified that the program has been unloaded from the second server; and

verifying that the program has been unloaded from the second server.

32. The method of claim 31 wherein the acts of pausing, verifying and commencing are automatically performed by executing commands stored within the program.

33. The method of claim 32 wherein the act of verifying that the program has been unloaded from the second server comprises reading the host server attribute and determining that the host server status indicates the first server as the host server of the program.

34. The method of claim 18 wherein the act of executing the program in the second server comprises:

determining a first location within the program where execution of the program by the first server ceased; and

commencing execution of the program by the second server at the first location.

35. The method of claim 34 wherein the act of determining the first position comprises:

updating a pointer within the program as it is executed by the first server; and

determining the location of the pointer prior to execution of the program by the second server.

36. The method of claim 18 further comprising:

if it is determined that the second server does not have the specified resources, sending an error message to a system operator.

37. The method of claim 36 wherein the specified resources are identified in a list of resources which is part of the information contained within the object.

38. The method of claim 37 wherein the act of determining if the second server has access to specified resources necessary to execute the program, comprises comparing the list of resources to a list of resources initialized by a BIOS program stored within the second server.

39. The method of claim 37 wherein the act of determining if the second server has access to specified resources necessary to execute the program, comprises comparing the list of resources to a configuration file stored within the second server.

40. The method of claim 18 further comprising:

detecting when the first server is once again operational; and

resuming execution of the program in the first server upon detecting that the first server is once again operational.

41. The method of claim 40 wherein the act of detecting when the first server is once again operational, comprises:

tranmitting packets at periodic intervals from the second server to the first server; and

waiting for an acknowledgement signal in response to each packet for a specified period of time, wherein if the acknowledgement signal is received within the specified period of time, the first server is determined to be operational.

42. The method of claim 17 wherein the act of detecting a failure of the first server comprises:

tranmitting packets at periodic intervals from the second server to the first server; and

waiting for an acknowledgement signal in response to each packet for a specified period of time, wherein if the acknowledgement signal is not received within the specified period of time, the failure of the first server is detected.

43. The method of claim 17 wherein the act of detecting a failure of the first server comprises:

monitoring communications between the first server and a network resource; and

detecting a termination in the communication between the first server and the network resource.

44. The method of claim 17 wherein the act of detecting a failure of the first server comprises:

successively transmitting first and second command signals from the first server to a device coupled to the first server, wherein the first command signal places the device in a first status condition and the second command signal places the device in a second status condition; and

monitoring a status condition of the device with the second server, coupled to the device, wherein a change in the status condition of the device indicates that the first server is operational and a constant status condition indicates the failure of the first server.

45. A method for fault tolerant execution of an application program in a server network having a first server and a second server, comprising:

executing, in the first server, the application program;

prompting a system operator for information to be stored in a cluster network database, wherein the information comprises;

a host server attribute which identifies which server is currently executing the program;

a primary server attribute which identifies which server is primarily responsible for executing the program; and

a backup server attribute which identifies which server is a backup server for executing the program if the primary server experiences a failure;

determining if the first server has failed;

if it is determined that the first server has failed, initiating a failover procedure, comprising;

reading the backup server attribute in the object with the second server;

determining whether the backup server attribute names the second server as the backup server;

determining whether the second server has sufficient resources to execute the application program;

if the backup server status names the second server as the backup server, loading the program in the second server and determining if the first server is once again operational; and

if it is determined that the first server is once again operational, initiating a failback process, comprising;

unloading the program from a random access memory in the second server;

verifying that the program has been unloaded from the second server; and

loading the program in a random access memory in the first server after the program has been unloaded from the second server.

46. A method for fault tolerant execution of an application program in a server network having a first server and a second server, comprising:

executing the application program in the first server;

automatically storing an object in a cluster network database, wherein the object represents the program and contains information comprising;

a host server attribute which identifies which server is currently executing the program;

a primary server attribute which identifies which server is primarily responsible for executing the program; and

a backup server attribute which identifies which server is a backup server for executing the program if the primary server experiences a failure;

determining if the first server has failed;

if it is determined that the first server has failed, initiating a failover procedure, comprising;

determining whether the second server has sufficient resources to execute the application program;

reading the backup server attribute in the object with the second server;

determining whether the backup server attribute names the second server as the backup server;

if the backup server status names the second server as the backup server, loading the program in the second server;

executing the program in the second server;

determining if the first server is once again operational; and

if it is determined that the first server is once again operational, initiating a failback process, comprising;

unloading the program from a random access memory in the second server;

loading the program in a random access memory in the first server;

pausing execution of the program in the first server until it is verified that the program has been unloaded from the second server; and

verifying that the program has been unloaded from the second server.

47. The method of claim 46 wherein the act of storing an object which represents the program in a cluster network database is performed automatically by the program as it is executed in the first server, wherein the information is contained within the program and is automatically written into the object stored the cluster network database.

48. The method of claim 46 wherein the acts of pausing, verifying and commencing are automatically performed by executing commands stored within the program.

49. The method of claim 46 wherein:

the act of executing the program in the second server comprises;

determining a first location within the program where execution of the program by the first server ceased; and

commencing execution of the program by the second server at the first location; and

the act of executing the program by the first server after it is verified that the program has been unloaded from the second server, comprises;

determining a second location within the program where execution of the program by the second server ceased; and

commencing execution of the program by the first server at the second location.

50. The method of claim 49 wherein:

the act of determining the first position comprises;

updating a pointer within the program as it is executed by the first server; and

determining the location of the pointer prior to execution of the program by the second server; and

the act of determining the second position comprises;

updating the pointer within the program as it is executed by the second server; and

determining the location of the pointer prior to resuming execution of the program by the first server.

51. The method of claim 46 further comprising:

determining if the second server has access to specified resources necessary to execute the program; and

if it is determined that the second server does not have access to the specified resources, sending an error message to a system operator.

52. The method of claim 51 wherein the specified resources are identified in a list of resources which is part of the information contained within the object.

53. The method of claim 52 wherein the act of determining if the second server has access to specified resources necessary to execute the program, comprises comparing the list of resources to a list of resources initialized by a BIOS program stored within the second server.

54. The method of claim 52 wherein the act of determining if the second server has access to specified resources necessary to execute the program, comprises comparing the list of resources to a configuration file stored within the second server.

55. A method for fault tolerant execution of an application program in a server network having a first and second server, comprising:

executing the application program in the first server;

storing an object which represents the program in a cluster network database, wherein the object contains information pertaining to the program;

detecting a failure of the first server;

reading the information contained in the object; and

executing the application program in the second server upon detection of the failure of the first server, in accordance with the information in the object.

56. The method of claim 55 wherein the act of storing an object comprises:

storing a host server attribute which identifies which server is currently executing the program;

a primary server attribute which identifies which server is primarily responsible for executing the program; and

a backup server attribute which identifies which server is a backup server for executing the program if the primary server experiences a failure.

57. A method of providing fault tolerant execution of an application program in a server network having a first server and a second server, comprising:

executing, in said first server, said application program;

detecting a failure of said first server to properly run said application; and

automatically, without operator intervention, executing in said second server said application program in response to said detecting step upon determining that said second server has sufficient resources to execute the application program.

58. The method of claim 57 further comprising:

sensing correction of said failure of said first server; and

automatically, without operator intervention, executing said application program in said first server in response to said sensing step.

59. The method of claim 58 wherein said sensing is provided by said second server.

60. The method of claim 57 wherein said detecting is provided by said second server.

61. A method of providing fault tolerant execution of an application program in a server network having a first and second servers, comprising:

executing, in said first server, said application program;

detecting a fault in the first server; and

automatically, without operator intervention, executing, in said second server, said application program in response to said detecting step upon determining that the second server has sufficient resources to execute the application program.

62. The method of claim 61 further comprising:

sensing correction of said fault in said first server; and

automatically, without operator intervention, executing said application program in said first server in response to said sensing step.

63. The method of claim 62 wherein said sensing is provided by said second server.

64. The method of claim 61 wherein said detecting is provided by said second server.