Automatic site failover

• US 7,542,987 B2
• Filed: 04/21/2005
• Issued: 06/02/2009
• Est. Priority Date: 03/28/2002
• Status: Expired due to Term

• Current Assignee: Valtrus Innovations Limited (f/k/a Dolya Holdco 9 Limited) (Key Patent Innovations Limited)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Hess, Randy, Lubbers, Clark, Leveille, Jason, Korgaonkar, Anuja, Elkington, Susan, McCarty, James, Sicola, Stephen J.
• Primary Examiner(s): AL HASHEMI, SANA A
• Application Number:
  US11/111,380
• Publication Number:
  US 20050229021A1
• Time in Patent Office: 1,503 Days
• Field of Search: 707100-102, 707/103.R, 707 3- 5, 714/43, 714/6, 711/369, 711/365, 711/113
• US Class Current: 1/1
• CPC Class Codes: G06F 11/2058 using more than 2 mirrored copies
• CPC Class Codes: G06F 11/2064 while ensuring consistency
• CPC Class Codes: G06F 11/2069 Management of state, configuration or failover
• CPC Class Codes: G06F 11/2071 using a plurality of controllers
• CPC Class Codes: G06F 11/2079 Bidirectional techniques
• CPC Class Codes: G06F 11/2082 Data synchronisation
• CPC Class Codes: G06F 2201/855 Details of asynchronous mirroring using a journal to transfer not-yet-mirrored changes
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

A data storage system adapted to maintain redundant data storage sets at a destination location(s) is disclosed. The data storage system establishes a copy set comprising a source volume and a destination volume. Data written to a source volume is automatically copied to the destination volume. The data storage system maintains a data log that may be activated when the destination volume is inaccessible due to, for example, a malfunction in the destination storage system or in the communication link between the source system and the destination system. I/O commands and the data associated with those commands are written to the data log, and after a destination system becomes available the information in the data log is merged into the destination volume to conform the data in the destination volume to the data in the source volume. The data log competes for disk capacity with other volumes on the system, and log memory is allocated as needed. In operation, the array controllers monitor connection status between array controllers in a DRM group. When a connection failure is detected the controllers determine which of the remaining controllers determine whether the source controller remains online, and if not then which destination controller should assume the role of the source controller.

Claims

1. A storage controller, comprising:

an input port to receive input/output data operations from a host computer;

an output port for transmitting input/output data operations to at least one destination controller;

a processor;

a memory module communicatively connected to the processor and comprising logic instructions which, when executed, configure the processor to;

detect a failure in normal heartbeat operations between the storage controller and at least one destination controller; and

in response to the failure;

take the storage controller offline to the host computer when communication connections fail between the storage controller and a first predetermined number of destination controllers; and

log write input/output operations directed to the one or more destination controllers into a data log when communication connections remain active between the storage controller and a second predetermined number of destination controllers.

2. The storage controller of claim 1, wherein the memory module further comprises logic instructions for which, when executed by the processor, configure the processor to execute a background process to send heartbeats to and receive heartbeats from one or more destination controllers.

3. The storage controller of claim 1, wherein the data log comprises a storage set treated as a logical unit by the array controller.

4. The storage controller of claim 1, wherein the first predetermined number of destination controllers corresponds to a majority of destination controllers associated with the source controller.

5. The storage controller of claim 1, wherein the second predetermined number of destination controllers corresponds to a majority of destination controllers associated with the source controller.

6. A storage controller, comprising:

an input port to receive input/output data operations for a data replication management group from a host computer;

an output port for transmitting input/output data operations for a data replication management group to at least one destination controller;

a processor;

a memory module communicatively connected to the processor and comprising logic instructions which, when executed, configure the processor to;

detect a failure in normal heartbeat operations between the storage controller and one or more peer storage controllers;

determine whether the storage controller is a source controller for the data replication management group associated with the input/output data operations;

implement a first failover technique when the storage controller is a source controller for the data replication management group associated with the input/output data operations; and

implement a second failover technique when the storage controller is not a source controller for the data replication management group associated with the input/output data operations.

7. The storage controller of claim 6, wherein the first failover technique comprises taking the storage controller offline to the host computer when communication connections fail between the storage controller and a first predetermined number of peer controllers.

8. The storage controller of claim 6, wherein the first failover technique comprises logging input/output operations directed to the one or more peer storage controllers into a data log when communication connections remain active between the storage controller and a second predetermined number of peer storage controllers.

9. The storage controller of claim 6, wherein the second failover technique comprises:

determining whether data associated with the data replication management group in the storage controller is more current than corresponding data associated peer controllers by obtaining a group sequence number from one or more peer controllers and comparing the group sequence numbers; and

when the data associated with the storage controller is more current than the data associated other destination controllers in the data replication management group, then;

(a) installing the storage controller as a source controller for the data replication management group; and

(b) reconciling data between storage controllers in the data replication management group.