Patent US6609213B1 successfully refreshed from Google Patents.
← Back to Patent Explorer
US6609213B1 Expired / Lapsed US ⏱️ 0.0 years remaining

Cluster-based system and method of recovery from server failures

Assignee: Dell Products LP
•
Filing: 2000-08-10
•
Granted: 2003-08-19
•
Expires: 2020-08-10
📄 Original PDF 🌐 Google Patents 🔄 Sync Now

Abstract

Abstract A system and method for recovering from a server failure in a computer network, wherein the network contains several stand-alone, non-clustered, servers, and a cluster, wherein a clustered server also serves as the spare server, is disclosed. This cluster will have one standby recovery group for each non-clustered server in the computer network. Each recovery group contains the IP address and network name of the associated stand-alone server. The cluster monitors the health of the stand-alone servers, preferably through the use of a heartbeat mechanism. If the cluster detects a failure, it will reassign the LUNs owned by the failing server to the cluster. After the cluster has reassigned the LUNs, it will activate the recovery group containing the IP address and network name of the failing server. Subsequently, the cluster will assume the identity of the failing server and serve its users, until the failing server is repaired or replaced.

Inventors

  • 👤 Nam Nguyen
  • 👤 Michael Kosacek

Bibliographic Details

Application Number —
Jurisdiction US
Data Source google_patents
Last Synchronized 2026-11-03 01:52
CPC Classifications
G; G06; G06F; G06F11/00; G06F11/07; G06F11/16; G06F11/20; G06F11/202; G06F11/2023; G06F11/2025; G06F11/2028; G06F11/2033; G06F11/2038

Claims Analysis

