Multisite replication with coordinated cycle switching

• US 8,732,124 B1
• Filed: 03/26/2012
• Issued: 05/20/2014
• Est. Priority Date: 03/26/2012
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Arnon, Dan, Meiri, David, Halstead, Mark, Yoder, Benjamin, Shorey, Oliver M. D.
• Primary Examiner(s): Beausoliel, Jr., Robert
• Assistant Examiner(s): Khakhar, Nirav K
• Application Number:
  US13/429,504
• Time in Patent Office: 785 Days
• Field of Search: 707/613
• US Class Current: 707/613
• CPC Class Codes: G06F 11/00 Error detection; Error correction; Monitoring error detection, correction or monitoring in information storage based on relative movement between record carrier and transducer G11B20/18; monitoring, i.e. supervising the progress of recording or reproducing G11B27/36; in static stores G11C29/00
• CPC Class Codes: G06F 11/2064 while ensuring consistency
• CPC Class Codes: G06F 11/2074 Asynchronous techniques
• CPC Class Codes: G06F 11/2076 Synchronous techniques
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation

Abstract

Handling asynchronous data provided by at least two sources includes synchronizing data between the at least two sources, coordinating cycle switching between the at least two sources, where an asynchronous cycle of data from one of the sources corresponds to an asynchronous cycle of data from an other one of the sources, receiving asynchronous data corresponding to a data cycle from at least one of the sources, and saving at least some of the received data. A first portion of data for a particular cycle may be transmitted from one of the sources and a second portion of data for the particular cycle, different from the first portion of data, may be transmitted from an other one of the sources and the first portion and the second portion together may correspond to all of the data for the particular cycle.

Claims

1. A method of handling asynchronous data provided by at least two sources, comprising:

synchronizing data between the at least two sources;

coordinating cycle switching between the at least two sources, wherein an asynchronous data cycle of asynchronous data from one of the sources corresponds to an asynchronous data cycle of asynchronous data from at least one other one of the sources;

receiving, at a destination, the asynchronous data corresponding to a particular asynchronous data cycle from at least one of the sources;

handling the asynchronous data received at the destination, wherein the handling includes at least one of;

(i) determining that different portions of the asynchronous data for the particular asynchronous data cycle have been received from each of the at least two sources, wherein the different portions together correspond to all of the asynchronous data for the particular asynchronous data cycle;

or

(ii) determining that at least a portion of the asynchronous data for the particular asynchronous data cycle received from the one of the sources is the same as at least a portion of the asynchronous data for the particular asynchronous data cycle received from the at least one other one of the sources; and

saving at least some of the asynchronous data received at the destination.

2. A method, according to claim 1, wherein a first portion of the data for the particular asynchronous data cycle is transmitted from one of the sources and a second portion of the asynchronous data for the particular asynchronous data cycle, different from the first portion of data, is transmitted from the at least one other one of the sources and wherein the first portion and the second portion together correspond to all of the asynchronous data for the particular asynchronous data cycle.

3. A method, according to claim 2, wherein a particular criteria is used to determine whether data is provided in the first portion of data.

4. A method, according to claim 3, wherein the particular criteria includes one of:

volume identifier and whether data was written locally to a particular one of the sources.

5. A method, according to claim 4, wherein the particular criteria includes the volume identifier and wherein data for volumes having an identifier meeting a specific criteria is provided for the first portion and data for volumes having an identifier that does not meet the specific criteria is provided for the second portion.

6. A method, according to claim 2, further comprising:

maintaining a bitmap at each of the sources indicating data in a portion for an other one of the sources.

7. A method, according to claim 6, wherein following failure of one of the sources, the other one of the sources uses the bitmap to transmit data that was set for transmission by one of the sources prior to failure thereof.

8. A method, according to claim 1, wherein all of the asynchronous data for the particular asynchronous data cycle is transmitted by one of the sources and all of the asynchronous data for the particular asynchronous data cycle is transmitted by the at least one other one of the sources, and wherein duplicate asynchronous data that is received is discarded.

9. A method, according to claim 1, further comprising:

suspending asynchronous transfer for a particular one of the sources following failure of the particular one of the sources.

10. A method, according to claim 9, further comprising:

reenabling asynchronous transfer for the particular one of the sources following resynchronization of the particular one of the sources with at least one other one of the sources.

11. Computer software, provided in a non-transitory computer-readable medium, that handles asynchronous data provided by at least two sources having synchronized data therebetween, the software comprising:

executable code that coordinates cycle switching between the at least two sources, wherein an asynchronous data cycle of asynchronous data from one of the sources corresponds to an asynchronous data cycle of asynchronous data from at least one other one of the sources, the asynchronous data being synchronized between the at least two sources;

executable code that receives, at a destination, the asynchronous data corresponding to a particular asynchronous data cycle from at least one of the sources;

executable code that handles the received asynchronous data at the destination, wherein the handling includes at least one of;

(i) determining that different portions of the asynchronous data for the particular asynchronous data cycle have been received from each of the at least two sources, wherein the different portions together correspond to all of the asynchronous data for the particular asynchronous data cycle;

or

(ii) determining that at least a portion of the asynchronous data for the particular asynchronous data cycle received from the one of the sources is the same as at least a portion of the asynchronous data for the particular asynchronous data cycle received from the at least one other one of the sources; and

executable code that saves at least some of the received asynchronous data received at the destination.

12. Computer software, according to claim 11, wherein a first portion of data for the particular asynchronous data cycle is transmitted from one of the sources and a second portion of data for the particular asynchronous data cycle, different from the first portion of data, is transmitted from the at least one other one of the sources and wherein the first portion and the second portion together correspond to all of the data for the particular asynchronous data cycle.

13. Computer software, according to claim 12, wherein a particular criteria is used to determine whether data is provided in the first portion of data.

14. Computer software, according to claim 13, wherein the particular criteria includes one of:

volume identifier and whether data was written locally to a particular one of the sources.

15. Computer software, according to claim 14, wherein the particular criteria includes the volume identifier and wherein data for volumes having an identifier meeting a specific criteria is provided for the first portion and data for volumes having an identifier that does not meet the specific criteria is provided for the second portion.

16. Computer software, according to claim 12, further comprising:

executable code that maintains a bitmap at each of the sources indicating data in a portion for an other one of the sources.

17. Computer software, according to claim 16, wherein following failure of one of the sources, the other one of the sources uses the bitmap to transmit data that was set for transmission by one of the sources prior to failure thereof.

18. Computer software, according to claim 11, wherein all of the data for the particular asynchronous data cycle is transmitted by one of the sources and all of the data for the particular asynchronous data cycle is transmitted by the least one other one of the sources, and wherein duplicate asynchronous data that is received is discarded.

19. Computer software, according to claim 11, further comprising:

executable code that suspends asynchronous transfer for a particular one of the sources following failure of the particular one of the sources.

20. Computer software, according to claim 19, further comprising:

executable code that reenables asynchronous transfer for the particular one of the sources following resynchronization of the particular one of the sources with at least one other one of the sources.