Failover procedure for server system
DCFirst Claim
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.
3 Assignments
Litigations
1 Petition
Accused Products
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.
-
Citations
17 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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
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. - View Dependent Claims (10, 11, 12, 13, 14, 15, 16, 17)
-
Specification