Adaptive quiesce for efficient cross-host consistent CDP checkpoints

• US 8,868,513 B1
• Filed: 06/17/2014
• Issued: 10/21/2014
• 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/306,883
• Publication Number:
  US 20140298092A1
• Time in Patent Office: 126 Days
• Field of Search: 707/610, 707/615, 707/649, 707/657, 707/674
• US Class Current: 707/674
• 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 use in disaster recovery systems, comprising:

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

determining whether acknowledgements have been received from each of the plurality of enterprise host computers within the timeout period, the acknowledgments indicating that an enterprise host computer of the plurality of enterprise host computers has successfully stopped writing enterprise data to the source datastores;

adjusting the timeout period for the write quiesce command;

transmitting at a second time, the write quiesce command with the adjusted timeout period; and

generating a target datastore, by a continuous data protection disaster recovery system to replicate the enterprise data in the source datastores.

2. The method of claim 1 further comprising dynamically determining a value of the timeout period for the second time, based on the timeout period for the first time and based on a production constraint.

3. The method of claim 2 wherein the production constraint limits the percentage of total time allocated for quiesce timeouts.

4. The method of claim 2 wherein the production constraint limits the number of quiesce timeouts that occur in a designated time period.

5. The method of claim 1 further comprising logging the write quiesce command to write enterprise data to the source datastores, issued by one or more of the plurality of enterprise host computers in at least one of a plurality of write journals of the target datastore, and promoting the logged write quiesce command 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.

6. The method of claim 5 further comprising recovering the source datastores based on images of the replication disks and on the plurality of write journals and the marked checkpoints.

7. The method of claim 1 further comprising determining the acknowledgements have not been received from each of the plurality of enterprise host computers within the timeout period.

8. The method of claim 7 further comprising increasing the timeout period for the write quiesce command transmitted at the second time.

9. The method of claim 1 further comprising determining the acknowledgements have been received from each of the plurality of enterprise host computers within the timeout period.

10. The method of claim 9 further comprising:

marking a cross-host checkpoint in a target datastore for the enterprise host computer computers, responsive to the determination; and

decreasing the timeout period for the write quiesce command transmitted at the second time.

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

a target datastore for replicating data written to the source datastores; and

a checkpoint engine (i) transmitting, at a first time, a write quiesce command to a plurality of enterprise host computers, each write quiesce command including a timeout period that is adjusted, (ii) for determining whether acknowledgements have been received from each of the plurality of enterprise host computers within the timeout period, the acknowledgements indicating that an enterprise host computer of the plurality of enterprise host computers has successfully stopped writing enterprise data to the source datastores, (iii) for adjusting the timeout period for the write quiesce command; and

(iv) for transmitting at a second time, the write quiesce command with the adjusted timeout period.

12. The system of claim 11 wherein the checkpoint engine dynamically determines a value of the timeout period for the second time, based on the timeout period for the first time and based on a production constraint.

13. The system of claim 11 wherein the production constraint limits the percentage of total time allocated for quiesce timeouts.

14. The system of claim 11 wherein the production constraint limits the number of quiesce timeouts that occur in a designated time period.

15. 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 command 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 plurality of write journals of the target datastore.

16. The system of claim 15 further comprising a data recovery engine for recovering 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.

17. The system of claim 15, further comprising the checkpoint engine determining the acknowledgements have not been received from each of the plurality of enterprise host computers within the timeout period.

18. The system of claim 15 further comprising the checkpoint engine increasing the timeout period for the write quiesce command transmitted at the second time.

19. The system of claim 15 further comprising the checkpoint engine determining the acknowledgements have been received from each of the plurality of enterprise host computers within the timeout period.

20. The system of claim 19 further comprising the checkpoint engine:

marking a cross-host checkpoint in a target datastore for the enterprise host computer computers, responsive to the determination; and

decreasing the timeout period for the write quiesce command transmitted at the second time.