Total Claims: 33
Claim 1
Independent Claim 221 words
A system for recovering from the failure of a server in a computer network comprising one or more non-clustered servers, wherein each server possesses a network address, and one or more devices, wherein the devices are communicatively coupled to the network and associated with a LUN address and wherein each LUN address is owned by a server, comprising: a heartbeat mechanism operable to transmit a heartbeat signal to a server and receive a response from the server, whereby a failing server may be detected if a response to the heartbeat signal is not received; LUN management software, wherein the LUN management software is operable to re-assign the LUN addresses owned by the failing server when the failing server is detected; a cluster group comprising at least one cluster server, wherein the cluster server is operable to receive ownership of the LUN addresses owned by the failing server; and wherein the cluster server is running cluster software operable for creating a recovery group that is associated with the network address associated with the failing server, and wherein the recovery group is operable to receive a user or computer network request that is directed to the associated network address of the failing server, such that the cluster server is operable to serve the user or run an application associated with the failing server.
Claim 2
Independent Claim 221 words
A system for recovering from the failure of a server in a computer network comprising one or more non-clustered servers, wherein each server possesses a network address, and one or more devices, wherein the devices are communicatively coupled to the network and associated with a LUN address and wherein each LUN address is owned by a server, comprising: a heartbeat mechanism operable to transmit a heartbeat signal to a server and receive a response from the server, whereby a failing server may be detected if a response to the heartbeat signal is not received; LUN management software, wherein the LUN management software is operable to re-assign the LUN addresses owned by the failing server when the failing server is detected; a cluster group comprising at least one cluster server, wherein the cluster server is operable to receive ownership of the LUN addresses owned by the failing server; and wherein the cluster server is running cluster software operable for creating a recovery group that is associated with the network address associated with the failing server, and wherein the recovery group is operable to receive a user or computer network request that is directed to the associated network address of the failing server, such that the cluster server is operable to serve the user or run an application associated with the failing server.
Claim 3
Dependent Claim 15 words
The system of claim 1 , wherein the computer network comprises a SAN storage network.
Claim 4
Dependent Claim 22 words
The system of claim 2 , wherein the non-clustered servers and the cluster group are communicatively coupled to the SAN storage network.
Claim 5
Dependent Claim 12 words
The system of claim 3 , wherein the devices comprise storage devices.
Claim 6
Dependent Claim 42 words
The system of claim 4 , wherein the non-clustered servers and the cluster group are running storage consolidation software, wherein the storage consolidation software is operable to manage the access to the storage devices by the non-clustered servers and the cluster group.
Claim 7
Dependent Claim 16 words
The system of claim 5 , wherein the storage consolidation software comprises the LUN management software.
Claim 8
Dependent Claim 18 words
The system of claim 5 , wherein the storage consolidation software is operable to run the heartbeat mechanism.
Claim 9
Dependent Claim 64 words
The system of claim 1 , wherein the cluster group comprises a plurality of clustered servers and wherein the clustered servers are communicatively coupled to the heartbeat mechanism and the LUN management software such that if a failing clustered server fails to respond to a heartbeat signal, another clustered server may assume the network address and LUN addresses associated with the failing clustered server.
Claim 10
Dependent Claim 23 words
The system of claim 1 , wherein the LUN management software is operable to mask the LUN addresses owned by the failing server.
Claim 11
Independent Claim 242 words
A method for recovering from the failure of a server in a computer network comprising one or more non-clustered servers, wherein each server possesses a network address, and one or more devices, wherein the devices are communicatively coupled to the network and associated with a LUN address and wherein each LUN address is owned by a server, comprising the steps of: providing LUN management software, wherein the LUN management software is operable to re-assign the LUN addresses owned by the failing server when the failing server is detected; providing a cluster group comprising at least one cluster server, wherein the cluster server is operable to receive ownership of the LUN addresses owned by the failing server; and wherein the cluster server is running cluster software operable for creating a recovery group that is associated with the network address associated with the failing server, and wherein the recovery group is operable to receive a user or computer network request that is directed to the associated network address of the failing server, such that the cluster server is operable to assume the identity of the failing server and serve the user or run an application associated with the failing server; monitoring the status of the non-clustered servers; detecting a failing non-clustered server; re-assigning the LUNs owned by the failing non-clustered server to the cluster server; activating the recovery group associated with the failing non-clustered server; and assuming the identity of the failing non-clustered server.
Claim 12
Independent Claim 242 words
A method for recovering from the failure of a server in a computer network comprising one or more non-clustered servers, wherein each server possesses a network address, and one or more devices, wherein the devices are communicatively coupled to the network and associated with a LUN address and wherein each LUN address is owned by a server, comprising the steps of: providing LUN management software, wherein the LUN management software is operable to re-assign the LUN addresses owned by the failing server when the failing server is detected; providing a cluster group comprising at least one cluster server, wherein the cluster server is operable to receive ownership of the LUN addresses owned by the failing server; and wherein the cluster server is running cluster software operable for creating a recovery group that is associated with the network address associated with the failing server, and wherein the recovery group is operable to receive a user or computer network request that is directed to the associated network address of the failing server, such that the cluster server is operable to assume the identity of the failing server and serve the user or run an application associated with the failing server; monitoring the status of the non-clustered servers; detecting a failing non-clustered server; re-assigning the LUNs owned by the failing non-clustered server to the cluster server; activating the recovery group associated with the failing non-clustered server; and assuming the identity of the failing non-clustered server.
Claim 13
Dependent Claim 48 words
The method of claim 10 , further comprising the step of providing a heartbeat mechanism operable to transmit a heartbeat signal to a server and receive a response from the server, whereby a failing server may be detected if a response to the heartbeat signal is not received.
Claim 14
Dependent Claim 115 words
The method of claim 11 , wherein the cluster group comprises a plurality of clustered servers and wherein the clustered servers are communicatively coupled to the heartbeat mechanism and the LUN management software such that if a failing clustered server fails to respond to a heartbeat signal, another clustered server may assume the network address and LUN addresses associated with the failing clustered server; and further comprising the steps of: monitoring the status of the clustered servers; detecting a failing clustered server; re-assigning the LUNs owned by the failing cluster server to another non-failing cluster server; activating the recovery group associated with the failing cluster server; and assuming the identity of the failing cluster server.
Claim 15
Dependent Claim 15 words
The method of claim 11 , wherein the computer network comprises a SAN storage network.
Claim 16
Dependent Claim 22 words
The method of claim 13 , wherein the non-clustered servers and the cluster group are communicatively coupled to the SAN storage network.
Claim 17
Dependent Claim 12 words
The method of claim 14 , wherein the devices comprise storage devices.
Claim 18
Dependent Claim 42 words
The method of claim 15 , wherein the non-clustered servers and the cluster group are running storage consolidation software, wherein the storage consolidation software is operable to manage the access to the storage devices by the non-clustered servers and the cluster group.
Claim 19
Dependent Claim 16 words
The method of claim 16 , wherein the storage consolidation software comprises the LUN management software.
Claim 20
Dependent Claim 18 words
The method of claim 16 , wherein the storage consolidation software is operable to run the heartbeat mechanism.
Claim 21
Dependent Claim 23 words
The method of claim 10 , wherein the LUN management software is operable to mask the LUN addresses owned by the failing server.
Claim 22
Dependent Claim 150 words
A computer network comprising: one or more devices communicatively coupled to the computer network, wherein the devices are each associated with a LUN address, wherein each LUN address is owned by a server coupled to the computer network; one or more non-clustered servers, wherein each non-clustered server possesses a network address; a cluster group comprising at least one clustered server, wherein the cluster server is operable to receive ownership of the LUN addresses owned by a failing server; and wherein the cluster server is running cluster software operable for creating a recovery group that is associated with the network address associated with the failing server, and wherein the recovery group is operable to receive a user or computer network request that is directed to the network address of the failing server, such that the cluster server is operable to serve the user or run an application with the failing server.
Claim 23
Dependent Claim 150 words
A computer network comprising: one or more devices communicatively coupled to the computer network, wherein the devices are each associated with a LUN address, wherein each LUN address is owned by a server coupled to the computer network; one or more non-clustered servers, wherein each non-clustered server possesses a network address; a cluster group comprising at least one clustered server, wherein the cluster server is operable to receive ownership of the LUN addresses owned by a failing server; and wherein the cluster server is running cluster software operable for creating a recovery group that is associated with the network address associated with the failing server, and wherein the recovery group is operable to receive a user or computer network request that is directed to the network address of the failing server, such that the cluster server is operable to serve the user or run an application with the failing server.
Claim 24
Dependent Claim 53 words
The computer network of claim 20 , further comprising a heartbeat mechanism operable to transmit a heartbeat signal to each server on the computer network and receive a response from the server, whereby the failing server may be detected by the cluster server if a response to the heartbeat signal is not received.
Claim 25
Dependent Claim 39 words
The computer network of claim 21 , further comprising LUN management software, wherein the LUN management software is operable to re-assign the LUN addresses owned by the failing server to the recovery group when the failing server is detected.
Claim 26
Dependent Claim 80 words
The computer network of claim 22 , wherein the cluster group comprises a plurality of clustered servers, wherein each clustered server is possesses a network address and may possess a LUN address, and wherein the clustered servers are communicatively coupled to the heartbeat mechanism and the LUN management software such that if a failing clustered server fails to respond to a heartbeat signal, another clustered server may assume the network address and LUN addresses associated with the failing clustered server.
Claim 27
Dependent Claim 24 words
The computer network of claim 22 , wherein the LUN management software is operable to mask the LUN address owned by the failing server.
Claim 28
Dependent Claim 17 words
The computer network of claim 20 , wherein the computer network further comprises a SAN storage network.
Claim 29
Dependent Claim 23 words
The computer network of claim 25 , wherein the non-clustered servers and the cluster group are communicatively coupled to the SAN storage network.
Claim 30
Dependent Claim 13 words
The computer network of claim 26 , wherein the devices comprise storage devices.
Claim 31
Dependent Claim 43 words
The computer network of claim 27 , wherein the non-clustered servers and the cluster group are running storage consolidation software, wherein the storage consolidation software is operable to manage the access to the storage devices by the non-clustered servers and the cluster group.
Claim 32
Dependent Claim 17 words
The computer network of claim 28 , wherein the storage consolidation software comprises the LUN management software.
Claim 33
Dependent Claim 19 words
The computer network of claim 28 , wherein the storage consolidation software is operable to run the heartbeat mechanism.

USPTO Annuity & Maintenance Windows

Annuity Stage Window Opens Payment Deadline Surcharge Period Until Estimated Fee Status
3.5 Years (Year 4) 2006-08-18 2007-02-17 2007-08-19 $2000.00 Window Closed / Lapsed
7.5 Years (Year 8) 2010-08-18 2011-02-17 2011-08-19 $3760.00 Window Closed / Lapsed
11.5 Years (Year 12) 2014-08-18 2015-02-17 2015-08-19 $7700.00 Window Closed / Lapsed

Assigned Categories & Tags

No categories assigned to this patent yet.

Assign Category Tag