Context-based failover architecture for redundant servers

• US 5,996,086 A
• Filed: 10/14/1997
• Issued: 11/30/1999
• Est. Priority Date: 10/14/1997
• Status: Expired due to Term

• Current Assignee: NetApp, Inc.
• Original Assignee: LSI Logic Corporation (Broadcom, Inc.)
• Inventors: Delaney, William P., Spry, Andrew J., Fredin, Gerald J.
• Primary Examiner(s): Hua, Ly V.
• Assistant Examiner(s): HAMDAN, WASSEEM H
• Application Number:
  US08/949,678
• Time in Patent Office: 777 Days
• Field of Search: 714/22, 714/2, 714/3, 714/4, 714/6, 709/225, 710/15
• US Class Current: 714/4.11
• CPC Class Codes: G06F 11/2007 using redundant communication media
• CPC Class Codes: G06F 11/2023 Failover techniques
• CPC Class Codes: G06F 11/2033 switching over of hardware resources
• CPC Class Codes: G06F 11/2035 without idle spare hardware
• CPC Class Codes: G06F 11/2046 where the redundant components share persistent storage G06F11/2043 takes precedence

Abstract

In a redundant server network system, failover services for a failed server are provided by a survivor server belonging to a common failover group. At startup of a local server process running on the survivor server, a context is created for the local server and for each remote server belonging to the same failover group as the local server. At startup the context of the local server is also activated. The local server process is configured to operate on and make decisions based upon activated contexts. Each context includes server specific configuration and control information. When the survivor server must provide failover services for a failed server belonging to its same failover group, the context corresponding to the failed remote server is activated.

Claims

1. In a redundant server network system comprising a local server and a remote server belonging to a common failover group, a method for providing failover services for said remote server if said remote server fails, said method comprising the steps of:

creating and initializing a local server context based on local server configuration information associated with said local server that is stored on a first storage device;

activating said local server context;

becoming aware of a failure of said remote server;

acquiring a second storage device;

reading remote server configuration information associated with said remote server that is stored on said second storage device;

creating and initializing a failover context based on said remote server configuration information read from said second storage device;

activating said failover context; and

executing a server process on said local server which operates on, and makes decisions based upon, activated ones of said local server context and said failover context.

2. The method of claim 1, wherein:

said server process comprises a context-aware process configured to switch between each of said activated ones of said local server context and said failover context.

3. The method of claim 1, further comprising the step of:

starting up a failover context-specific process for said failover context on said survivor server when said failover context is activated, said failover context-specific process configured to operate on said failover context.

4. The method of claim 1, wherein:

said server process comprises a context-dumb process configured to be unaware of said plurality of contexts.

5. The method of claim 1, comprising the step of:

reading from a non-volatile storage device a location in said second storage device from which to read said failed server specific configuration information.

6. A network system for providing failover services for redundant servers, comprising:

a remote server coupled to a first storage device which stores remote server specific configuration information associated with said remote server;

a local server coupled to a first storage device which stores local server specific configuration information associated with said local server, said local server having ability to acquire said first storage device and to read said remote server configuration information;

a local server process comprising;

an initialization process for creating a local context based on said local server configuration information and a remote context based on said remote server configuration information, and for activating said local server context; and

a failover process for acquiring said first storage device, reading said remote server specific configuration information, creating and initializing a failover context, and activating said failover context when said local server is to provide failover services for said remote server;

said local server process executing on said local server by operating on, and making decisions based upon, activated ones of said local server context and said failover context activated ones of said local context and said remote context.

7. The system of claim 6, comprising:

a non-volatile storage device comprising a first variable which indicates a location of said remote server specific configuration information on said first storage device.

8. The system of claim 7, wherein:

said non-volatile storage device comprises a second variable which indicates a location of said local server specific configuration information on said second storage device.

9. The system of claim 6, wherein:

said remote server serves shared files on said first storage device; and

said failover process is configured to cause said shared files to be served by said local server.

10. The system of claim 9, wherein:

said failover process starts up a failover context-specific process for said remote context on said local server, said failover context-specific process configured to operate on said remote context.

11. The system of claim 6, wherein:

said server process comprises a context-dumb process, said failover context-dumb process being configured to be unaware of said local context or said remote context.

12. A server process for providing failover services in a redundant server network system, said network system comprising a local server and a remote server belonging to a common failover group, said local server coupled to a first storage device which stores local server specific configuration information and said remote server coupled to a second storate device which stores remote server specific configuration information, said server process executing locally on said local server, said server process comprising:

an initialization process for creating a a local server context based on said local server specific configuration information stored on said first storage device, and for activating said local server context; and

a failover process for acquiring said second storage device, reading said remote server specific configuration information from said second storage device, creating and initializing a failover context based on said remote server specific configuration information, and activating said failover context when said local server is to provide failover services for said remote server; and

and execution process which cycles through, operates on, and makes decisions based upon, activated ones of said local server context and said failover context.

13. The server process of claim 12, wherein:

said failover process starts up a failover context-specific process for said remote context on said local server, said failover context-specific process configured to operate on said failover context.

14. The system of claim 13, further comprising:

a context-dumb process configured to be unaware of said local context and said failover context.

15. The server process of claim 12, further comprising:

a context-dumb process configured to be unaware of said local context and said failover context.