Failover procedure for server system

• US 9,141,489 B2
• Filed: 06/10/2010
• Issued: 09/22/2015
• Est. Priority Date: 07/09/2009
• Status: Active Grant

• Current Assignee: Uniloc 2017 LLC (FIG LLC (d/b/a Fortress Investment Group LLC))
• Original Assignee: Uniloc Luxembourg S.à r.l. (f/k/a Uniloc Luxembourg S.A.) (Uniloc Corporation Pty. Limited)
• Inventors: Etchegoyen, Craig Stephen
• Primary Examiner(s): CHAO, MICHAEL W
• Application Number:
  US12/813,420
• Publication Number:
  US 20110010560A1
• Time in Patent Office: 1,930 Days
• Field of Search: 726/22
• US Class Current: 1/1
• CPC Class Codes: G06F 11/2025 using centralised failover control functionality
• CPC Class Codes: G06F 11/2038 with a single idle spare processing component
• CPC Class Codes: G06F 11/2041 with more than one idle spare processing component
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/28 using route fault recovery

Abstract

A failover procedure for a computer system includes steps for routing traffic from a routing device to a first server, storing in the routing device data representing a fingerprint of the first server, receiving periodically at the routing device a status message from the first server, detecting at the routing device an invalid status message from the first server by absence of the fingerprint in a status message from the first server within a predetermined time period after last receiving a valid status message, and routing the traffic from the routing device to a second server in response to detecting the invalid status message from the first server. A redundant server system implementing the failover procedure may include servers each capable of generating its fingerprint by reading current system configuration data.

Claims

1. A method for implementing a failover procedure for a computer system, comprising:

routing traffic from a routing device to a first server;

storing in the routing device data representing a fingerprint of the first server;

receiving periodically at the routing device a status message from the first server;

detecting at the routing device an invalid status message from the first server by absence of the fingerprint in a status message from the first server within a predetermined time period after last receiving a valid status message at the routing device; and

routing the traffic from the routing device to a second server in response to detecting the invalid status message from the first server.

2. The method of claim 1, wherein the detecting step further comprises comparing the status message received from the first server to the fingerprint stored on the routing device and determining that the status message is valid only if a fingerprint encoded in the status message received matches the fingerprint stored in the routing device.

3. The method of claim 2, further comprising

storing in the routing device data representing a fingerprint of the second server;

receiving periodically at the routing device a status message from the second server;

detecting at the routing device an invalid status message from the second server by absence of the second server fingerprint in a status message from the second server within a predetermined time period after last receiving a valid status message at the routing device; and

routing the traffic from the routing device to the first server in response to detecting the invalid status message from the second server.

4. The method of claim 2, further comprising, after receiving an invalid status message from the first server, restoring a secure tunnel from the routing device to the first server in response to detecting a valid status signal from the first server.

5. The method of claim 4, further comprising generating the fingerprint at the first server in response to routing the traffic from the routing device to the second server.

6. The method of claim 1, further comprising generating the fingerprint at the first server by reading system data indicating a current system configuration of the first server.

7. The method of claim 6, further comprising generating the first fingerprint by encrypting at least a portion of the system data using a cryptographic key.

8. The method of claim 1, further comprising transmitting the status message to the routing device via a secure tunnel.

9. A redundant server system with failover capability, comprising:

a first server and a second server, each configured with a first application for serving data to multiple clients and a second application for generating periodic status messages, each status message including a server fingerprint;

a routing device in secure communication with the first server and the second server, the routing device configured

to route traffic exclusively to a primary server of the first and second servers,

to receive the status messages from the first and second servers,

to compare the server fingerprint of a status message with a server fingerprint stored on the routing device; and

to change the primary server to another of the first and second servers in response to a comparison of the primary server fingerprint yielding a mismatch prior to the change.

10. The system of claim 9, wherein each of the first and second servers are each configured with an application for generating a hardware fingerprint by reading server system data indicating a current system configuration.

11. The system of claim 10, wherein the application for generating a hardware fingerprint is further configured for generating the hardware fingerprint by encrypting at least a portion of the server system data using a cryptographic key.

12. The system of claim 9, wherein the mismatch indicates the primary server is in a failure condition, and wherein each of the first and second servers is further configured to periodically transmit the status messages to the routing device at a designated frequency whenever not in a failure condition.

13. The system of claim 9, wherein the mismatch indicates the primary server is in a failure condition, and wherein each of the first and second servers further comprises a database replicating data stored in another of the first and second servers when neither one of the first and second servers is in a failure condition.

14. The system of claim 9, wherein each of the first and second servers further comprises a proxy server application managing communications with the routing device.

15. The system of claim 9, further comprising a second routing device in secure communication with the first server and the second server, the second routing device configured

to route traffic exclusively to a primary server of the first and second servers,

to receive the status messages from the first and second servers,

to compare the server fingerprint of a status message with a server fingerprint stored on the second routing device;

and

to change the primary server to another of the first and second servers in response to a comparison of the primary server fingerprint yielding a mismatch prior to the change.

16. The system of claim 9, further comprising at least one slave server in communication with the first and second servers.

17. The system of claim 16, further comprising at least one additional routing device in secure communication with the second server and with the at least one slave server, the at least one additional routing device configured

to route traffic from the at least one slave server exclusively to a primary server of the first and second servers,

to receive the status messages from the first and second servers, to compare the server fingerprint of a status message with a server fingerprint stored on the at least one additional routing device;

and

to change the primary server to another of the first and second servers in response to a comparison of the primary server fingerprint yielding a mismatch prior to the change.