Survivable and scalable data system and method for computer networks

• US 7,047,300 B1
• Filed: 02/10/1998
• Issued: 05/16/2006
• Est. Priority Date: 02/10/1998
• Status: Expired due to Term

• Current Assignee: Sprint Communications Company LP (Deutsche Telekom AG)
• Original Assignee: Sprint Communications Company LP (Deutsche Telekom AG)
• Inventors: Wells, Scott Christopher, Oehrke, Terry Lee, O'Brien, Michael Allen
• Primary Examiner(s): DINH, DUNG C
• Application Number:
  US09/021,466
• Time in Patent Office: 3,017 Days
• Field of Search: 709/224, 709/213, 709/214, 709/215, 709/208, 711/129, 711/153
• US Class Current: 709/226
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30

Abstract

A fully scalable and survivable network architecture and method is disclosed. In particular, a system for providing network or intranet processing and stored data access and an associated method is provided. The system includes a plurality of sets of at least first and second application processors. Each of the first and second processors within a set apply substantially the same application. One or more switches operatively connect to at least the first and second processors and a plurality of data storage devices. The data stored in the data storage device is associated with the application and mirrored, and at least the first and second processors operate at substantially the same time to obtain data. Both sources of mirrored data are operational at the same time to output data.

Claims

1. A scalable system for providing network processing and stored data access, the system comprising:

(a) at least first and second servers operative to process at least first and second user requests, respectively;

(b) a switch operatively connected to each of the servers;

(c) a load balancer operatively connected to each of the at least first and second servers, the load balancer operative to route an additional user request to the one of the at least first and second servers with the least load;

(d) a plurality of data storage devices operatively connected to the switch; and

(e) wherein the servers operate independently of the data storage devices and are connected to the data storage devices via the switch in a manner to permit the inclusion of an additional server to process another additional user request without the inclusion of an additional data storage device.

2. A scalable system for providing network processing and stored data access, the system comprising:

(a) at least first and second sets of servers, each of the sets of servers comprising at least first and second servers operative to process at least first and second user requests, respectively, and wherein each of the sets of servers applies a separate application;

(b) a switch operatively connected to each of the servers within each of the sets of servers;

(c) a plurality of data storage devices operatively connected to the switch;

(d) wherein the sets of servers operate independently of the data storage devices and are connected to the data storage devices via the switch in a manner to permit the inclusion of an additional server to any of the sets of servers to process at least an additional user request without the inclusion of an additional data storage device; and

(e) wherein each of the at least first and second servers of any one of the sets of servers applies an application, and wherein the system further comprises a load balancer operatively connected to each of the at least first and second servers of each of the sets of servers, the load balancer operative to route user requests to the one of the at least first and second servers of the sets of servers with the least load for a particular application.

3. A survivable system for providing network processing and stored data access, the system comprising:

(a) at least first and second servers operative to process at least first and second user requests, respectively,

(b) a switch operatively connected to each of the servers;

(c) a plurality of data storage devices operatively connected to the switch;

(d) wherein each of the first and second servers applies an application, the application applied by the first server being substantially the same as the application applied by the second server such that, in the event of a failure of either of the first and second servers, any subsequent user requests will be processed by any other of the servers that are operable; and

(e) wherein each of the plurality of data storage devices stores data, the data stored by each of the plurality of data storage devices being substantially the same such that, in the event of a failure of any one of the plurality of data storage devices, the data is accessible from any other of the plurality of data storage devices that are operable.

4. The system of claim 3 wherein the data stored by any one of the plurality of data storage devices is associated with an application applied by any one of the first and second servers.

5. The system of claim 3 wherein each of the at least first and second servers applies an application selected from the group consisting of:

a mail application, a news application, a directory application, a content application, a groupware application, and an internet protocol (IP) service.

6. The system of claim 3 further comprising a load balancer operatively connected to each of the at least first and second servers, the load balancer operative to route user requests to the one of the at least first and second servers corresponding to the server with the least load.

7. A method for providing network processing and stored data access, the method comprising the steps of:

(a) providing at least first and second servers operative to apply first and second applications, respectively, the first application being substantially the same as the second application;

(b) receiving first and second user requests on the first and second servers, respectively;

(c) applying the first and second applications to the first and second user requests, respectively, to generate first and second queries, respectively;

(d) providing at least first and second data storage devices configured to store first and second data, respectively, the first data being substantially the same as the second data;

(e) switching the first and second queries to the first and second data storage devices, respectively;

(f) routing first requested data from the first data storage device to the first server in response to the first query, and routing second requested data from the second data storage device to the second server in response to the second query;

(g) in the event of a failure of either of the first and second servers, processing any subsequent requests on any other of the servers that are operable; and

(h) in the event of a failure of either of the first and second data storage devices, providing any subsequent requested data from any other of the data storage devices that are operable.

8. The method of claim 7 wherein each of the first and second applications is selected from the group consisting of:

a mail application, a news application, a directory application, a content application, a groupware application, and an internet protocol (IP) service.