Automated failover in a cluster of geographically dispersed server nodes using data replication over a long distance communication link

• US 20060047776A1
• Filed: 08/31/2004
• Published: 03/02/2006
• Est. Priority Date: 08/31/2004
• Status: Abandoned Application

• Current Assignee: Unisys Corporation
• Original Assignee: Unisys Corporation
• Inventors: Legg, Chris B., Moreno, Brenda Ann, Drohomereski, Carl Terence, Carlson, Dennis Arthur, Olshewski, Keith Louis, Chieng, Stephen Senh
• Application Number:
  US10/931,228
• Publication Number:
  US 20060047776A1
• Time in Patent Office: Days
• US Class Current: 709/217
• CPC Class Codes: G06F 11/203 using migration
• CPC Class Codes: G06F 11/2035 without idle spare hardware
• CPC Class Codes: G06F 11/2048 where the redundant components share neither address space nor persistent storage

Abstract

An embodiment of the invention is a method for performing an automated failover from a remote server node to a local server node, the remote server node and the local server node being in a cluster of geographically dispersed server nodes. The local server node is selected to be recipient of a failover from a remote server node by a cluster service software. The local server node is coupled to a local storage system and a local replication module external to the local storage system. The remote server node is coupled to a remote storage system and a remote replication module external to the remote storage system. The local and remote replication modules are in long distance communication with each other to perform data replication between the local and remote storage systems. A controlling cluster resource is brought online at the local server node, the controlling cluster resource being a base dependency of dependent cluster resources in a cluster group. The state of the controlling cluster resource is set to online pending to delay the dependent cluster resources in the cluster group from going online at the local server node. Configuration information of the controlling cluster resource is then verified.

Claims

1. A method comprising:

selecting a first server node to be recipient of a failover from a second server node using a cluster service software, the first and second server nodes being programmatically connected by the cluster service software, the first server node being coupled to a first storage system and a first replication module external to the first storage system, the second server node being coupled to a second storage system and a second replication module external to the second storage system, the first and second replication modules being in communication with each other via a long distance communication link to perform data replication between the first and second storage systems;

bringing a controlling cluster resource online at the first server node, the controlling cluster resource being a base dependency of dependent cluster resources in a cluster group;

setting the state of the controlling cluster resource to online pending;

verifying configuration information of the controlling cluster resource;

if the configuration information is correct,

determining the name of the first server node;

sending a first command from the controlling cluster resource to the first replication module to initiate failover of data; and

sending a second command from the controlling cluster resource to the local replication module to check for completion of failover of data.

2. The method of claim 1 further comprising, if the configuration information is correct:

if the failover of data is completed successfully,

setting the state of the controlling cluster resource to online state to allow the dependent cluster resources in the cluster group to go online at the first server node;

else,

setting the state of the controlling cluster resource to failed state to prevent the dependent cluster resources in the cluster group from going online at the first server node.

3. The method of claim 1 further comprising:

if the configuration information is not correct,

setting the state of the controlling cluster resource to failed state to prevent the dependent cluster resources in the cluster group from going online at the first server node.

4. The method of claim 1 wherein verifying configuration information of the controlling cluster resource comprises verifying IP addresses of first and second replication modules, identity of a consistency group, and lists of cluster nodes located at each of the first and second server nodes.

5. The method of claim 1 wherein the dependent cluster resources in the cluster group comprise application cluster resources and a physical storage disk cluster resource.

6. The method of claim 1 wherein the controlling cluster resource communicates with the first replication module via a secure shell protocol over a management network.

7. The method of claim 1 wherein the first replication module communicates with the first server node via a fibre channel switch.

8. The method of claim 1 wherein the first and second replication modules communicate with each other asynchronously.

9. A system comprising:

a first server node including a controlling cluster resource and dependent cluster resources in a cluster group, the controlling cluster resource being a base dependency of the dependent cluster resources in the cluster group;

a first storage system coupled to the first server node;

a first replication module coupled to the first server node, the first replication module being external to the first storage system;

a second server node including a copy of the controlling cluster resource and copies of the cluster resources in the cluster group;

a second storage system coupled to the second server node;

a second replication module coupled to the second server node, the second replication module being external to the second storage system;

wherein the first and second server nodes are programmatically connected by a cluster service software, and the first server node is selected by the cluster service software to be recipient of a failover from the second server node, the first and second replication modules are in communication with each other via a long distance communication link to perform data replication between the first and second storage systems, and wherein the controlling cluster resource controls the failover.

10. The system of claim 9 wherein the controlling cluster resource communicates with the first replication module via a management network to control the failover.

11. The system of claim 10 wherein the controlling cluster resource sends a first command to the first replication module to initiate failover of data.

12. The system of claim 11 wherein the controlling cluster resource sends a second command to the first replication module to check for completion of failover of data.

13. The system of claim 9 wherein the state of the controlling cluster resource is set to online pending state to keep the dependent cluster resources in the cluster group in pending state at the first server node.

14. The system of claim 9 wherein the state of the controlling cluster resource is set to online state to allow the dependent cluster resources in the cluster group to go online at the first server node.

15. The system of claim 9 wherein the state of the controlling cluster resource is set to failed state to prevent the dependent cluster resources in the cluster group from going online at the first server node.

16. The system of claim 9 wherein the dependent cluster resources in the cluster group comprise application cluster resources and a physical storage disk cluster resource.

17. An article of manufacture comprising:

a machine-accessible medium including data that, when accessed by a machine, cause the machine to perform operations comprising;

selecting a first server node to be recipient of a failover from a second server node, the first and second server nodes being programmatically connected by a cluster service software, the first server node being coupled to a first storage system and a first replication module external to the first storage system, the second server node being coupled to a second storage system and a second replication module external to the second storage system, the first and second replication modules being in communication with each other via a long distance communication link to perform data replication between the first and second storage systems;

bringing a controlling cluster resource online at the first server node, the controlling cluster resource being a base dependency of dependent cluster resources in a cluster group;

setting the state of the controlling cluster resource to online pending;

verifying configuration information of the controlling cluster resource;

if the configuration information is correct,

determining the name of the first server node;

sending a first command from the controlling cluster resource to the first replication module to initiate failover of data; and

sending a second command from the controlling cluster resource to the local replication module to check for completion of failover of data.

18. The article of manufacture of claim 17 wherein, if the configuration information is correct, the data further comprise data that, when accessed by the machine, cause the machine to perform operations comprising:

if the failover of data is completed successfully,

setting the state of the controlling cluster resource to online state to allow the dependent cluster resources in the cluster group to go online at the first server node;

else,

setting the state of the controlling cluster resource to failed state to prevent the dependent cluster resources in the cluster group from going online at the first server node.

19. The article of manufacture of claim 17 wherein, if the configuration information is not correct, the data further comprise data that, when accessed by the machine, cause the machine to perform operations comprising:

setting the state of the controlling cluster resource to failed state to prevent the dependent cluster resources in the cluster group from going online at the first server node.

20. The article of manufacture of claim 17 wherein the data causing the machine to perform the operation of verifying configuration information of the controlling cluster resource comprise data that, when accessed by the machine, cause the machine to perform operations comprising:

verifying IP addresses of first and second replication modules, identity of a consistency group, and lists of cluster nodes located at each of the first and second server nodes.