CA2356633C - Coordinating persistent status information with multiple file servers - Google Patents
Coordinating persistent status information with multiple file servers Download PDFInfo
- Publication number
- CA2356633C CA2356633C CA002356633A CA2356633A CA2356633C CA 2356633 C CA2356633 C CA 2356633C CA 002356633 A CA002356633 A CA 002356633A CA 2356633 A CA2356633 A CA 2356633A CA 2356633 C CA2356633 C CA 2356633C
- Authority
- CA
- Canada
- Prior art keywords
- server
- file server
- messages
- state
- storage devices
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/2002—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where interconnections or communication control functionality are redundant
- G06F11/2007—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where interconnections or communication control functionality are redundant using redundant communication media
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/142—Reconfiguring to eliminate the error
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/2097—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements maintaining the standby controller/processing unit updated
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
- G06F11/2023—Failover techniques
- G06F11/2033—Failover techniques switching over of hardware resources
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
- G06F11/2041—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant with more than one idle spare processing component
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
- G06F11/2048—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant where the redundant components share neither address space nor persistent storage
Abstract
The invention provides a storage system, and a method for operating a storag e system, that provides for relatively rapid and reliable takeover among a plurality of independent file servers. Each file server maintains a reliable communication path to the others. Each file server maintains its own state in reliable memory. Each file server regularl y confirms the state of the other file servers. Each file server labels messages on the redundant communication paths, so as to allow other file servers to combine the redundant communication paths into a single ordered stream of messages. Each file server maintains its own state in its persistent memory and compares that state with the ordered stream of messages, so as to determine whether other file server s have progressed beyond the file server's own last known state. Each file server uses the shared resources (such as magnetic disks) themselves as part of the redundant communication paths, so as to prevent mutual attempts at takeover of resources when each file server believes the other to have failed. Each file server provides a status report to the others when recovering from an error, so as to prevent the possibility of multiple file servers each repeatedly failing and attempting to seize the resources of the others.
Description
Title of the Invention Coordinating Persistent Status Information with Multiple File Servers BackQround of the Invention 1. Field of the Invention io The invention relates to computer systems.
2. Related Art Computer storage systems are used to record and retrieve data. It is desirable for the services and data provided by the storage system to be available for service to the greatest degree possible. Accordingly, some computer storage systems provide a plurality of file servers, with the property that when a first file server fails, a second file server is available to provide the services and the data otherwise provided by the first. The second file server provides these services and data by takeover of resources otherwise managed by the first file server.
One problem in the known art is that when two file servers each provide backup for the other, it is important that each of the two file servers is able to reliably detect failure of the other and to smoothly handle any required takeover operations. It would be advantageous for this to occur without either of the two file servers interfering with proper operation of the other. This problem is particularly acute in systems when one or both file servers recover from a service interruption.
Accordingly, it would be advantageous to provide a storage system and a method for operating a storage system, that provides for relatively rapid and reliable takeover among a plurality of independent: file servers. This advantage is achieved in an embodiment of the invention in which each file server (a) maintains redundant communication paths to the others, (b) maintains its own state in persistent memory at least some of which is accessible to the others, and (c) regularly confirms the state of the other file servers.
Summary of the Invention The invention provides a storage system and a method for operating a storage system, that provides for relatively rapid and reliable takeover among a plurality of independent file servers. Each file server maintains a reliable (such as redundant) io communication path to the others, preventing any single point of failure in communication among file servers. Each file server maintains its own state in reliable (such as persistent) memory at least some of which is accessible to the others, providing a method for confirming that its own state information is up to date, and for reconstructing proper state infonmation if not. Each file server regularly confirms the state of the other file servers, and attempts takeover operations only when the other file servers are clearly unable to provide their share of services.
In a preferred embodiment, each file server sequences messages on the redundant communication paths, so as to allow other file servers to combine the 2o redundant communication paths into a single ordered stream of messages.
Each file server maintains its own state in its persistent memory and compares that state with the ordered stream of messages, so as to determine whether other file servers have progressed beyond the file server's own last known state. Each file server uses the shared resources (such as magnetic disks) themselves as part of the redundant communication paths, so as to prevent mutual attempts at takeover of resources when each file server believes the other to have failed.
In accordance with an aspect of the present invention there is provided a file server including a set of storage devices capable of being shared with a second file server; a controller disposed for coupling to said shared set of storage devices; a transceiver disposed for coupling to a communication path and for communicating messages using said communication path, said communication path using said shared set of storage devices to communicate said messages;
and a takeover monitor coupled to at least part of said shared set of storage devices, and responsive to said communication path and said shared set of storage devices.
In accordance with another aspect of the present invention there is provided apparatus including a shared resource; a pair of servers comprising a first server and a second server, each coupled to said shared resource and each disposed for managing at least part of said shared resource;
and a communication path disposed for coupling a sequence of messages between said pair, said communication path disposed for using said shared resource for coupling said sequence of messages; each one of said pair being disposed for takeover of at least part of said shared resource in response to said communication path; wherein said sequence of messages prevents both of said pair from concurrently performing said takeover.
In accordance with yet another aspect of the present invention there is provided a method for operating a file server, said method including steps for controlling a shared resource comprising a subset of a set of shared storage devices; receiving and transmitting messages with a second file server, said steps for receiving and transmitting using a communication path including said shared storage devices; monitoring said communicating path - 2a -and said shared storage devices; storing state information about said file server in a persistent memory; and performing a takeover operation of said shared resource in response to said steps for monitoring and a state of said persistent memory.
In accordance with yet another aspect of the present invention there is provided a method including steps for managing at a first server at least a part of a shared resource; receiving and transmitting a sequence of messages between said first server to a second server, using said shared resource; and performing a takeover operation at a first server of at least part of said shared resource in response to said sequence of messages; wherein said steps for receiving and transmitting prevent both of said first server and said second server from concurrently performing said takeover operation.
In accordance with yet another aspect of the present invention there is provided a memory, including a set of instructions, wherein said set of instructions are executable by a processor to operate a first file server, said set of instructions comprising: controlling a shared resource comprising a subset of a set of shared storage devices; receiving and transmitting a sequence of messages with a second file server, said steps for receiving and transmitting using a communication path including said shared storage devices; monitoring said communication path and said shared storage devices; storing state information about said first file server in a persistent memory; and performing a takeover operation of said shared resource in response to said instructions for monitoring and a state of said persistent memory.
- 2b -In accordance with yet another aspect of the present invention there is provided a file server, including: an interface to a set of mass storage devices and to at least one network; and a processor and controller disposed to access said mass storage devices, to communicate messages with at least a second file server that has access to said mass storage devices, and to process state information about said server and said second file server;
wherein said messages are used to communicate said state information to and from said second file server, and wherein said messages are sent over plural different communication paths including at least part of said mass storage devices and said network.
In accordance with yet another aspect of the present invention there is provided a method of controlling a file server, comprising the steps of: accessing a set of mass storage devices; communicating messages with at least a second file server that has access to said mass storage devices; and processing state information about said server and said second file server; wherein said messages are used to communicate said state information to and from said second file server, and wherein said messages are sent over plural different communication paths including at least part of said mass storage devices and a network.
In accordance with yet another aspect of the present invention there is provided a memory storing information including instructions, the instructions executable by a processor to control a file server, the instructions comprising the steps of: accessing a set of mass storage devices; communicating messages with at least a second file server that has access to said mass storage devices; and processing state information about said server - 2c -and said second file server; wherein said messages are used to communicate said state information to and from said second file server, and wherein said messages are sent over plural different communication paths including at least part of said mass storage devices and a network.
In a preferred embodiment, each file server provides a status report to the others when recovering from an error, so as to prevent the possibility of multiple file servers each repeatedly failing and attempting to seize the resources of the others.
- 2d -Brief Description of the Drawings Figure 1 shows a block diagram of a multiple file server system with coordinated persistent status information.
Figure 2 shows a state diagram of a method of operation for a multiple file server system with coordinated persistent status information.
Detailed Description of the Preferred Embodiment In the following description, a preferred embodiment of the invention is described with regard to preferred process steps and data structures. However, those skilled in the art would recognize, after perusal of this application, that embodiments of the invention may be implemented using one or more general purpose processors (or special purpose processors adapted to the particular process steps and data structures) operating under program control, and that implementation of the preferred process steps and data structures described herein using such equipment would not require undue experimentation or further invention.
In a preferred embodiment, the file server system, and each file server therein, operates using inventions described in the following patent application:
International Application No. PCT/US99/05071, filed March 8, 1999, in the name of Network Appliance Inc., title "Highly Available File Servers," International Publication No.
WO 99/46680.
This application is referred to as the "Clustering Disclosure."
One problem in the known art is that when two file servers each provide backup for the other, it is important that each of the two file servers is able to reliably detect failure of the other and to smoothly handle any required takeover operations. It would be advantageous for this to occur without either of the two file servers interfering with proper operation of the other. This problem is particularly acute in systems when one or both file servers recover from a service interruption.
Accordingly, it would be advantageous to provide a storage system and a method for operating a storage system, that provides for relatively rapid and reliable takeover among a plurality of independent: file servers. This advantage is achieved in an embodiment of the invention in which each file server (a) maintains redundant communication paths to the others, (b) maintains its own state in persistent memory at least some of which is accessible to the others, and (c) regularly confirms the state of the other file servers.
Summary of the Invention The invention provides a storage system and a method for operating a storage system, that provides for relatively rapid and reliable takeover among a plurality of independent file servers. Each file server maintains a reliable (such as redundant) io communication path to the others, preventing any single point of failure in communication among file servers. Each file server maintains its own state in reliable (such as persistent) memory at least some of which is accessible to the others, providing a method for confirming that its own state information is up to date, and for reconstructing proper state infonmation if not. Each file server regularly confirms the state of the other file servers, and attempts takeover operations only when the other file servers are clearly unable to provide their share of services.
In a preferred embodiment, each file server sequences messages on the redundant communication paths, so as to allow other file servers to combine the 2o redundant communication paths into a single ordered stream of messages.
Each file server maintains its own state in its persistent memory and compares that state with the ordered stream of messages, so as to determine whether other file servers have progressed beyond the file server's own last known state. Each file server uses the shared resources (such as magnetic disks) themselves as part of the redundant communication paths, so as to prevent mutual attempts at takeover of resources when each file server believes the other to have failed.
In accordance with an aspect of the present invention there is provided a file server including a set of storage devices capable of being shared with a second file server; a controller disposed for coupling to said shared set of storage devices; a transceiver disposed for coupling to a communication path and for communicating messages using said communication path, said communication path using said shared set of storage devices to communicate said messages;
and a takeover monitor coupled to at least part of said shared set of storage devices, and responsive to said communication path and said shared set of storage devices.
In accordance with another aspect of the present invention there is provided apparatus including a shared resource; a pair of servers comprising a first server and a second server, each coupled to said shared resource and each disposed for managing at least part of said shared resource;
and a communication path disposed for coupling a sequence of messages between said pair, said communication path disposed for using said shared resource for coupling said sequence of messages; each one of said pair being disposed for takeover of at least part of said shared resource in response to said communication path; wherein said sequence of messages prevents both of said pair from concurrently performing said takeover.
In accordance with yet another aspect of the present invention there is provided a method for operating a file server, said method including steps for controlling a shared resource comprising a subset of a set of shared storage devices; receiving and transmitting messages with a second file server, said steps for receiving and transmitting using a communication path including said shared storage devices; monitoring said communicating path - 2a -and said shared storage devices; storing state information about said file server in a persistent memory; and performing a takeover operation of said shared resource in response to said steps for monitoring and a state of said persistent memory.
In accordance with yet another aspect of the present invention there is provided a method including steps for managing at a first server at least a part of a shared resource; receiving and transmitting a sequence of messages between said first server to a second server, using said shared resource; and performing a takeover operation at a first server of at least part of said shared resource in response to said sequence of messages; wherein said steps for receiving and transmitting prevent both of said first server and said second server from concurrently performing said takeover operation.
In accordance with yet another aspect of the present invention there is provided a memory, including a set of instructions, wherein said set of instructions are executable by a processor to operate a first file server, said set of instructions comprising: controlling a shared resource comprising a subset of a set of shared storage devices; receiving and transmitting a sequence of messages with a second file server, said steps for receiving and transmitting using a communication path including said shared storage devices; monitoring said communication path and said shared storage devices; storing state information about said first file server in a persistent memory; and performing a takeover operation of said shared resource in response to said instructions for monitoring and a state of said persistent memory.
- 2b -In accordance with yet another aspect of the present invention there is provided a file server, including: an interface to a set of mass storage devices and to at least one network; and a processor and controller disposed to access said mass storage devices, to communicate messages with at least a second file server that has access to said mass storage devices, and to process state information about said server and said second file server;
wherein said messages are used to communicate said state information to and from said second file server, and wherein said messages are sent over plural different communication paths including at least part of said mass storage devices and said network.
In accordance with yet another aspect of the present invention there is provided a method of controlling a file server, comprising the steps of: accessing a set of mass storage devices; communicating messages with at least a second file server that has access to said mass storage devices; and processing state information about said server and said second file server; wherein said messages are used to communicate said state information to and from said second file server, and wherein said messages are sent over plural different communication paths including at least part of said mass storage devices and a network.
In accordance with yet another aspect of the present invention there is provided a memory storing information including instructions, the instructions executable by a processor to control a file server, the instructions comprising the steps of: accessing a set of mass storage devices; communicating messages with at least a second file server that has access to said mass storage devices; and processing state information about said server - 2c -and said second file server; wherein said messages are used to communicate said state information to and from said second file server, and wherein said messages are sent over plural different communication paths including at least part of said mass storage devices and a network.
In a preferred embodiment, each file server provides a status report to the others when recovering from an error, so as to prevent the possibility of multiple file servers each repeatedly failing and attempting to seize the resources of the others.
- 2d -Brief Description of the Drawings Figure 1 shows a block diagram of a multiple file server system with coordinated persistent status information.
Figure 2 shows a state diagram of a method of operation for a multiple file server system with coordinated persistent status information.
Detailed Description of the Preferred Embodiment In the following description, a preferred embodiment of the invention is described with regard to preferred process steps and data structures. However, those skilled in the art would recognize, after perusal of this application, that embodiments of the invention may be implemented using one or more general purpose processors (or special purpose processors adapted to the particular process steps and data structures) operating under program control, and that implementation of the preferred process steps and data structures described herein using such equipment would not require undue experimentation or further invention.
In a preferred embodiment, the file server system, and each file server therein, operates using inventions described in the following patent application:
International Application No. PCT/US99/05071, filed March 8, 1999, in the name of Network Appliance Inc., title "Highly Available File Servers," International Publication No.
WO 99/46680.
This application is referred to as the "Clustering Disclosure."
In a preferred embodiment, each file server in the file server system controls its associated mass storage devices so as to form a redundant array, such as a RAID storage system, using inventions described in the following patent applications:
Application Serial No. 08/471,218, filed June 5, 1995, in the name of inventors David Hitz et al, title "A
Method for Providing Parity in a Raid Sub-System Using Non-Volatile Memory", now U.S. Patent No. 5,948,110, issued September 7, 1999;
Application Serial No. 08/454,921, filed May 31, 1995, in the name of inventors David Hitz et al., titled "Method for Maintaining Consistent States of a File System and for Creating User-Accessible Read-Only Copies of a File System," now U.S. Patent No. 5,819,292 issued October 6, 1998;
Application Serial No. 08/464,591, filed May 31, 1995, in the name of inventors David Hitz et al., titled "Method for Allocating Files in a File System Integrated with a Raid Disk Sub-System", now U.S. Patent No. 6,038,570, issued March 14, 2000.
These applications are collectively referred to as the "WAFL Disclosures".
System Elements Figure 1 shows a block diagram of a multiple file server system with coordinated persistent status information.
A system 100 includes a plurality of file servers 110, a plurality of mass storage devices 120, a SAN (system area network) 130, and a PN (public network) 140.
Application Serial No. 08/471,218, filed June 5, 1995, in the name of inventors David Hitz et al, title "A
Method for Providing Parity in a Raid Sub-System Using Non-Volatile Memory", now U.S. Patent No. 5,948,110, issued September 7, 1999;
Application Serial No. 08/454,921, filed May 31, 1995, in the name of inventors David Hitz et al., titled "Method for Maintaining Consistent States of a File System and for Creating User-Accessible Read-Only Copies of a File System," now U.S. Patent No. 5,819,292 issued October 6, 1998;
Application Serial No. 08/464,591, filed May 31, 1995, in the name of inventors David Hitz et al., titled "Method for Allocating Files in a File System Integrated with a Raid Disk Sub-System", now U.S. Patent No. 6,038,570, issued March 14, 2000.
These applications are collectively referred to as the "WAFL Disclosures".
System Elements Figure 1 shows a block diagram of a multiple file server system with coordinated persistent status information.
A system 100 includes a plurality of file servers 110, a plurality of mass storage devices 120, a SAN (system area network) 130, and a PN (public network) 140.
In a preferred embodiment, there are exactly two file servers 110. Each file server 110 is capable of acting independently with regard to the mass storage devices 120. Each file server 110 is disposed for receiving file server requests from client devices (not shown), for performing operations on the mass storage devices 120 in response thereto, and for transmitting responses to the file server requests to the client devices.
For example, in a preferred embodiment, the file servers 110 are each similar to file servers described in the Clustering Disclosures.
- 4a -Each of the file servers 110 includes a processor 111, program and data memory 112, and a persistent memory 113 for maintaining state information across possible service interruptions. In a preferred embodiment, the persistent memory 113 includes a nonvolatile RAM.
The mass storage devices 120 preferably include a plurality of writeable magnetic disks, magneto-optical disks, or optical disks. In a preferred embodiment, the mass storage devices 120 are disposed in a RAID configuration or other system for maintaining information persistent across possible service interruptions.
Each of the mass storage devices 120 are coupled to each of the file servers 110 using a mass storage bus 121. In a preferred embodiment, each file server 110 has its own mass storage bus 121. The first file server 110 is coupled to the mass storage devices 120 so as to be a primary controller for a first subset of the mass storage devices 120 and a secondary controller for a second subset thereof. The second file server 110 is coupled to the mass storage devices 120 so as to be a primary controller for the second subset of the mass storage devices 120 and a secondary controller for the first subset thereof.
The mass storage bus 121 associated with each file server 110 is coupled to the processor 111 for that file server 110 so that file server 110 can control mass storage devices 120. In alternative embodiments, the file servers 110 may be coupled to the mass storage devices 120 using other techniques, such as fiber channel switches or switched fabrics.
The mass storage devices 120 are disposed to include a plurality of mailbox disks 122, each of which has at least one designated region 123 into which one file server 110 can write messages 124 for reading by the other file server 110. In a preferred embodiment, there is at least one designated region 123, on each mailbox disk 122 for 3o reading and at least one designated region 123 for writing, by each file server 110.
For example, in a preferred embodiment, the file servers 110 are each similar to file servers described in the Clustering Disclosures.
- 4a -Each of the file servers 110 includes a processor 111, program and data memory 112, and a persistent memory 113 for maintaining state information across possible service interruptions. In a preferred embodiment, the persistent memory 113 includes a nonvolatile RAM.
The mass storage devices 120 preferably include a plurality of writeable magnetic disks, magneto-optical disks, or optical disks. In a preferred embodiment, the mass storage devices 120 are disposed in a RAID configuration or other system for maintaining information persistent across possible service interruptions.
Each of the mass storage devices 120 are coupled to each of the file servers 110 using a mass storage bus 121. In a preferred embodiment, each file server 110 has its own mass storage bus 121. The first file server 110 is coupled to the mass storage devices 120 so as to be a primary controller for a first subset of the mass storage devices 120 and a secondary controller for a second subset thereof. The second file server 110 is coupled to the mass storage devices 120 so as to be a primary controller for the second subset of the mass storage devices 120 and a secondary controller for the first subset thereof.
The mass storage bus 121 associated with each file server 110 is coupled to the processor 111 for that file server 110 so that file server 110 can control mass storage devices 120. In alternative embodiments, the file servers 110 may be coupled to the mass storage devices 120 using other techniques, such as fiber channel switches or switched fabrics.
The mass storage devices 120 are disposed to include a plurality of mailbox disks 122, each of which has at least one designated region 123 into which one file server 110 can write messages 124 for reading by the other file server 110. In a preferred embodiment, there is at least one designated region 123, on each mailbox disk 122 for 3o reading and at least one designated region 123 for writing, by each file server 110.
The SAN 130 is coupled to the processor 111 and to the persistent memory 113 at each of the file servers 110.
The SAN 130 is disposed to transmit messages 124 from the processor 111 at the first file server 110 to the persistent memory 113 at the second file server 110. Similarly, the SAN 130 is disposed to transmit messages 124 from the processor 111 at the second file server 110 to the persistent memory 113 at the first file server 110.
In a preferred embodiment, the SAN 130 comprises a ServerNet connection between the two file servers 110. In alternative embodiments, the persistent memory 112 may be disposed logically remote to the file servers 110 and accessible using the SAN 130.
The PN 140 is coupled to the processor 111 at each of the file servers 110. The PN 140 is disposed to transmit messages 124 from each file server 110 to the other file server 110.
In a preferred embodiment, the PN 140 can comprise a direct communication channel, a LAN (local area network), a WAN (wide area network), or some combination thereof.
Although the mass storage devices 120, the SAN 130, and the PN 140 are each disposed to transmit messages 124, the messages 124 transmitted using each of these pathways between the file servers 110 can have substantially differing formats, even though payload for those messages 124 is identical.
The SAN 130 is disposed to transmit messages 124 from the processor 111 at the first file server 110 to the persistent memory 113 at the second file server 110. Similarly, the SAN 130 is disposed to transmit messages 124 from the processor 111 at the second file server 110 to the persistent memory 113 at the first file server 110.
In a preferred embodiment, the SAN 130 comprises a ServerNet connection between the two file servers 110. In alternative embodiments, the persistent memory 112 may be disposed logically remote to the file servers 110 and accessible using the SAN 130.
The PN 140 is coupled to the processor 111 at each of the file servers 110. The PN 140 is disposed to transmit messages 124 from each file server 110 to the other file server 110.
In a preferred embodiment, the PN 140 can comprise a direct communication channel, a LAN (local area network), a WAN (wide area network), or some combination thereof.
Although the mass storage devices 120, the SAN 130, and the PN 140 are each disposed to transmit messages 124, the messages 124 transmitted using each of these pathways between the file servers 110 can have substantially differing formats, even though payload for those messages 124 is identical.
Method of Operation Figure 2 shows a state diagram of a method of operation for a multiple file server system with coordinated persistent status information.
- 6a -A state diagram 200 includes a plurality of states and a plurality of transitions there between. Each transition is from a first state to a second state and occurs upon detection of a selected event.
s The state diagram 200 is followed by each of the file servers 110 independently. Thus, there is a state for. "this" file server 110 and another (possibly same, possibly different) state for the "the other" file server 110. Each file server I 10 independently determines what transition to follow from each state to its own next state.
The state diagram 200 is described herein with regard to "this" file server 110.
In a NORMAL state 210, this file server 110 has control of its own assigned mass storage devices 120.
In a TAKEOVER state 220. this file server 110 has taken over control of 1s the mass storage devices 120 normally assigned to the other file server 110.
In a STOPPED state 230, this file server 110 has control of none of the mass storage devices 120 and is not operational.
In a REBOOTING state 240, this file server 110 has control of none of the mass storage devices 120 and is recovering from a service interruption.
NORMAL State In the NORMAL state 210, both file servers 110 are operating properly, and each controls its set of mass storage devices 120.
In this state, each file server 110 periodically sends state information in messages 124 using the redundant comniunication paths between the two file servers 110. Thus, each file server 110 periodically transmits messages 124 having state information by the following techniques:
- 6a -A state diagram 200 includes a plurality of states and a plurality of transitions there between. Each transition is from a first state to a second state and occurs upon detection of a selected event.
s The state diagram 200 is followed by each of the file servers 110 independently. Thus, there is a state for. "this" file server 110 and another (possibly same, possibly different) state for the "the other" file server 110. Each file server I 10 independently determines what transition to follow from each state to its own next state.
The state diagram 200 is described herein with regard to "this" file server 110.
In a NORMAL state 210, this file server 110 has control of its own assigned mass storage devices 120.
In a TAKEOVER state 220. this file server 110 has taken over control of 1s the mass storage devices 120 normally assigned to the other file server 110.
In a STOPPED state 230, this file server 110 has control of none of the mass storage devices 120 and is not operational.
In a REBOOTING state 240, this file server 110 has control of none of the mass storage devices 120 and is recovering from a service interruption.
NORMAL State In the NORMAL state 210, both file servers 110 are operating properly, and each controls its set of mass storage devices 120.
In this state, each file server 110 periodically sends state information in messages 124 using the redundant comniunication paths between the two file servers 110. Thus, each file server 110 periodically transmits messages 124 having state information by the following techniques:
o Each file server 110 transmits a inessage 124 by copying that message to the mailbox disks on its assigned mass storage devices 120.
In a preferred embodiment, messages 124 are transmitted using the mailbox disks by writing the messages 124 to a first mailbox disk and then to a second mailbox disk.
o Each file server I 10 transmits a message 124 by copying that message 124, using the SAN 130, to its persistent memory 113 (possibly both its own persistent io memory 113 and that for the other file server 110).
In a preferred embodiment, messages 124 are transmitted using the SAN 130 using a NUMA technique.
and o Each file server 110 transmits a message 124 by transmitting that message 124, using the PN 140, to the other file server 110.
In a preferred embodiment, messages 124 are transmitted using the PN 140 using encapsulation in a communication protocol known to both file servers 110, such as UDP or IP.
Each message 124 includes the following information for "this" file server I 10 (that is, the file server 110 transmitting the message 124):
o a system ID for this file server 110;
o a state indicator for this file server 1.10;
In a preferred embodiment, the state indicator can be one of the following:
(NORMAL) operating normally, (TAKEOVER) this file server 110 has taken over control of the mass storage devices 120, (NO-TAKEOVER) this file server 110 does not want the receiving file server to take over control of its mass storage devices 120, and (DISABLE) takeover is disabled for both file servers 110.
o a generation number Gi, comprising a monotonically increasing number identified with a current instantiation of this file server 110;
In a preferred embodiment, the instantiation of this file server 110 is incremented when this file server 110 is initiated on boot-up. If any file server 110 suffers a service interruption that involves reinitialization, the generation number Gi will be incremented, and the message 124 will indicate that it is subsequent to any message 124 send before the service interruption.
and o a sequence number Si, comprising a monotonically increasing number identified with the current message 124 transmitted by this file server 110.
Similarly, each message 124 includes the following information for "the other" file server 110 (that is, the file server 110 receiving the message 124):
o a generation number Gi, comprising a monotonically increasing number identified with a current instantiation of the other file server 110;
and o a sequence number Si, comprising a monotonically increasing number identified with the most recent message 124 received from the other file server 110.
In a preferred embodiment, messages 124 are transmitted using the mailbox disks by writing the messages 124 to a first mailbox disk and then to a second mailbox disk.
o Each file server I 10 transmits a message 124 by copying that message 124, using the SAN 130, to its persistent memory 113 (possibly both its own persistent io memory 113 and that for the other file server 110).
In a preferred embodiment, messages 124 are transmitted using the SAN 130 using a NUMA technique.
and o Each file server 110 transmits a message 124 by transmitting that message 124, using the PN 140, to the other file server 110.
In a preferred embodiment, messages 124 are transmitted using the PN 140 using encapsulation in a communication protocol known to both file servers 110, such as UDP or IP.
Each message 124 includes the following information for "this" file server I 10 (that is, the file server 110 transmitting the message 124):
o a system ID for this file server 110;
o a state indicator for this file server 1.10;
In a preferred embodiment, the state indicator can be one of the following:
(NORMAL) operating normally, (TAKEOVER) this file server 110 has taken over control of the mass storage devices 120, (NO-TAKEOVER) this file server 110 does not want the receiving file server to take over control of its mass storage devices 120, and (DISABLE) takeover is disabled for both file servers 110.
o a generation number Gi, comprising a monotonically increasing number identified with a current instantiation of this file server 110;
In a preferred embodiment, the instantiation of this file server 110 is incremented when this file server 110 is initiated on boot-up. If any file server 110 suffers a service interruption that involves reinitialization, the generation number Gi will be incremented, and the message 124 will indicate that it is subsequent to any message 124 send before the service interruption.
and o a sequence number Si, comprising a monotonically increasing number identified with the current message 124 transmitted by this file server 110.
Similarly, each message 124 includes the following information for "the other" file server 110 (that is, the file server 110 receiving the message 124):
o a generation number Gi, comprising a monotonically increasing number identified with a current instantiation of the other file server 110;
and o a sequence number Si, comprising a monotonically increasing number identified with the most recent message 124 received from the other file server 110.
Each message 124 also includes a version number of the status protocol with which the message 124 is transmitted.
Since the file server 110 receives the messages 124 using a plurality of pathways, it determines for each message 124 whether or not that message 124 is "new"
(the file server 110 has not seen it before), or "old" (the file server 110 has seen it before). The file server 110 maintains a record of the generation number Gi and the sequence number Si of the most recent new message 124. The file server 110 determines that the particular message 124 is new if aiid only if:
o its generation number Gi is greater than the most recent new message 124;
or o its generation number Gi is equal to the most recent new message 124 and its sequence number Si is greater than most recent new message 124.
If either of the file servers 110 determines that the message 124 is not new, that file server 110 can ignore that message 124.
In this state, each file server 110 periodically saves its own state information using the messages 124. Thus, each file server 110 records its state information both on its own mailbox disks and in its own persistent memory 113.
In this state, each file server 110 periodically watches for a state change in the other file server 110. The first file server I 10 detects a state change in the second file server 110 in one of at least two ways:
o The first file server I 10 notes that the second file server 110 has not updated its state information (using a message 124) for a timeout period.
In a preferred embodiment, this timeout period is two-half seconds for communication using the mailbox disks and one-half second for communication using the SAN 130. However, there is no particular requirement for using these timeout values; in alternative embodiments, different timeout values or techniques other than timeout periods may be used.
and o The first file server 110 notes that the second file server 110 has updated its state information (using one or more messages 124) to indicate that the second file server 110 has changed its state.
In a preferred embodiment, the second file server 110 indicates when it is in one of the states described with regard to each message 124.
If the first file server 110 determines that the second file server 110 is also in the NORMAL state, the NORMAL-OPERATION transition 211 is taken to remain in the state 210.
The first file server 110 makes its determination responsive to messages 124 it receives from the second file server 110. If there are no such messages 124 for a time period responsive to the timeout period described above (such as two to five times the timeout period), the first file server 110 decides that the second file server 110 has suffered a service interruption.
If the first file server 110 determines that the second file server 110 has suffered a service interruption (that is, the second file server 110 is in the STOPPED state 230), the TAKEOVER-OPERATION transition 212 is taken to enter the TAKEOVER
state 220.
The TAKEOVER-OPERATION transition 212 can be disabled by a message 124 state indicator such as DISAI3LE or NO-TAKEOVER.
In a preferred embodiment, either file server 110 can disable the TAKEOVER-OPERATION transition 212 responsive to (a) an operator command, (b) a synchronization error between the persistent memories 113, or (c) any compatibility mismatch between the file servers 110.
To perform the TAKEOVEI.t-OPERATION transition 212, this file server 110 performs the following actions at a step 213:
o This file server 110 sends the message 124 state indicator TAKEOVER to the other file server 110, using including the reliable communication path (including the mailbox disks 122, the SAN 130, and the PN 140).
o This file server 110 waits for the other file server 110 to have the opportunity to receive and act on the TAKEOVER-OPERATION transition 212 (that is, to suspend its own access to the mass storage devices 120.
o This file server 110 issues disk reservation commands to the mass storage devices 120 normally assigned to the other file server 110.
o This file server 110 takes any other appropriate action to assure that the other file server 110 is passive.
If the takeover operation is successful, the TAKEOVER-OPERATION
transition 212 completes and this file server enters the TAKEOVER state 220.
Otherwise (such as if takeover is disabled), this file server 110 returns to the NORMAL
state 210.
TAKEOVER State In the TAKEOVER state 220, this file server 110 is operating properly, but the other file server 110 is not. This file server 110 has taken over control of both its and the other's mass storage devices 120.
In this state, this file server 110 continues to write messages 124 to the persistent memory 113 and to the mailbox disks 122, so as to preserve its own state in the event of a service interruption.
In this state, this file server 110 continues to control all the mass storage devices 120, both its own and those normally assigned to the other file server 110, until this file server 110 determines that it should give back control of some mass storage devices 120.
In a preferred embodiment, the first file server 110 makes its determination responsive to operator control. An operator for this file server 110 determines that the other file server 110 has recovered from its service interruption. The GIVEBACK-OPERATION transition 221 is taken to enter the NORMAL state 210.
In alternative embodiments, the first file server 110 may make its determination responsive to messages 124 it receives from the second file server 110. If the second file server 110 sends messages 124 indicating that it has recovered from a service interruption (that is, it is in the REBOOTING state 240), the first file server 110 may initiate the GIVEBACK-OPERATION transition 221.
To perform the GIVEBACK-OPERATION transition 221, this file server 110 performs the following actions at a step 222:
o This file server 110 releases its disk reservation commands to the mass storage devices 120 normally assigned to the other file server 110.
o This file server I 10 sends the message 124 state indicator NORMAL to the other file server 110, including using the mailbox disks 122, the SAN 130, and the PN
140.
o This file server 110 disables the TAKEOVER-OPERATION transition 212 by the other file server 110 until the other file server 110 enters the NORMAL state 210.
This file server 110 remains at the step 222 until the other file server 110 enters the NORMAL state 210.
When the giveback operation is successful, the GIVEBACK-OPERATION
transition 221 completes and this file server enters the NORMAL state 210.
STOPPED State In the STOPPED state 230, this file server 110 has control of none of the t o mass storage devices 120 and is not operational.
In this state, this file server 110 performs no operations, until this file server 1 10 determines that it reboot.
In a preferred embodiment, the first file server 110 makes its determination responsive to operator control. An operator for this file server 110 determines that it has recovered from its service interruption. The REBOOT-OPERATION transition 231 is taken to enter the REBOOTING state 240.
In alternative embodiments, the first file server 110 may make its determination responsive to a timer or other automatic attempt to reboot. When this file server 110 determines that it has recovered from its service interruption, it attempts to reboot, and the REBOOT-OPERATION transition 231 is taken to enter the REBOOTING state 240.
REBOOTING State In the REBOOTING state 240, this file server 110 has control of none of the mass storage devices 120 and is recovering from a service interruption.
In this state, the file server 110 attempts to recover from a service interruption.
If this file server 110 is unable to recover from the service interruption, the REBOOT-FAILED transition 241 is taken and this file server 110 remains in the REBOOTING state 240.
s If this file server 110 is able to recover from the service interruption, but the other file server 110 is in the TAKEOVER state 220, the REBOOT-FAILED
transition 241 is taken and this file server 110 remains in the REBOOTING
state 240. In this case, the other file server 110 controls the mass storage devices 120 normally assigned to this file server 110, and this file server 110 waits for the GIVEBACK-io OPERATION transition 221 before re-attempting to recover from the service interruption.
If this file server 110 is able to recover from the service interruption, and determines it should enter the NORMAL state 210 (as described below), the REBOOT-15 NORMAL transition 242 is taken and this file server 110 enters the NORMAL
state 210.
If this file server 110 is able to recover from the service interruption, and determines it should enter the TAKEOVER state 210 (as described below), the REBOOT- TAKEOVER transition 243 is taken and this file server 110 enters the zo TAKEOVER state 210.
In a preferred embodiment, this file server 110 performs the attempt to recover from the service interruption with the following steps.
25 At a step 251, this file server 110 initiates its recovery operation.
At a step 252, this file server 110 determines whether it is able to write to any of the mass storage devices 120 (that is, if the other file server 110 is in the TAKEOVER state 220). If so, this file server 110 displays a prompt to an operator so 30 indicating and requesting the operator to command the other file server 110 to perform the GIVEBACK-OPERATION transition 221.
This file server 110 waits until the operator commands the other file server 110 to perform a giveback operation, waits until the GIVEBACK-OPERATION
transition 221 is complete, and proceeds with the next step.
s At a step 253, this file server 110 determines the state of the other file server 110. This file server 110 makes this determination in response to its own persistent memory 113 and the mailbox disks 122. This file server 110 notes the state it was in before entering the REBOOTING state 240 (that is, either the NORMAL
state 210 or the TAKEOVER state 220).
to If this file server 110 determines that the other file server 110 is in the NORMAL state 210, it proceeds with the step 254. If this file server 110 determines that it had previously taken over all the mass storage devices 120 (that is, that the other file server 110 is in the STOPPED state 230 or the REBOOTING state 240), it proceeds with 15 the step 255.
At a step 254, this file server 110 attempts to seize its own mass storage devices 120 but not those normally assigned to the other file server 110. This file server 110 proceeds with the step 256.
At a step 255, this file server 110 attempts to seize both its own mass storage devices 120 and those normally assigned to the other file server 110.
This file server 110 proceeds with the step 256.
At a step 256, this file server 110 determines whether its persistent memory 113 is current with regard to pending file server operations. If not, this file server 110 flushes its persistent memory 113 of pending file server operations.
At a step 257, this file server 110 determines if it is able to communicate with the other file server and if there is anything (such as an operator command) preventing takeover operations. This file server 110 makes its determination in response to the persistent memory 113 and the mailbox disks 122.
At a step 258, if this file server 110 was in the NORMAL state 210 before entering the REBOOTING state 240 (that is, this file server 110 performed the step 254 and seized only its own mass storage devices 120), it enters the NORMAL state 210.
s At a step 258, if this file server 110 was in the TAKEOVER state 220 before entering the REBOOTING state 240 (that is, this file server 110 performed the step 255 and seized all the mass storage devices 120, it enters the TAKEOVER
state 220.
Alternative Embodiments Although prefenred embodinients are disclosed herein, many variations are possible which remain within the concept, scope, and spirit of the invention, and these variations would become clear to those skilled in the art after perusal of this application.
Since the file server 110 receives the messages 124 using a plurality of pathways, it determines for each message 124 whether or not that message 124 is "new"
(the file server 110 has not seen it before), or "old" (the file server 110 has seen it before). The file server 110 maintains a record of the generation number Gi and the sequence number Si of the most recent new message 124. The file server 110 determines that the particular message 124 is new if aiid only if:
o its generation number Gi is greater than the most recent new message 124;
or o its generation number Gi is equal to the most recent new message 124 and its sequence number Si is greater than most recent new message 124.
If either of the file servers 110 determines that the message 124 is not new, that file server 110 can ignore that message 124.
In this state, each file server 110 periodically saves its own state information using the messages 124. Thus, each file server 110 records its state information both on its own mailbox disks and in its own persistent memory 113.
In this state, each file server 110 periodically watches for a state change in the other file server 110. The first file server I 10 detects a state change in the second file server 110 in one of at least two ways:
o The first file server I 10 notes that the second file server 110 has not updated its state information (using a message 124) for a timeout period.
In a preferred embodiment, this timeout period is two-half seconds for communication using the mailbox disks and one-half second for communication using the SAN 130. However, there is no particular requirement for using these timeout values; in alternative embodiments, different timeout values or techniques other than timeout periods may be used.
and o The first file server 110 notes that the second file server 110 has updated its state information (using one or more messages 124) to indicate that the second file server 110 has changed its state.
In a preferred embodiment, the second file server 110 indicates when it is in one of the states described with regard to each message 124.
If the first file server 110 determines that the second file server 110 is also in the NORMAL state, the NORMAL-OPERATION transition 211 is taken to remain in the state 210.
The first file server 110 makes its determination responsive to messages 124 it receives from the second file server 110. If there are no such messages 124 for a time period responsive to the timeout period described above (such as two to five times the timeout period), the first file server 110 decides that the second file server 110 has suffered a service interruption.
If the first file server 110 determines that the second file server 110 has suffered a service interruption (that is, the second file server 110 is in the STOPPED state 230), the TAKEOVER-OPERATION transition 212 is taken to enter the TAKEOVER
state 220.
The TAKEOVER-OPERATION transition 212 can be disabled by a message 124 state indicator such as DISAI3LE or NO-TAKEOVER.
In a preferred embodiment, either file server 110 can disable the TAKEOVER-OPERATION transition 212 responsive to (a) an operator command, (b) a synchronization error between the persistent memories 113, or (c) any compatibility mismatch between the file servers 110.
To perform the TAKEOVEI.t-OPERATION transition 212, this file server 110 performs the following actions at a step 213:
o This file server 110 sends the message 124 state indicator TAKEOVER to the other file server 110, using including the reliable communication path (including the mailbox disks 122, the SAN 130, and the PN 140).
o This file server 110 waits for the other file server 110 to have the opportunity to receive and act on the TAKEOVER-OPERATION transition 212 (that is, to suspend its own access to the mass storage devices 120.
o This file server 110 issues disk reservation commands to the mass storage devices 120 normally assigned to the other file server 110.
o This file server 110 takes any other appropriate action to assure that the other file server 110 is passive.
If the takeover operation is successful, the TAKEOVER-OPERATION
transition 212 completes and this file server enters the TAKEOVER state 220.
Otherwise (such as if takeover is disabled), this file server 110 returns to the NORMAL
state 210.
TAKEOVER State In the TAKEOVER state 220, this file server 110 is operating properly, but the other file server 110 is not. This file server 110 has taken over control of both its and the other's mass storage devices 120.
In this state, this file server 110 continues to write messages 124 to the persistent memory 113 and to the mailbox disks 122, so as to preserve its own state in the event of a service interruption.
In this state, this file server 110 continues to control all the mass storage devices 120, both its own and those normally assigned to the other file server 110, until this file server 110 determines that it should give back control of some mass storage devices 120.
In a preferred embodiment, the first file server 110 makes its determination responsive to operator control. An operator for this file server 110 determines that the other file server 110 has recovered from its service interruption. The GIVEBACK-OPERATION transition 221 is taken to enter the NORMAL state 210.
In alternative embodiments, the first file server 110 may make its determination responsive to messages 124 it receives from the second file server 110. If the second file server 110 sends messages 124 indicating that it has recovered from a service interruption (that is, it is in the REBOOTING state 240), the first file server 110 may initiate the GIVEBACK-OPERATION transition 221.
To perform the GIVEBACK-OPERATION transition 221, this file server 110 performs the following actions at a step 222:
o This file server 110 releases its disk reservation commands to the mass storage devices 120 normally assigned to the other file server 110.
o This file server I 10 sends the message 124 state indicator NORMAL to the other file server 110, including using the mailbox disks 122, the SAN 130, and the PN
140.
o This file server 110 disables the TAKEOVER-OPERATION transition 212 by the other file server 110 until the other file server 110 enters the NORMAL state 210.
This file server 110 remains at the step 222 until the other file server 110 enters the NORMAL state 210.
When the giveback operation is successful, the GIVEBACK-OPERATION
transition 221 completes and this file server enters the NORMAL state 210.
STOPPED State In the STOPPED state 230, this file server 110 has control of none of the t o mass storage devices 120 and is not operational.
In this state, this file server 110 performs no operations, until this file server 1 10 determines that it reboot.
In a preferred embodiment, the first file server 110 makes its determination responsive to operator control. An operator for this file server 110 determines that it has recovered from its service interruption. The REBOOT-OPERATION transition 231 is taken to enter the REBOOTING state 240.
In alternative embodiments, the first file server 110 may make its determination responsive to a timer or other automatic attempt to reboot. When this file server 110 determines that it has recovered from its service interruption, it attempts to reboot, and the REBOOT-OPERATION transition 231 is taken to enter the REBOOTING state 240.
REBOOTING State In the REBOOTING state 240, this file server 110 has control of none of the mass storage devices 120 and is recovering from a service interruption.
In this state, the file server 110 attempts to recover from a service interruption.
If this file server 110 is unable to recover from the service interruption, the REBOOT-FAILED transition 241 is taken and this file server 110 remains in the REBOOTING state 240.
s If this file server 110 is able to recover from the service interruption, but the other file server 110 is in the TAKEOVER state 220, the REBOOT-FAILED
transition 241 is taken and this file server 110 remains in the REBOOTING
state 240. In this case, the other file server 110 controls the mass storage devices 120 normally assigned to this file server 110, and this file server 110 waits for the GIVEBACK-io OPERATION transition 221 before re-attempting to recover from the service interruption.
If this file server 110 is able to recover from the service interruption, and determines it should enter the NORMAL state 210 (as described below), the REBOOT-15 NORMAL transition 242 is taken and this file server 110 enters the NORMAL
state 210.
If this file server 110 is able to recover from the service interruption, and determines it should enter the TAKEOVER state 210 (as described below), the REBOOT- TAKEOVER transition 243 is taken and this file server 110 enters the zo TAKEOVER state 210.
In a preferred embodiment, this file server 110 performs the attempt to recover from the service interruption with the following steps.
25 At a step 251, this file server 110 initiates its recovery operation.
At a step 252, this file server 110 determines whether it is able to write to any of the mass storage devices 120 (that is, if the other file server 110 is in the TAKEOVER state 220). If so, this file server 110 displays a prompt to an operator so 30 indicating and requesting the operator to command the other file server 110 to perform the GIVEBACK-OPERATION transition 221.
This file server 110 waits until the operator commands the other file server 110 to perform a giveback operation, waits until the GIVEBACK-OPERATION
transition 221 is complete, and proceeds with the next step.
s At a step 253, this file server 110 determines the state of the other file server 110. This file server 110 makes this determination in response to its own persistent memory 113 and the mailbox disks 122. This file server 110 notes the state it was in before entering the REBOOTING state 240 (that is, either the NORMAL
state 210 or the TAKEOVER state 220).
to If this file server 110 determines that the other file server 110 is in the NORMAL state 210, it proceeds with the step 254. If this file server 110 determines that it had previously taken over all the mass storage devices 120 (that is, that the other file server 110 is in the STOPPED state 230 or the REBOOTING state 240), it proceeds with 15 the step 255.
At a step 254, this file server 110 attempts to seize its own mass storage devices 120 but not those normally assigned to the other file server 110. This file server 110 proceeds with the step 256.
At a step 255, this file server 110 attempts to seize both its own mass storage devices 120 and those normally assigned to the other file server 110.
This file server 110 proceeds with the step 256.
At a step 256, this file server 110 determines whether its persistent memory 113 is current with regard to pending file server operations. If not, this file server 110 flushes its persistent memory 113 of pending file server operations.
At a step 257, this file server 110 determines if it is able to communicate with the other file server and if there is anything (such as an operator command) preventing takeover operations. This file server 110 makes its determination in response to the persistent memory 113 and the mailbox disks 122.
At a step 258, if this file server 110 was in the NORMAL state 210 before entering the REBOOTING state 240 (that is, this file server 110 performed the step 254 and seized only its own mass storage devices 120), it enters the NORMAL state 210.
s At a step 258, if this file server 110 was in the TAKEOVER state 220 before entering the REBOOTING state 240 (that is, this file server 110 performed the step 255 and seized all the mass storage devices 120, it enters the TAKEOVER
state 220.
Alternative Embodiments Although prefenred embodinients are disclosed herein, many variations are possible which remain within the concept, scope, and spirit of the invention, and these variations would become clear to those skilled in the art after perusal of this application.
Claims (59)
1. A file server including a set of storage devices capable of being shared with a second file server;
a controller disposed for coupling to said shared set of storage devices;
a transceiver disposed for coupling to a communication path and for communicating messages using said communication path, said communication path using said shared set of storage devices to communicate said messages;
and a takeover monitor coupled to at least part of said shared set of storage devices, and responsive to said communication path and said shared set of storage devices.
a controller disposed for coupling to said shared set of storage devices;
a transceiver disposed for coupling to a communication path and for communicating messages using said communication path, said communication path using said shared set of storage devices to communicate said messages;
and a takeover monitor coupled to at least part of said shared set of storage devices, and responsive to said communication path and said shared set of storage devices.
2. A file server as in claim 1, including persistent memory storing state information about said file server, said takeover monitor being responsive to said persistent memory.
3. Apparatus including a shared resource;
a pair of servers comprising a first server and a second server, each coupled to said shared resource and each disposed for managing at least part of said shared resource;
and a communication path disposed for coupling a sequence of messages between said pair, said communication path disposed for using said shared resource for coupling said sequence of messages;
each one of said pair being disposed for takeover of at least part of said shared resource in response to said communication path;
wherein said sequence of messages prevents both of said pair from concurrently performing said takeover.
a pair of servers comprising a first server and a second server, each coupled to said shared resource and each disposed for managing at least part of said shared resource;
and a communication path disposed for coupling a sequence of messages between said pair, said communication path disposed for using said shared resource for coupling said sequence of messages;
each one of said pair being disposed for takeover of at least part of said shared resource in response to said communication path;
wherein said sequence of messages prevents both of said pair from concurrently performing said takeover.
4. Apparatus as in claim 3, wherein at least one said server includes a file server;
said shared resource includes a storage medium;
and said communication path includes a designated location on said storage medium.
said shared resource includes a storage medium;
and said communication path includes a designated location on said storage medium.
5. Apparatus as in claim 3, wherein each one of said pair includes persistent memory;
said persistent memory being disposed for storing state information about said pair; and each one of said pair being disposed for takeover in response to said persistent memory.
said persistent memory being disposed for storing state information about said pair; and each one of said pair being disposed for takeover in response to said persistent memory.
6. Apparatus as in claim 3, wherein each said server is disposed for transmitting a message including recovery information relating to a status of said server on recovery from a service interruption; and each said server is disposed so that giveback of at least part of said shared resource is responsive to said recovery information.
7. Apparatus as in claim 3, wherein each said server is disposed for transmitting a message including recovery information relating to a status of said server on recovery from a service interruption; and each said server is disposed so that said takeover is responsive to said recovery information.
8. Apparatus as in claim 3, wherein said first server determines a state for itself and for said second server in response to said communication path; and said second server determines a state for itself and for said first server in response to said communication path;
wherein said first server and said second server concurrently each determine state for each other, such that it does not occur that each of said first server and said second server both consider the other to be inoperative.
wherein said first server and said second server concurrently each determine state for each other, such that it does not occur that each of said first server and said second server both consider the other to be inoperative.
9. Apparatus as in claim 3, wherein said shared resource includes a plurality of storage devices; and said communication path includes at least part of said storage devices.
10. Apparatus as in claim 3, wherein said communication path includes a plurality of independent communication paths between said pair; and each message in said sequence includes a generation number, said generation number being responsive to a service interruption and a persistent memory for a sender of said message.
11. Apparatus as in claim 3, wherein said communication path includes a plurality of independent communication paths between said pair; and said first server is disposed for determining a state for itself and for said second server in response to a state of said shared resource and in response to a state of a persistent memory at said first server.
12. Apparatus as in claim 3, wherein said communication path includes a plurality of independent communication paths between said pair; and said plurality of independent communication paths includes at least two of the group: a packet network, a shared storage element, a system area network.
13. Apparatus as in claim 3, wherein said communication path is disposed for transmitting at least one message from said first server to said second server;
said message indicating that said first server is attempting said takeover; receipt of said message being responsive to a state of said shared resource.
said message indicating that said first server is attempting said takeover; receipt of said message being responsive to a state of said shared resource.
14. Apparatus as in claim 13, wherein said second server is disposed for altering its state in response to said message, in said altered state refraining from writing to said shared resource.
15. A method for operating a file server, said method including steps for controlling a shared resource comprising a subset of a set of shared storage devices;
receiving and transmitting messages with a second file server, said steps for receiving and transmitting using a communication path including said shared storage devices;
monitoring said communicating path and said shared storage devices; storing state information about said file server in a persistent memory; and performing a takeover operation of said shared resource in response to said steps for monitoring and a state of said persistent memory.
receiving and transmitting messages with a second file server, said steps for receiving and transmitting using a communication path including said shared storage devices;
monitoring said communicating path and said shared storage devices; storing state information about said file server in a persistent memory; and performing a takeover operation of said shared resource in response to said steps for monitoring and a state of said persistent memory.
16. A method including steps for managing at a first server at least a part of a shared resource;
receiving and transmitting a sequence of messages between said first server to a second server, using said shared resource; and performing a takeover operation at a first server of at least part of said shared resource in response to said sequence of messages;
wherein said steps for receiving and transmitting prevent both of said first server and said second server from concurrently performing said takeover operation.
receiving and transmitting a sequence of messages between said first server to a second server, using said shared resource; and performing a takeover operation at a first server of at least part of said shared resource in response to said sequence of messages;
wherein said steps for receiving and transmitting prevent both of said first server and said second server from concurrently performing said takeover operation.
17. A method as in claim 16, including steps for determining, at said first server, a state for itself and for said second server in response to a communication path, and determining, at said second server, a state for itself and for said first server in response to said communication path, wherein said first server and said second server concurrently each determine state for each other, such that it does not occur that each of said first server and said second server both consider the other to be inoperative.
18. A method as in claim 16, including steps for storing state information about said first server in a persistent memory, wherein said first server determines a state for itself in response to a state of said persistent memory.
19. A method as in claim 16, including steps for transmitting, from said first server, recovery information relating to a status of said first server on recovery from a service interruption; and performing a giveback operation of at least part of said shared resource in response to said recovery information.
20. A method as in claim 16, including steps for transmitting, from said first server, recovery information relating to a status of said server on recovery from a service interruption;
wherein said steps for performing said takeover operation are responsive to said recovery information.
wherein said steps for performing said takeover operation are responsive to said recovery information.
21. A method as in claim 16, wherein said shared resource includes a plurality of storage devices; and a communication path includes at least part of said storage devices;
wherein loss of access to said part of said storage devices breaks said communication path.
wherein loss of access to said part of said storage devices breaks said communication path.
22. A method as in claim 16, including steps for transmitting at least one message from a first said server to a second said server, said message indicating that said first server is attempting said takeover;
altering a state of said second server in response to said message; and in said altered state refraining from writing to said shared resource.
altering a state of said second server in response to said message; and in said altered state refraining from writing to said shared resource.
23. A method as in claim 16, wherein a communication path includes a plurality of independent communication paths between said pair; and including steps for numbering said sequence of messages;
determining, at each recipient, a unified order for messages delivered using different ones of said plurality of independent communication paths; and determining, at said first server, a state for itself and for said second server in response to a state of said shared resource and in response to a state of a persistent memory at said first server.
determining, at each recipient, a unified order for messages delivered using different ones of said plurality of independent communication paths; and determining, at said first server, a state for itself and for said second server in response to a state of said shared resource and in response to a state of a persistent memory at said first server.
24. A method as in claim 16, wherein a communication path includes a plurality of independent communication paths between said pair; and including steps for numbering said sequence of messages;
determining, at each recipient, a unified order for messages delivered using different ones of said plurality of independent communication paths; and transmitting substantially each message in said sequence on at least two of said plurality of independent communication paths, wherein there is no single point of failure for communication between said pair.
determining, at each recipient, a unified order for messages delivered using different ones of said plurality of independent communication paths; and transmitting substantially each message in said sequence on at least two of said plurality of independent communication paths, wherein there is no single point of failure for communication between said pair.
25. A method as in claim 16, wherein a communication path includes a plurality of independent communication paths between said pair, and including steps for numbering said sequence of messages;
determining, at each recipient, a unified order for messages delivered using different ones of said plurality of independent communication paths;
wherein said plurality of independent communication paths includes at least two of the group: a packet network, a shared storage element, a system area network.
determining, at each recipient, a unified order for messages delivered using different ones of said plurality of independent communication paths;
wherein said plurality of independent communication paths includes at least two of the group: a packet network, a shared storage element, a system area network.
26. A method as in claim 16, wherein a communication path includes a plurality of independent communication paths between said pair; and including steps for numbering said sequence of messages;
determining, at each recipient, a unified order for messages delivered using different ones of said plurality of independent communication paths;
wherein said steps for numbering include (a) determining a generation number in response to a service interruption and a persistent memory for a sender of said message, and (b) providing said generation number in substantially each message in said sequence.
determining, at each recipient, a unified order for messages delivered using different ones of said plurality of independent communication paths;
wherein said steps for numbering include (a) determining a generation number in response to a service interruption and a persistent memory for a sender of said message, and (b) providing said generation number in substantially each message in said sequence.
27. A memory, including a set of instructions, wherein said set of instructions are executable by a processor to operate a first file server, said set of instructions comprising:
controlling a shared resource comprising a subset of a set of shared storage devices;
receiving and transmitting a sequence of messages with a second file server, said steps for receiving and transmitting using a communication path including said shared storage devices;
monitoring said communication path and said shared storage devices;
storing state information about said first file server in a persistent memory; and performing a takeover operation of said shared resource in response to said instructions for monitoring and a state of said persistent memory.
controlling a shared resource comprising a subset of a set of shared storage devices;
receiving and transmitting a sequence of messages with a second file server, said steps for receiving and transmitting using a communication path including said shared storage devices;
monitoring said communication path and said shared storage devices;
storing state information about said first file server in a persistent memory; and performing a takeover operation of said shared resource in response to said instructions for monitoring and a state of said persistent memory.
28. A memory, as in claim 27, including instructions for managing at a first server at least part of a shared resource;
receiving and transmitting said sequence of messages between said first server to a second server, using said shared resource; and performing a takeover operation at a first server of at least part of said shared resource in response to said sequence of messages;
wherein said instructions for receiving and transmitting prevent both of said first server and said second server from concurrently performing said takeover operation.
receiving and transmitting said sequence of messages between said first server to a second server, using said shared resource; and performing a takeover operation at a first server of at least part of said shared resource in response to said sequence of messages;
wherein said instructions for receiving and transmitting prevent both of said first server and said second server from concurrently performing said takeover operation.
29. A memory as in claim 27, including instructions for determining, at said first server, a state for itself and for said second server in response to said communication path;
determining, at said second server, a state for itself and for said first server in response to said communication path;
wherein said first server and said second server concurrently each determine state for each other, such that it does not occur that each of said first server and said second server both consider the other to be inoperative.
determining, at said second server, a state for itself and for said first server in response to said communication path;
wherein said first server and said second server concurrently each determine state for each other, such that it does not occur that each of said first server and said second server both consider the other to be inoperative.
30. A memory as in claim 27, also including an instruction for storing state information about said first server in a persistence memory, wherein said first server determines a state for itself in response to a state of said persistent memory.
31. A memory as in claim 27, including instructions for transmitting, from said first server, recovery information relating to a status of said first server on recovery from a service interruption; and performing a giveback operation of at least part of said shared resource is responsive to said recovery information.
32. A memory, as in claim 27, including instructions for transmitting, from said first server, recovery information relating to a status of said server on recovery from a service interruption;
wherein said instructions for performing said takeover operation are responsive to said recovery information.
wherein said instructions for performing said takeover operation are responsive to said recovery information.
33. A memory as in claim 27, wherein said shared resource includes a plurality of storage devices; and said communication path includes at least part of said storage devices;
whereby loss of access to said part of said storage devices breaks said communication path.
whereby loss of access to said part of said storage devices breaks said communication path.
34. A memory as in claim 27, including instructions for transmitting at least one message from a first said server to a second said server, said message indicating that said first server is attempting said takeover;
altering a state of said second server in response to said message; and in said altered state refraining from writing to said shared resource.
altering a state of said second server in response to said message; and in said altered state refraining from writing to said shared resource.
35. A memory as in claim 27, wherein said communication path includes a plurality of independent communication paths between said first file server and said second file server; and including instructions for numbering said sequence of messages;
determining, at each recipient, a unified order for messages delivered using different ones of said plurality of independent communication paths; and determining, at said first file server, a state for itself and for said second file server in response to a state of said shared resource and in response to a state of a persistent memory at said first file server.
determining, at each recipient, a unified order for messages delivered using different ones of said plurality of independent communication paths; and determining, at said first file server, a state for itself and for said second file server in response to a state of said shared resource and in response to a state of a persistent memory at said first file server.
36. A memory as in claim 27, wherein said communication path includes a plurality of independent communication paths between said first file server and said second file server; and including instructions for numbering said sequence of messages;
determining, at each recipient, a unified order for messages delivered using different ones of said plurality of independent communication paths;
transmitting substantially each message in said sequence on at least two of said plurality of independent communication paths, wherein there is no single point of failure for communication between said pair.
determining, at each recipient, a unified order for messages delivered using different ones of said plurality of independent communication paths;
transmitting substantially each message in said sequence on at least two of said plurality of independent communication paths, wherein there is no single point of failure for communication between said pair.
37. A memory as in claim 27, wherein said communication path includes a plurality of independent communication paths between said first file server and said second file server; and including instructions for numbering said sequence of messages;
determining, at each recipient, a unified order for messages delivered using different ones of said plurality of independent communication paths;
wherein said plurality of independent communication paths includes at least two of the group: a packet network, a shared storage element, a system area network.
determining, at each recipient, a unified order for messages delivered using different ones of said plurality of independent communication paths;
wherein said plurality of independent communication paths includes at least two of the group: a packet network, a shared storage element, a system area network.
38. A memory as in claim 27, wherein said communication path includes a plurality of independent communication paths between said first file server and said second file server; and including steps for numbering said sequence of messages; and determining, at each recipient, a unified order for messages delivered using different ones of said plurality of independent communication paths;
wherein said steps for numbering include (a) determining a generation number in response to a service interruption and a persistent memory for a sender of said message, and (b) providing said generation number in substantially each message in said sequence.
wherein said steps for numbering include (a) determining a generation number in response to a service interruption and a persistent memory for a sender of said message, and (b) providing said generation number in substantially each message in said sequence.
39. A file server, including:
an interface to a set of mass storage devices and to at least one network; and a processor and controller disposed to access said mass storage devices, to communicate messages with at least a second file server that has access to said mass storage devices, and to process state information about said server and said second file server;
wherein said messages are used to communicate said state information to and from said second file server, and wherein said messages are sent over plural different communication paths including at least part of said mass storage devices and said network.
an interface to a set of mass storage devices and to at least one network; and a processor and controller disposed to access said mass storage devices, to communicate messages with at least a second file server that has access to said mass storage devices, and to process state information about said server and said second file server;
wherein said messages are used to communicate said state information to and from said second file server, and wherein said messages are sent over plural different communication paths including at least part of said mass storage devices and said network.
40. A file server as in claim 39, wherein said part of said mass storage devices that are included in said communication paths further comprises one or more mailboxes stored on said mass storage devices.
41. A file server as in claim 39, wherein said plural different communication paths include at least one other network.
42. A file server as in claim 39, wherein one of the servers can take over control of the mass storage devices from the other server.
43. A file server as in claim 42, wherein take over occurs if messages from the other server timeout or if messages from the other server indicate that the other server has changed state.
44. A file server as in claim 43, wherein different timeouts are used for the different communication paths.
45. A file server as in claim 42, wherein said messages are used to prevent both servers from concurrently attempting to take over control of the mass storage devices.
46. A method of controlling a file server, comprising the steps of:
accessing a set of mass storage devices;
communicating messages with at least a second file server that has access to said mass storage devices; and processing state information about said server and said second file server;
wherein said messages are used to communicate said state information to and from said second file server, and wherein said messages are sent over plural different communication paths including at least part of said mass storage devices and a network.
accessing a set of mass storage devices;
communicating messages with at least a second file server that has access to said mass storage devices; and processing state information about said server and said second file server;
wherein said messages are used to communicate said state information to and from said second file server, and wherein said messages are sent over plural different communication paths including at least part of said mass storage devices and a network.
47. A method as in claim 46, wherein said part of said mass storage devices that are included in said communication paths further comprises one or more mailboxes stored on said mass storage devices.
48. A method as in claim 46, wherein said plural different communication paths include at least one other network.
49. A method as in claim 46, wherein one of the servers can take over control of the mass storage devices from the other server.
50. A method as in claim 49, wherein take over occurs if messages from the other server timeout or if messages from the other server indicate that the other server has changed state.
51. A method as in claim 50, wherein different timeouts are used for the different communication paths.
52. A method as in claim 49, wherein said messages are used to prevent both servers from concurrently attempting to take over control of the mass storage devices.
53. A memory storing information including instructions, the instructions executable by a processor to control a file server, the instructions comprising the steps of:
accessing a set of mass storage devices;
communicating messages with at least a second file server that has access to said mass storage devices; and processing state information about said server and said second file server;
wherein said messages are used to communicate said state information to and from said second file server, and wherein said messages are sent over plural different communication paths including at least part of said mass storage devices and a network.
accessing a set of mass storage devices;
communicating messages with at least a second file server that has access to said mass storage devices; and processing state information about said server and said second file server;
wherein said messages are used to communicate said state information to and from said second file server, and wherein said messages are sent over plural different communication paths including at least part of said mass storage devices and a network.
54. A memory as in claim 53, wherein said part of said mass storage devices that are included in said communication paths further comprises one or more mailboxes stored on said mass storage devices.
55. A memory as in claim 53, wherein said plural different communication paths include at least one other network.
56. A memory as in claim 53, wherein one of the servers can take over control of the mass storage devices from the other server.
57. A memory as in claim 56, wherein take over occurs if messages from the other server timeout or if messages from the other server indicate that the other server has changed state.
58. A memory as in claim 57, wherein different timeouts are used for the different communication paths.
59. A memory as in claim 56, wherein said messages are used to prevent both servers from concurrently attempting to take over control of the mass storage devices.
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/139,257 | 1998-08-25 | ||
US09/139,257 US6119244A (en) | 1998-08-25 | 1998-08-25 | Coordinating persistent status information with multiple file servers |
PCT/US1999/017137 WO2000011553A1 (en) | 1998-08-25 | 1999-07-28 | Coordinating persistent status information with multiple file servers |
Publications (2)
Publication Number | Publication Date |
---|---|
CA2356633A1 CA2356633A1 (en) | 2000-03-02 |
CA2356633C true CA2356633C (en) | 2009-11-17 |
Family
ID=22485802
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002356633A Expired - Fee Related CA2356633C (en) | 1998-08-25 | 1999-07-28 | Coordinating persistent status information with multiple file servers |
Country Status (7)
Country | Link |
---|---|
US (3) | US6119244A (en) |
EP (2) | EP1437658B1 (en) |
JP (1) | JP2002526821A (en) |
AT (1) | ATE270444T1 (en) |
CA (1) | CA2356633C (en) |
DE (1) | DE69918467T2 (en) |
WO (1) | WO2000011553A1 (en) |
Families Citing this family (144)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6604118B2 (en) | 1998-07-31 | 2003-08-05 | Network Appliance, Inc. | File system image transfer |
US6192408B1 (en) * | 1997-09-26 | 2001-02-20 | Emc Corporation | Network file server sharing local caches of file access information in data processors assigned to respective file systems |
US6545981B1 (en) | 1998-01-07 | 2003-04-08 | Compaq Computer Corporation | System and method for implementing error detection and recovery in a system area network |
US6493343B1 (en) * | 1998-01-07 | 2002-12-10 | Compaq Information Technologies Group | System and method for implementing multi-pathing data transfers in a system area network |
US6317844B1 (en) * | 1998-03-10 | 2001-11-13 | Network Appliance, Inc. | File server storage arrangement |
US6119244A (en) * | 1998-08-25 | 2000-09-12 | Network Appliance, Inc. | Coordinating persistent status information with multiple file servers |
US6523130B1 (en) * | 1999-03-11 | 2003-02-18 | Microsoft Corporation | Storage system having error detection and recovery |
US6961749B1 (en) * | 1999-08-25 | 2005-11-01 | Network Appliance, Inc. | Scalable file server with highly available pairs |
KR100644572B1 (en) * | 1999-10-02 | 2006-11-13 | 삼성전자주식회사 | Device operation detecting apparatus and method in directory serve |
EP1188294B1 (en) | 1999-10-14 | 2008-03-26 | Bluearc UK Limited | Apparatus and method for hardware implementation or acceleration of operating system functions |
US6983330B1 (en) * | 1999-12-29 | 2006-01-03 | Emc Corporation | Method and apparatus for using multiple paths for processing out of band commands |
GB0002972D0 (en) * | 2000-02-09 | 2000-03-29 | Orange Personal Comm Serv Ltd | Data handling system |
US6779128B1 (en) * | 2000-02-18 | 2004-08-17 | Invensys Systems, Inc. | Fault-tolerant data transfer |
US6874027B1 (en) * | 2000-04-07 | 2005-03-29 | Network Appliance, Inc. | Low-overhead threads in a high-concurrency system |
US6842823B1 (en) | 2000-04-14 | 2005-01-11 | Stratus Technologies Bermuda Ltd | Methods and apparatus for persistent volatile computer memory |
US6802022B1 (en) * | 2000-04-14 | 2004-10-05 | Stratus Technologies Bermuda Ltd. | Maintenance of consistent, redundant mass storage images |
US6701449B1 (en) * | 2000-04-20 | 2004-03-02 | Ciprico, Inc. | Method and apparatus for monitoring and analyzing network appliance status information |
US6738768B1 (en) * | 2000-06-27 | 2004-05-18 | Johnson William J | System and method for efficient information capture |
US6980313B2 (en) * | 2000-07-11 | 2005-12-27 | Imran Sharif | Fax-compatible internet appliance |
US20030115167A1 (en) * | 2000-07-11 | 2003-06-19 | Imran Sharif | Web browser implemented in an Internet appliance |
US20020078445A1 (en) * | 2000-07-11 | 2002-06-20 | Imran Sharif | Internet appliance for interactive audio/video display using a remote control unit for user input |
US6728897B1 (en) | 2000-07-25 | 2004-04-27 | Network Appliance, Inc. | Negotiating takeover in high availability cluster |
US6671820B1 (en) * | 2000-08-10 | 2003-12-30 | Dell Products, L.P. | System and method for the prevention of corruption of networked storage devices during backup data recovery |
US6609213B1 (en) * | 2000-08-10 | 2003-08-19 | Dell Products, L.P. | Cluster-based system and method of recovery from server failures |
US6636879B1 (en) * | 2000-08-18 | 2003-10-21 | Network Appliance, Inc. | Space allocation in a write anywhere file system |
US6910154B1 (en) * | 2000-08-18 | 2005-06-21 | Network Appliance, Inc. | Persistent and reliable delivery of event messages |
US6728922B1 (en) | 2000-08-18 | 2004-04-27 | Network Appliance, Inc. | Dynamic data space |
US7072916B1 (en) | 2000-08-18 | 2006-07-04 | Network Appliance, Inc. | Instant snapshot |
US6751635B1 (en) | 2000-08-18 | 2004-06-15 | Network Appliance, Inc. | File deletion and truncation using a zombie file space |
US20020026385A1 (en) * | 2000-08-31 | 2002-02-28 | Mccloskey John M. | System and methods for generating an electronic purchase order for a part using a display of computer-aided design (CAD) drawing and related article and media |
US7296073B1 (en) | 2000-09-13 | 2007-11-13 | Network Appliance, Inc. | Mechanism to survive server failures when using the CIFS protocol |
US6760861B2 (en) * | 2000-09-29 | 2004-07-06 | Zeronines Technology, Inc. | System, method and apparatus for data processing and storage to provide continuous operations independent of device failure or disaster |
US6654912B1 (en) | 2000-10-04 | 2003-11-25 | Network Appliance, Inc. | Recovery of file system data in file servers mirrored file system volumes |
US20020104008A1 (en) * | 2000-11-30 | 2002-08-01 | Cochran Robert A. | Method and system for securing control-device-lun-mediated access to luns provided by a mass storage device |
US6754773B2 (en) | 2001-01-29 | 2004-06-22 | Snap Appliance, Inc. | Data engine with metadata processor |
US6990667B2 (en) | 2001-01-29 | 2006-01-24 | Adaptec, Inc. | Server-independent object positioning for load balancing drives and servers |
US7054927B2 (en) | 2001-01-29 | 2006-05-30 | Adaptec, Inc. | File system metadata describing server directory information |
US6862692B2 (en) * | 2001-01-29 | 2005-03-01 | Adaptec, Inc. | Dynamic redistribution of parity groups |
US6990547B2 (en) * | 2001-01-29 | 2006-01-24 | Adaptec, Inc. | Replacing file system processors by hot swapping |
US20020138559A1 (en) * | 2001-01-29 | 2002-09-26 | Ulrich Thomas R. | Dynamically distributed file system |
US7353380B2 (en) | 2001-02-12 | 2008-04-01 | Aventail, Llc, A Subsidiary Of Sonicwall, Inc. | Method and apparatus for providing secure streaming data transmission facilities using unreliable protocols |
US7383329B2 (en) | 2001-02-13 | 2008-06-03 | Aventail, Llc | Distributed cache for state transfer operations |
US7360075B2 (en) | 2001-02-12 | 2008-04-15 | Aventail Corporation, A Wholly Owned Subsidiary Of Sonicwall, Inc. | Method and apparatus for providing secure streaming data transmission facilities using unreliable protocols |
US6950961B2 (en) * | 2001-02-13 | 2005-09-27 | Hewlett-Packard Development Company, L.P. | Highly available, monotonic increasing sequence number generation |
US6715098B2 (en) * | 2001-02-23 | 2004-03-30 | Falconstor, Inc. | System and method for fibrechannel fail-over through port spoofing |
US20020133601A1 (en) * | 2001-03-16 | 2002-09-19 | Kennamer Walter J. | Failover of servers over which data is partitioned |
US6668264B1 (en) * | 2001-04-03 | 2003-12-23 | Network Appliance, Inc. | Resynchronization of a target volume with a source volume |
US7219122B1 (en) * | 2001-04-23 | 2007-05-15 | Massachusetts Institute Of Technology | Software service handoff mechanism with a performance reliability improvement mechanism (PRIM) for a collaborative client-server system |
TWI220821B (en) * | 2001-04-26 | 2004-09-01 | Accton Technology Corp | Zero-loss web service system and method |
US6895532B2 (en) * | 2001-05-03 | 2005-05-17 | Hewlett-Packard Development Company, L.P. | Wireless server diagnostic system and method |
US7739614B1 (en) | 2001-05-22 | 2010-06-15 | Netapp, Inc. | System and method for consolidated reporting of characteristics for a group of directories |
US8171414B2 (en) * | 2001-05-22 | 2012-05-01 | Netapp, Inc. | System and method for consolidated reporting of characteristics for a group of file systems |
US6954884B2 (en) * | 2001-06-01 | 2005-10-11 | Lucent Technologies Inc. | System and method for effecting recovery of a network |
US6842869B2 (en) * | 2001-06-08 | 2005-01-11 | International Business Machines Corporation | Method to maintain nonvolatile system information cached in a distributed control network |
US20030005080A1 (en) * | 2001-06-28 | 2003-01-02 | Watkins James S. | Systems and methods for accessing data |
US20030005350A1 (en) * | 2001-06-29 | 2003-01-02 | Maarten Koning | Failover management system |
US7249150B1 (en) | 2001-07-03 | 2007-07-24 | Network Appliance, Inc. | System and method for parallelized replay of an NVRAM log in a storage appliance |
US7194513B2 (en) * | 2001-07-08 | 2007-03-20 | Imran Sharif | System and method for using an internet appliance to send/receive digital content files as E-mail attachments |
US6757695B1 (en) * | 2001-08-09 | 2004-06-29 | Network Appliance, Inc. | System and method for mounting and unmounting storage volumes in a network storage environment |
US6851070B1 (en) | 2001-08-13 | 2005-02-01 | Network Appliance, Inc. | System and method for managing time-limited long-running operations in a data storage system |
US6965989B1 (en) | 2001-08-14 | 2005-11-15 | Network Appliance, Inc. | System and method for fast reboot of a file server |
US6920579B1 (en) | 2001-08-20 | 2005-07-19 | Network Appliance, Inc. | Operator initiated graceful takeover in a node cluster |
US7287063B2 (en) * | 2001-10-05 | 2007-10-23 | International Business Machines Corporation | Storage area network methods and apparatus using event notifications with data |
GB2381713A (en) * | 2001-11-01 | 2003-05-07 | 3Com Corp | Failover mechanism involving blocking of access of a malfunctioning server and continuing monitoring to enable unblocking of access if server recovers |
US6996741B1 (en) * | 2001-11-15 | 2006-02-07 | Xiotech Corporation | System and method for redundant communication between redundant controllers |
US6934880B2 (en) * | 2001-11-21 | 2005-08-23 | Exanet, Inc. | Functional fail-over apparatus and method of operation thereof |
US7730153B1 (en) * | 2001-12-04 | 2010-06-01 | Netapp, Inc. | Efficient use of NVRAM during takeover in a node cluster |
US6868509B2 (en) * | 2001-12-07 | 2005-03-15 | Invensys Systems, Inc. | Method and apparatus for network fault correction via adaptive fault router |
US7742504B2 (en) * | 2002-01-24 | 2010-06-22 | University Of Southern California | Continuous media system |
US6959310B2 (en) * | 2002-02-15 | 2005-10-25 | International Business Machines Corporation | Generating data set of the first file system by determining a set of changes between data stored in first snapshot of the first file system, and data stored in second snapshot of the first file system |
US6829617B2 (en) * | 2002-02-15 | 2004-12-07 | International Business Machines Corporation | Providing a snapshot of a subset of a file system |
US7039828B1 (en) | 2002-02-28 | 2006-05-02 | Network Appliance, Inc. | System and method for clustered failover without network support |
US6934878B2 (en) * | 2002-03-22 | 2005-08-23 | Intel Corporation | Failure detection and failure handling in cluster controller networks |
US7418500B1 (en) | 2002-03-25 | 2008-08-26 | Network Appliance, Inc. | Mechanism for controlled sharing of files in a clustered application environment |
JP2004013215A (en) * | 2002-06-03 | 2004-01-15 | Hitachi Ltd | Storage system, storage sub-system, and information processing system including them |
US6857001B2 (en) | 2002-06-07 | 2005-02-15 | Network Appliance, Inc. | Multiple concurrent active file systems |
US7024586B2 (en) | 2002-06-24 | 2006-04-04 | Network Appliance, Inc. | Using file system information in raid data reconstruction and migration |
US8117328B2 (en) * | 2002-06-25 | 2012-02-14 | Microsoft Corporation | System and method for automatically recovering from failed network connections in streaming media scenarios |
US20040019640A1 (en) * | 2002-07-25 | 2004-01-29 | Bartram Linda Ruth | System and method for distributing shared storage for collaboration across multiple devices |
JP4026456B2 (en) * | 2002-09-13 | 2007-12-26 | 日本電気株式会社 | Computer system and information collection method |
US7209551B1 (en) | 2002-09-19 | 2007-04-24 | Sbc Properties, L.P. | Provisioning unified messaging system services |
US7447739B1 (en) | 2002-09-19 | 2008-11-04 | At&T Intellectual Property I, L.P. | Data and voice messaging system |
US7171452B1 (en) | 2002-10-31 | 2007-01-30 | Network Appliance, Inc. | System and method for monitoring cluster partner boot status over a cluster interconnect |
US8041735B1 (en) | 2002-11-01 | 2011-10-18 | Bluearc Uk Limited | Distributed file system and method |
US7457822B1 (en) | 2002-11-01 | 2008-11-25 | Bluearc Uk Limited | Apparatus and method for hardware-based file system |
JP2004192179A (en) * | 2002-12-10 | 2004-07-08 | Fujitsu Ltd | Device for integrating nic having rdma function into system without protecting hard memory or providing exclusive monitor process |
US7231489B1 (en) | 2003-03-03 | 2007-06-12 | Network Appliance, Inc. | System and method for coordinating cluster state information |
US7739543B1 (en) | 2003-04-23 | 2010-06-15 | Netapp, Inc. | System and method for transport-level failover for loosely coupled iSCSI target devices |
US7260737B1 (en) | 2003-04-23 | 2007-08-21 | Network Appliance, Inc. | System and method for transport-level failover of FCP devices in a cluster |
US7716323B2 (en) * | 2003-07-18 | 2010-05-11 | Netapp, Inc. | System and method for reliable peer communication in a clustered storage system |
US7593996B2 (en) * | 2003-07-18 | 2009-09-22 | Netapp, Inc. | System and method for establishing a peer connection using reliable RDMA primitives |
US7373640B1 (en) | 2003-07-31 | 2008-05-13 | Network Appliance, Inc. | Technique for dynamically restricting thread concurrency without rewriting thread code |
US7277897B2 (en) * | 2003-08-01 | 2007-10-02 | Oracle International Corporation | Dynamic reassignment of data ownership |
US8234517B2 (en) * | 2003-08-01 | 2012-07-31 | Oracle International Corporation | Parallel recovery by non-failed nodes |
US7467191B1 (en) | 2003-09-26 | 2008-12-16 | Network Appliance, Inc. | System and method for failover using virtual ports in clustered systems |
US7451167B2 (en) * | 2003-10-24 | 2008-11-11 | Network Appliance, Inc. | Verification of file system log data using per-entry checksums |
US7966294B1 (en) | 2004-01-08 | 2011-06-21 | Netapp, Inc. | User interface system for a clustered storage system |
US7340639B1 (en) | 2004-01-08 | 2008-03-04 | Network Appliance, Inc. | System and method for proxying data access commands in a clustered storage system |
US7966293B1 (en) | 2004-03-09 | 2011-06-21 | Netapp, Inc. | System and method for indexing a backup using persistent consistency point images |
US8621029B1 (en) | 2004-04-28 | 2013-12-31 | Netapp, Inc. | System and method for providing remote direct memory access over a transport medium that does not natively support remote direct memory access operations |
US7328144B1 (en) | 2004-04-28 | 2008-02-05 | Network Appliance, Inc. | System and method for simulating a software protocol stack using an emulated protocol over an emulated network |
US7478263B1 (en) | 2004-06-01 | 2009-01-13 | Network Appliance, Inc. | System and method for establishing bi-directional failover in a two node cluster |
US7496782B1 (en) | 2004-06-01 | 2009-02-24 | Network Appliance, Inc. | System and method for splitting a cluster for disaster recovery |
US7308600B2 (en) * | 2004-08-11 | 2007-12-11 | International Business Machines Corporation | Managing access to spare data storage devices |
US7624336B2 (en) * | 2004-11-08 | 2009-11-24 | International Business Machines Corporation | Selection of status data from synchronous redundant devices |
US8073899B2 (en) * | 2005-04-29 | 2011-12-06 | Netapp, Inc. | System and method for proxying data access commands in a storage system cluster |
JP4511455B2 (en) | 2005-12-20 | 2010-07-28 | 富士通株式会社 | Fiber channel switch and computer system using the same |
US8990613B2 (en) | 2006-06-29 | 2015-03-24 | Dssdr, Llc | Data transfer and recovery |
US9015520B2 (en) | 2006-06-29 | 2015-04-21 | Dssdr, Llc | Data transfer and recovery |
US7487383B2 (en) * | 2006-06-29 | 2009-02-03 | Dssdr, Llc | Data transfer and recovery process |
US9189303B2 (en) * | 2006-08-10 | 2015-11-17 | International Business Machines Corporation | Shadow queues for recovery of messages |
US7979701B1 (en) | 2006-09-15 | 2011-07-12 | Netapp, Inc. | Cross mapping graphical interface to show encryption relationships between hosts and storage devices |
US7613947B1 (en) | 2006-11-30 | 2009-11-03 | Netapp, Inc. | System and method for storage takeover |
US7711683B1 (en) | 2006-11-30 | 2010-05-04 | Netapp, Inc. | Method and system for maintaining disk location via homeness |
US8868495B2 (en) * | 2007-02-21 | 2014-10-21 | Netapp, Inc. | System and method for indexing user data on storage systems |
US7734947B1 (en) | 2007-04-17 | 2010-06-08 | Netapp, Inc. | System and method for virtual interface failover within a cluster |
US7886182B1 (en) * | 2007-04-19 | 2011-02-08 | Network Appliances, Inc. | Enhanced coordinated cluster recovery |
US7958385B1 (en) | 2007-04-30 | 2011-06-07 | Netapp, Inc. | System and method for verification and enforcement of virtual interface failover within a cluster |
US7783931B2 (en) * | 2007-05-04 | 2010-08-24 | International Business Machines Corporation | Alternate communication path between ESSNI server and CEC |
US8392529B2 (en) | 2007-08-27 | 2013-03-05 | Pme Ip Australia Pty Ltd | Fast file server methods and systems |
US8140483B2 (en) | 2007-09-28 | 2012-03-20 | International Business Machines Corporation | Transaction log management |
US9904969B1 (en) | 2007-11-23 | 2018-02-27 | PME IP Pty Ltd | Multi-user multi-GPU render server apparatus and methods |
WO2009067680A1 (en) | 2007-11-23 | 2009-05-28 | Mercury Computer Systems, Inc. | Automatic image segmentation methods and apparartus |
US8319781B2 (en) | 2007-11-23 | 2012-11-27 | Pme Ip Australia Pty Ltd | Multi-user multi-GPU render server apparatus and methods |
US9019287B2 (en) | 2007-11-23 | 2015-04-28 | Pme Ip Australia Pty Ltd | Client-server visualization system with hybrid data processing |
US10311541B2 (en) | 2007-11-23 | 2019-06-04 | PME IP Pty Ltd | Multi-user multi-GPU render server apparatus and methods |
US8417809B1 (en) | 2007-12-25 | 2013-04-09 | Netapp, Inc. | Event supression method and system |
US7478264B1 (en) * | 2008-03-10 | 2009-01-13 | International Business Machines Corporation | Storage management server communication via storage device servers |
US8688798B1 (en) | 2009-04-03 | 2014-04-01 | Netapp, Inc. | System and method for a shared write address protocol over a remote direct memory access connection |
US8510334B2 (en) | 2009-11-05 | 2013-08-13 | Oracle International Corporation | Lock manager on disk |
US8782464B2 (en) | 2011-03-31 | 2014-07-15 | International Business Machines Corporation | Method and system for using a standby server to improve redundancy in a dual-node data storage system |
GB2499822B (en) | 2012-02-29 | 2020-01-08 | Metaswitch Networks Ltd | Failover processing |
US10070839B2 (en) | 2013-03-15 | 2018-09-11 | PME IP Pty Ltd | Apparatus and system for rule based visualization of digital breast tomosynthesis and other volumetric images |
US11183292B2 (en) | 2013-03-15 | 2021-11-23 | PME IP Pty Ltd | Method and system for rule-based anonymized display and data export |
US11244495B2 (en) | 2013-03-15 | 2022-02-08 | PME IP Pty Ltd | Method and system for rule based display of sets of images using image content derived parameters |
US8976190B1 (en) | 2013-03-15 | 2015-03-10 | Pme Ip Australia Pty Ltd | Method and system for rule based display of sets of images |
US10540803B2 (en) | 2013-03-15 | 2020-01-21 | PME IP Pty Ltd | Method and system for rule-based display of sets of images |
US9509802B1 (en) | 2013-03-15 | 2016-11-29 | PME IP Pty Ltd | Method and system FPOR transferring data to improve responsiveness when sending large data sets |
KR101720376B1 (en) * | 2013-12-19 | 2017-03-27 | 엘에스산전 주식회사 | Method for data synchronizing of Energy Management System |
US9348715B2 (en) * | 2014-03-20 | 2016-05-24 | Netapp Inc. | Storage device health status synchronization |
US11599672B2 (en) | 2015-07-31 | 2023-03-07 | PME IP Pty Ltd | Method and apparatus for anonymized display and data export |
US9984478B2 (en) | 2015-07-28 | 2018-05-29 | PME IP Pty Ltd | Apparatus and method for visualizing digital breast tomosynthesis and other volumetric images |
US9836368B2 (en) * | 2015-10-22 | 2017-12-05 | Netapp, Inc. | Implementing automatic switchover |
US10909679B2 (en) | 2017-09-24 | 2021-02-02 | PME IP Pty Ltd | Method and system for rule based display of sets of images using image content derived parameters |
Family Cites Families (103)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4351023A (en) * | 1980-04-11 | 1982-09-21 | The Foxboro Company | Process control system with improved system security features |
US4456957A (en) | 1981-09-28 | 1984-06-26 | Ncr Corporation | Apparatus using a decision table for routing data among terminals and a host system |
US4710868A (en) | 1984-06-29 | 1987-12-01 | International Business Machines Corporation | Interconnect scheme for shared memory local networks |
US4814971A (en) | 1985-09-11 | 1989-03-21 | Texas Instruments Incorporated | Virtual memory recovery system using persistent roots for selective garbage collection and sibling page timestamping for defining checkpoint state |
US4719569A (en) | 1985-10-11 | 1988-01-12 | Sun Microsystems, Inc. | Arbitrator for allocating access to data processing resources |
US4825354A (en) * | 1985-11-12 | 1989-04-25 | American Telephone And Telegraph Company, At&T Bell Laboratories | Method of file access in a distributed processing computer network |
CA1299757C (en) * | 1987-08-28 | 1992-04-28 | Brent Cameron Beardsley | Device initiated partial system quiescing |
DE3854026D1 (en) * | 1987-09-04 | 1995-07-27 | Digital Equipment Corp | Fault-tolerant computer system with error limitation. |
US5109515A (en) | 1987-09-28 | 1992-04-28 | At&T Bell Laboratories | User and application program transparent resource sharing multiple computer interface architecture with kernel process level transfer of user requested services |
NZ226733A (en) | 1987-12-21 | 1990-05-28 | Honeywell Bull | Coupling incompatible cpu to data processing system |
US5049873A (en) | 1988-01-29 | 1991-09-17 | Network Equipment Technologies, Inc. | Communications network state and topology monitor |
JP2625866B2 (en) * | 1988-04-26 | 1997-07-02 | 日本電気株式会社 | Electronic device housing cooling structure |
US4937763A (en) | 1988-09-06 | 1990-06-26 | E I International, Inc. | Method of system state analysis |
US5067099A (en) | 1988-11-03 | 1991-11-19 | Allied-Signal Inc. | Methods and apparatus for monitoring system performance |
US4984272A (en) * | 1988-11-30 | 1991-01-08 | At&T Bell Laboratories | Secure file handling in a computer operating system |
JPH02165241A (en) * | 1988-12-19 | 1990-06-26 | Toshiba Corp | File access system |
US5222217A (en) * | 1989-01-18 | 1993-06-22 | International Business Machines Corporation | System and method for implementing operating system message queues with recoverable shared virtual storage |
US5113442A (en) * | 1989-03-06 | 1992-05-12 | Lachman Associates, Inc. | Method and apparatus for providing access control in a secure operating system |
US5144659A (en) * | 1989-04-19 | 1992-09-01 | Richard P. Jones | Computer file protection system |
US5454099A (en) * | 1989-07-25 | 1995-09-26 | International Business Machines Corporation | CPU implemented method for backing up modified data sets in non-volatile store for recovery in the event of CPU failure |
US5261051A (en) * | 1989-08-14 | 1993-11-09 | Microsoft Corporation | Method and system for open file caching in a networked computer system |
US5163131A (en) | 1989-09-08 | 1992-11-10 | Auspex Systems, Inc. | Parallel i/o network file server architecture |
EP0444376B1 (en) * | 1990-02-27 | 1996-11-06 | International Business Machines Corporation | Mechanism for passing messages between several processors coupled through a shared intelligent memory |
US5166939A (en) | 1990-03-02 | 1992-11-24 | Micro Technology, Inc. | Data storage apparatus and method |
US5088081A (en) | 1990-03-28 | 1992-02-11 | Prime Computer, Inc. | Method and apparatus for improved disk access |
JPH04130950A (en) * | 1990-09-21 | 1992-05-01 | Toshiba Corp | Network system |
US5208813A (en) | 1990-10-23 | 1993-05-04 | Array Technology Corporation | On-line reconstruction of a failed redundant array system |
US5155835A (en) | 1990-11-19 | 1992-10-13 | Storage Technology Corporation | Multilevel, hierarchical, dynamically mapped data storage subsystem |
US5146588A (en) * | 1990-11-26 | 1992-09-08 | Storage Technology Corporation | Redundancy accumulator for disk drive array memory |
JP2603757B2 (en) | 1990-11-30 | 1997-04-23 | 富士通株式会社 | Method of controlling array disk device |
US5235601A (en) | 1990-12-21 | 1993-08-10 | Array Technology Corporation | On-line restoration of redundancy information in a redundant array system |
US5274799A (en) | 1991-01-04 | 1993-12-28 | Array Technology Corporation | Storage device array architecture with copyback cache |
DE4129809C2 (en) * | 1991-01-28 | 2000-08-17 | Bosch Gmbh Robert | Multi-computer system |
US5278838A (en) | 1991-06-18 | 1994-01-11 | Ibm Corp. | Recovery from errors in a redundant array of disk drives |
SE470031B (en) | 1991-06-20 | 1993-10-25 | Icl Systems Ab | System and method for monitoring and changing the operation of a computer system |
US5257391A (en) | 1991-08-16 | 1993-10-26 | Ncr Corporation | Disk controller having host interface and bus switches for selecting buffer and drive busses respectively based on configuration control signals |
US5321837A (en) | 1991-10-11 | 1994-06-14 | International Business Machines Corporation | Event handling mechanism having a process and an action association process |
US5379417A (en) | 1991-11-25 | 1995-01-03 | Tandem Computers Incorporated | System and method for ensuring write data integrity in a redundant array data storage system |
GB9126779D0 (en) * | 1991-12-17 | 1992-02-12 | Int Computers Ltd | Security mechanism for a computer system |
US5341381A (en) | 1992-01-21 | 1994-08-23 | Tandem Computers, Incorporated | Redundant array parity caching system |
US5305326A (en) | 1992-03-06 | 1994-04-19 | Data General Corporation | High availability disk arrays |
AU653670B2 (en) | 1992-03-10 | 1994-10-06 | Data General Corporation | Improvements for high availability disk arrays |
US5398253A (en) | 1992-03-11 | 1995-03-14 | Emc Corporation | Storage unit generation of redundancy information in a redundant storage array system |
US5469566A (en) | 1992-03-12 | 1995-11-21 | Emc Corporation | Flexible parity generation circuit for intermittently generating a parity for a plurality of data channels in a redundant array of storage units |
US5448718A (en) * | 1992-04-20 | 1995-09-05 | International Business Machines Corporation | Method and system for time zero backup session security |
US5708668A (en) | 1992-05-06 | 1998-01-13 | International Business Machines Corporation | Method and apparatus for operating an array of storage devices |
US5335235A (en) * | 1992-07-07 | 1994-08-02 | Digital Equipment Corporation | FIFO based parity generator |
US5504883A (en) * | 1993-02-01 | 1996-04-02 | Lsc, Inc. | Method and apparatus for insuring recovery of file control information for secondary storage systems |
US5522050A (en) * | 1993-05-28 | 1996-05-28 | International Business Machines Corporation | Bus-to-bus bridge for a multiple bus information handling system that optimizes data transfers between a system bus and a peripheral bus |
ATE409907T1 (en) * | 1993-06-03 | 2008-10-15 | Network Appliance Inc | METHOD AND DEVICE FOR DESCRIBING ANY AREAS OF A FILE SYSTEM |
US5963962A (en) | 1995-05-31 | 1999-10-05 | Network Appliance, Inc. | Write anywhere file-system layout |
US6604118B2 (en) | 1998-07-31 | 2003-08-05 | Network Appliance, Inc. | File system image transfer |
US7174352B2 (en) | 1993-06-03 | 2007-02-06 | Network Appliance, Inc. | File system image transfer |
US6138126A (en) | 1995-05-31 | 2000-10-24 | Network Appliance, Inc. | Method for allocating files in a file system integrated with a raid disk sub-system |
DE69431186T2 (en) | 1993-06-03 | 2003-05-08 | Network Appliance Inc | Method and file system for assigning file blocks to storage space in a RAID disk system |
WO1994029795A1 (en) | 1993-06-04 | 1994-12-22 | Network Appliance Corporation | A method for providing parity in a raid sub-system using a non-volatile memory |
JPH0779233A (en) | 1993-06-29 | 1995-03-20 | Synoptics Commun Inc | Apparatus for establishing topology, method and apparatus for communicating topology information |
US5572711A (en) * | 1993-09-28 | 1996-11-05 | Bull Hn Information Systems Inc. | Mechanism for linking together the files of emulated and host system for access by emulated system users |
US5497422A (en) | 1993-09-30 | 1996-03-05 | Apple Computer, Inc. | Message protection mechanism and graphical user interface therefor |
US5537567A (en) | 1994-03-14 | 1996-07-16 | International Business Machines Corporation | Parity block configuration in an array of storage devices |
US5566297A (en) | 1994-06-16 | 1996-10-15 | International Business Machines Corporation | Non-disruptive recovery from file server failure in a highly available file system for clustered computing environments |
DE69521101T2 (en) | 1994-10-31 | 2001-10-18 | Ibm | Shared virtual disks with application-transparent recovery |
EP0713183A3 (en) | 1994-11-18 | 1996-10-02 | Microsoft Corp | Network independent file shadowing |
US5689701A (en) * | 1994-12-14 | 1997-11-18 | International Business Machines Corporation | System and method for providing compatibility between distributed file system namespaces and operating system pathname syntax |
US5617568A (en) * | 1994-12-14 | 1997-04-01 | International Business Machines Corporation | System and method for supporting file attributes on a distributed file system without native support therefor |
US5604862A (en) | 1995-03-14 | 1997-02-18 | Network Integrity, Inc. | Continuously-snapshotted protection of computer files |
US5678006A (en) | 1995-04-27 | 1997-10-14 | Cisco Systems, Inc. | Network switch having network management agent functions distributed among multiple trunk and service modules |
US5696895A (en) * | 1995-05-19 | 1997-12-09 | Compaq Computer Corporation | Fault tolerant multiple network servers |
US5603051A (en) * | 1995-06-06 | 1997-02-11 | Hewlett-Packard Company | Input/output processor with a local memory providing shared resources for a plurality of input/output interfaces on an I/O bus |
US5675782A (en) * | 1995-06-06 | 1997-10-07 | Microsoft Corporation | Controlling access to objects on multiple operating systems |
US5761669A (en) * | 1995-06-06 | 1998-06-02 | Microsoft Corporation | Controlling access to objects on multiple operating systems |
US5729705A (en) * | 1995-07-24 | 1998-03-17 | Symbios Logic Inc. | Method and apparatus for enhancing throughput of disk array data transfers in a controller |
US5720029A (en) * | 1995-07-25 | 1998-02-17 | International Business Machines Corporation | Asynchronously shadowing record updates in a remote copy session using track arrays |
US5668958A (en) * | 1995-09-12 | 1997-09-16 | International Business Machines Corporation | Heterogeneous filing system with common API and reconciled file management rules |
US5841997A (en) | 1995-09-29 | 1998-11-24 | Emc Corporation | Apparatus for effecting port switching of fibre channel loops |
US5862312A (en) | 1995-10-24 | 1999-01-19 | Seachange Technology, Inc. | Loosely coupled mass storage computer cluster |
US5737523A (en) * | 1996-03-04 | 1998-04-07 | Sun Microsystems, Inc. | Methods and apparatus for providing dynamic network file system client authentication |
US5819310A (en) | 1996-05-24 | 1998-10-06 | Emc Corporation | Method and apparatus for reading data from mirrored logical volumes on physical disk drives |
US5825877A (en) * | 1996-06-11 | 1998-10-20 | International Business Machines Corporation | Support for portable trusted software |
US6098155A (en) | 1996-10-28 | 2000-08-01 | Sun Microsystems, Inc. | Apparatus and method for streamlining data transfer with existing interconnect bandwidth |
US6161165A (en) * | 1996-11-14 | 2000-12-12 | Emc Corporation | High performance data path with XOR on the fly |
US5915087A (en) * | 1996-12-12 | 1999-06-22 | Secure Computing Corporation | Transparent security proxy for unreliable message exchange protocols |
WO1998035306A1 (en) | 1997-02-11 | 1998-08-13 | Connected Corporation | File comparison for data backup and file synchronization |
US5950225A (en) | 1997-02-28 | 1999-09-07 | Network Appliance, Inc. | Fly-by XOR for generating parity for data gleaned from a bus |
US5931935A (en) * | 1997-04-15 | 1999-08-03 | Microsoft Corporation | File system primitive allowing reprocessing of I/O requests by multiple drivers in a layered driver I/O system |
US6272648B1 (en) * | 1997-05-13 | 2001-08-07 | Micron Electronics, Inc. | System for communicating a software-generated pulse waveform between two servers in a network |
US6134673A (en) * | 1997-05-13 | 2000-10-17 | Micron Electronics, Inc. | Method for clustering software applications |
US5856981A (en) | 1997-05-15 | 1999-01-05 | Lucent Technologies Inc. | Reliable connection oriented networks |
US5876278A (en) * | 1997-05-29 | 1999-03-02 | Cheng; Henry | Cooling device |
US6275953B1 (en) | 1997-09-26 | 2001-08-14 | Emc Corporation | Recovery from failure of a data processor in a network server |
USH1860H (en) | 1997-09-26 | 2000-09-05 | Dsc/Celcore, Inc. | Fault testing in a telecommunications switching platform |
US5996086A (en) | 1997-10-14 | 1999-11-30 | Lsi Logic Corporation | Context-based failover architecture for redundant servers |
US5950203A (en) | 1997-12-31 | 1999-09-07 | Mercury Computer Systems, Inc. | Method and apparatus for high-speed access to and sharing of storage devices on a networked digital data processing system |
US6457130B2 (en) | 1998-03-03 | 2002-09-24 | Network Appliance, Inc. | File access control in a multi-protocol file server |
US6317844B1 (en) | 1998-03-10 | 2001-11-13 | Network Appliance, Inc. | File server storage arrangement |
US5890959A (en) * | 1998-03-31 | 1999-04-06 | Digital Equipment Corporation | High efficiency blower system with integral backflow preventor |
US6279011B1 (en) | 1998-06-19 | 2001-08-21 | Network Appliance, Inc. | Backup and restore for heterogeneous file server environment |
US6574591B1 (en) | 1998-07-31 | 2003-06-03 | Network Appliance, Inc. | File systems image transfer between dissimilar file systems |
US6119244A (en) | 1998-08-25 | 2000-09-12 | Network Appliance, Inc. | Coordinating persistent status information with multiple file servers |
US6199099B1 (en) | 1999-03-05 | 2001-03-06 | Ac Properties B.V. | System, method and article of manufacture for a mobile communication network utilizing a distributed communication network |
AU7470700A (en) | 1999-08-24 | 2001-03-19 | Network Appliance, Inc. | Scalable file server with highly available pairs |
US6715034B1 (en) | 1999-12-13 | 2004-03-30 | Network Appliance, Inc. | Switching file system request in a mass storage system |
US6654912B1 (en) | 2000-10-04 | 2003-11-25 | Network Appliance, Inc. | Recovery of file system data in file servers mirrored file system volumes |
-
1998
- 1998-08-25 US US09/139,257 patent/US6119244A/en not_active Expired - Lifetime
-
1999
- 1999-07-28 CA CA002356633A patent/CA2356633C/en not_active Expired - Fee Related
- 1999-07-28 DE DE69918467T patent/DE69918467T2/en not_active Expired - Lifetime
- 1999-07-28 AT AT99937596T patent/ATE270444T1/en not_active IP Right Cessation
- 1999-07-28 JP JP2000566746A patent/JP2002526821A/en active Pending
- 1999-07-28 EP EP04003916.6A patent/EP1437658B1/en not_active Expired - Lifetime
- 1999-07-28 WO PCT/US1999/017137 patent/WO2000011553A1/en active IP Right Grant
- 1999-07-28 EP EP99937596A patent/EP1153346B1/en not_active Expired - Lifetime
-
2000
- 2000-09-08 US US09/657,388 patent/US6496942B1/en not_active Expired - Lifetime
-
2002
- 2002-12-16 US US10/321,832 patent/US6829720B2/en not_active Expired - Fee Related
Also Published As
Publication number | Publication date |
---|---|
US6119244A (en) | 2000-09-12 |
US20030149812A1 (en) | 2003-08-07 |
DE69918467T2 (en) | 2005-07-28 |
EP1437658B1 (en) | 2013-05-29 |
JP2002526821A (en) | 2002-08-20 |
EP1153346A1 (en) | 2001-11-14 |
ATE270444T1 (en) | 2004-07-15 |
CA2356633A1 (en) | 2000-03-02 |
EP1153346B1 (en) | 2004-06-30 |
US6829720B2 (en) | 2004-12-07 |
EP1437658A2 (en) | 2004-07-14 |
US6496942B1 (en) | 2002-12-17 |
DE69918467D1 (en) | 2004-08-05 |
EP1437658A3 (en) | 2006-11-15 |
WO2000011553A1 (en) | 2000-03-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2356633C (en) | Coordinating persistent status information with multiple file servers | |
JP4500490B2 (en) | How to prevent "split brain" in computer clustering systems | |
EP1402363B1 (en) | Method for ensuring operation during node failures and network partitions in a clustered message passing server | |
US7114094B2 (en) | Information processing system for judging if backup at secondary site is necessary upon failover | |
US6804703B1 (en) | System and method for establishing persistent reserves to nonvolatile storage in a clustered computer environment | |
US6363462B1 (en) | Storage controller providing automatic retention and deletion of synchronous back-up data | |
EP1770508B1 (en) | Blade-based distributed computing system | |
US6134673A (en) | Method for clustering software applications | |
US6594775B1 (en) | Fault handling monitor transparently using multiple technologies for fault handling in a multiple hierarchal/peer domain file server with domain centered, cross domain cooperative fault handling mechanisms | |
US6910150B2 (en) | System and method for state preservation in a stretch cluster | |
US20050283641A1 (en) | Apparatus, system, and method for verified fencing of a rogue node within a cluster | |
US20070180309A1 (en) | System and method for mirroring data | |
US20070180307A1 (en) | Method & system for resynchronizing data between a primary and mirror data storage system | |
WO1991014230A1 (en) | Message communication processing system | |
JP2010128886A (en) | Failure node isolation processing program, failure node isolation method and storage system | |
JP2006500693A (en) | Dynamic RDF group | |
EP1214663B1 (en) | Scalable file server with highly available pairs | |
KR100411978B1 (en) | Fault tolerant system and duplication method thereof | |
US7228352B1 (en) | Data access management system in distributed processing system | |
US7003645B2 (en) | Use of a storage medium as a communications network for liveness determination in a high-availability cluster | |
EP1782202A2 (en) | Computing system redundancy and fault tolerance | |
US7302607B2 (en) | Two node virtual shared disk cluster recovery | |
KR20030048503A (en) | Communication system and method for data synchronization of duplexing server | |
JP2021086489A (en) | Loosely-coupled system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request | ||
MKLA | Lapsed |
Effective date: 20160728 |