Adaptive quiesce for efficient cross-host consistent CDP checkpoints

• US 9,176,827 B2
• Filed: 12/30/2014
• Issued: 11/03/2015
• Est. Priority Date: 02/07/2012
• Status: Active Grant

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Zerto Ltd (Hewlett-Packard Enterprise Company)
• Inventors: Boldo, Amir, Mamluk, Ori, Burshan, Chen
• Primary Examiner(s): LEWIS, CHERYL RENEA
• Application Number:
  US14/585,576
• Publication Number:
  US 20150112937A1
• Time in Patent Office: 308 Days
• Field of Search: 707/610, 707/615, 707/649, 707/657, 707/674
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1448 Management of the data involved in backup or backup restore
• CPC Class Codes: G06F 11/1458 Management of the backup or restore process
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 2201/805 Real-time
• CPC Class Codes: G06F 2201/82 Solving problems relating to consistency
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

A disaster recovery system, including a target datastore for replicating data written to source datastores, and a checkpoint engine (i) for transmitting, at multiple times, quiesce commands to a plurality of host computers, each quiesce command including a timeout period that is adjusted at each of the multiple times, (ii) for determining, at each of the multiple times, whether acknowledgements indicating that a host has successfully stopped writing enterprise data to the source datastores, have been received from each of the host computers within the timeout period, (iii) for marking, at each of the multiple times, a cross-host checkpoint in the target datastore and reducing the timeout period for the quiesce commands at the next time, if the determining is affirmative, and (iv) for increasing, at each of the multiple times, the timeout period for the quiesce commands transmitted at the next time, if the determining is not affirmative.

Claims

1. A method for generating cross-host consistent checkpoints for disaster recovery systems, comprising:

transmitting a write quiesce command to each of a plurality of enterprise host computers, the write quiesce command including a timeout period, wherein each of the plurality of enterprise host computers are operative to write enterprise data to source datastores;

receiving a response from each of the plurality of enterprise host computers, wherein each response indicates whether or not a respective enterprise host computer has successfully stopped writing enterprise data to the source datastores within the timeout period;

determining a response time for each of the plurality of enterprise host computers; and

identifying a longest response time from the plurality of enterprise host computers.

2. The method of claim 1, comprising:

comparing the longest response time to the timeout period.

3. The method of claim 2, comprising:

increasing the timeout period responsive to comparing the longest response time to the timeout period.

4. The method of claim 2, comprising:

decreasing the timeout period responsive to comparing the longest response time to the timeout period.

5. The method of claim 2, wherein the timeout period is a first timeout period, comprising:

determining a second timeout period based on the response from each of the plurality of enterprise host computers.

6. The method of claim 1, comprising:

determining a response has not been received from at least one enterprise host computer within the timeout period.

7. The method of claim 1, comprising:

determining the response from each of the plurality of enterprise host computers has been received within the timeout period.

8. The method of claim 1, comprising:

marking a cross-host checkpoint in a target datastore for at least one of the plurality of enterprise host computer computers when the longest response time is less than the timeout period.

9. The method of claim 1, comprising:

logging the write quiesce command in at least one of a plurality of write journals of a target datastore;

promoting the logged write quiesce commands to replication disks of the target datastore at a plurality of times; and

marking checkpoints in each of the plurality of write journals of the target datastore.

10. The method of claim 9, comprising:

recovering the source datastores based on images of the replication disks, the plurality of write journals, and marked checkpoints.

11. A disaster recovery system for providing continuous data protection to an enterprise, the enterprise comprising a plurality of host computers operative to read enterprise data from source datastores and write enterprise data to source datastores, comprising:

a target datastore configured to replicate data written to the source datastores; and

a checkpoint engine configured to;

transmit a write quiesce command having a timeout period to each of a plurality of enterprise host computers, wherein each of the plurality of enterprise host computers are operative to write enterprise data to source datastores;

receive a response from at least one of the plurality of enterprise host computers, wherein each response indicates if a respective enterprise host computer has successfully stopped writing enterprise data to the source datastores within the timeout period;

determine a response time for each of the plurality of enterprise host computers; and

identify a longest response time from the plurality of enterprise host computers.

12. The system of claim 11, wherein the checkpoint engine compares the longest response time to the timeout period.

13. The system of claim 12, wherein the checkpoint engine increases the timeout period based on the comparison.

14. The system of claim 12, wherein the checkpoint engine decreases the timeout period based on the comparison.

15. The system of claim 12, wherein the timeout period is a first timeout period and the checkpoint engine determines a second timeout period based on the response from each of the plurality of enterprise host computers.

16. The system of claim 11, wherein the checkpoint engine determines responses have not been received from each of the plurality of enterprise host computers within the timeout period.

17. The system of claim 11, wherein the checkpoint engine determines the responses have been received from each of the plurality of enterprise host computers within the timeout period.

18. The system of claim 11, wherein the checkpoint engine marks a cross-host checkpoint in a target datastore for the enterprise host computer computers when the longest response time is less than the timeout period.

19. The system of claim 11 wherein the target datastore comprises:

a plurality of data disks for replication of the data in the source datastores; and

a plurality of write journals for logging the write quiesce commands issued by one or more of the plurality of enterprise host computers for writing enterprise data into the source datastores, and wherein the checkpoint engine marks a cross-host checkpoint by marking checkpoints in each of the plurality of write journals of the target datastore.

20. The system of claim 19, comprising:

a data recovery engine that recovers the source datastores based on images of the replication disks and based on the plurality of write journals and the checkpoints marked by the checkpoint engine.