Method and system for maintaining data in a continuous data protection system

• US 7,406,488 B2
• Filed: 02/05/2004
• Issued: 07/29/2008
• Est. Priority Date: 02/04/2004
• Status: Active Grant

• Current Assignee: NetApp, Inc.
• Original Assignee: NetApp, Inc.
• Inventors: Chang, Yafen Peggy, Johnston, Craig Anthony, Trimmer, Donald Alvin, Stager, Roger Keith, Johnson, Randall, Saxena, Pawan, Blaser, Rico
• Primary Examiner(s): Chace; Christian
• Assistant Examiner(s): Syed; Farhan M
• Application Number:
  US10/772,643
• Publication Number:
  US 20050171979A1
• Time in Patent Office: 1,636 Days
• Field of Search: 707/200, 707/202, 709/213
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1466 to make the backup process non-disruptive
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery
• CPC Class Codes: G06F 11/2074 Asynchronous techniques
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• 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/99952 Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

A method and system where data is maintained in a continuous data protection system is disclosed. A primary volume may be protected according to an any-point-in-time (APIT) window wherein restores may be performed at any time as desired. The APIT window may be of any time duration as desired. Outside of the APIT window, a retention policy for phasing out data may be established as desired.

Claims

1. A method for providing continuous data protection, the method comprising the steps of:

writing data to a primary volume;

duplicating the writes made to the primary volume to a second volume in a sequential fashion, wherein the secondary volume contains a chronological ordering of all writes made to the primary volume; and

identifying any point in time (APTI) window wherein all writes to the secondary volume are maintained so that within the identified APIT window, the primary volume may be restored to any previous point within the APIT window;

creating a block-ordered mapping data structure to track changes in the data written to the secondary volume between two points in time; and

merging the mapping data structures that protect contiguous points in time, whereby fewer mapping data structures are needed to protect the data between the same two points in time spanning the merged mapping data structures.

2. The method of claim 1 further including the step of retaining particular points in time beyond the APIT window.

3. The method of claim 2 wherein a point-in-time map is created by creating a full mapping between the primary volume and the secondary volume for a point in time that is retained beyond the APIT window, the full mapping using a data structure.

4. The method of claim 3 wherein the full mapping is created by merging data structures ranging in time from an initial time to a time when a snapshot was taken.

5. The method of claim 3 wherein the full mapping is created by merging data structures ranging in time from a time a point-in-time map created prior to a snapshot was taken to a time when the snapshot was taken.

6. The method of claim 1 wherein data on the secondary volume that is outside of the identified APIT window is discarded.

7. The method of claim 1 wherein data on the secondary volume that is outside of the identified APIT window is phased out according to a retention policy.

8. The method of claim 3 further comprising the step of periodically creating point-in-time maps to reduce a number of data structures that are needed when performing a restore.

9. A method for operating a data protection system for a protected computer system, the method comprising the steps of:

tracking writes made to a primary volume;

duplicating the writes to the primary volume in a sequential fashion on a secondary volume, wherein the secondary volume contains a chronological ordering of all writes made to the primary volume;

organizing a mapping of the writes between the primary volume and the secondary volume into block-ordered data structures, wherein the data structures enable the primary volume to be restored at any point in time;

identifying any point in time window wherein the data structures are maintained so that within the identified time window, the primary volume may be restored at any point within the time window; and

merging the data structures that protect contiguous points in time, whereby fewer data structures are needed to protect the data between the same two points in time spanning the merged data structures.

10. The method of claim 9 wherein a snapshot is taken at a particular point in time within the identified time window and a full mapping of the primary volume and the secondary volume for the particular point time is created.

11. The method of claim 10 wherein the full mapping is created by merging data structures ranging in time from an initial time to a time when the snapshot was taken.

12. The method of claim 10 wherein the full mapping is created by merging data structures ranging in time from a time when a point-in-time map created prior to the snapshot was taken to the time the snapshot was taken.

13. A system for providing continuous data protection, the system comprising:

a host computer;

a primary volume for storing data written by the host computer;

a secondary volume wherein writes made to the primary volume are sequentially duplicated onto the secondary volume, the secondary volume containing a chronological ordering of all writes made to the primary volume; and

a data protection system configured to;

manage the duplication of writes to the secondary volume;

map data between the primary volume and the secondary volume using block-ordered data structures, wherein the data structures are maintained so that within an established time window, the primary volume may be restored to any point within the time window; and

merge the data structures that protect contiguous points in time, whereby fewer data structures are needed to protect the data between the same two points in time spanning the merged data structures.

14. The system of claim 13 wherein the data protection system is configured to create a point-in-time map for a point-in-time at which the primary volume needs to be restored.

15. The system of claim 14 wherein the point-in-time map is created by creating a full mapping between the primary volume and the secondary volume.

16. The system of claim 15 wherein the full mapping is created by merging data structures ranging in time from an initial time to a time when a snapshot was taken.

17. The system of claim 16 wherein the full mapping is created by merging data structures ranging in time from a time when a point-in-time map created prior to the snapshot was taken to the time the snapshot was taken.

18. A computer-readable storage medium containing a set of instructions for a general purpose computer, the set of instructions comprising:

a tracking code segment for tracking writes made to a primary volume;

a duplicating code segment for duplicating the writes to the primary volume in a sequential fashion on a secondary volume, wherein the secondary volume contains a chronological ordering of all writes made to the primary volume;

an organizing code segment for organizing a mapping of the writes between the primary volume and the secondary volume into block-ordered data structures, wherein the data structures enable the primary volume to be restored to any point in time;

an identifying code segment for identifying any point in time window wherein the data structures are maintained so that within the identified time window, the primary volume may be restored to any point within the time window; and

a merging code segment for merging the data structures that protect contiguous points in time, whereby fewer data structures are needed to protect the data between the same two points in time spanning the merged data structures.

19. A method for enabling data recovery from a primary volume in a contiguous data protection system, comprising the steps of:

creating an initial copy of the primary volume;

after the initial copy is made, duplicating each write to the primary volume to a write log to be stored on a secondary volume, the write log being written to the secondary volume when the write log is full, wherein the secondary volume contains a chronological ordering of all writes made to the primary volume;

creating a snapshot of the primary volume, the snapshot being a point in time to which the primary volume can be stored;

creating a block-ordered data structure to track the writes made to the secondary volume, the data structure being derived from the write log and containing the writes made to the primary volume between two points in time; and

merging the data structures that protect contiguous points in time, whereby fewer data structures are needed to protect the data between the same two points in time spanning the merged data structures.

20. The method according to claim 19, wherein creating the snapshot includes inserting a marker into the write log, the marker indicating a time at which the snapshot is taken.

21. The method according to claim 19, wherein the merging step includes

merging data structures from a time corresponding to a snapshot to a current time.

22. A method for providing continuous data protection, comprising the steps of:

writing data to a primary volume;

duplicating the writes made to the primary volume to a secondary volume in a sequential fashion, wherein the secondary volume contains a time-based ordering of all writes made to the primary volume;

identifying an any point in time (APIT) window wherein all writes to the secondary volume are maintained so that within the identified APIT window, the primary volume may be restored to any point within the APIT window;

mapping the writes between the primary volume and secondary volume using a data structure; and

merging data structures that protect contiguous points in time, whereby fewer data structures are needed to protect the data between the same two points in time spanning the merged data structures.

23. The method of claim 22, further comprising the step of retaining particular points in time beyond the APIT window.

24. The method of claim 23, wherein a point in time map is created by creating a full mapping between the primary volume and the secondary volume for a point in time that is retained beyond the APIT window, the full mapping using a data structure.

25. The method of claim 24, wherein the full mapping is created by merging data structures ranging in time from an initial time to a time when a snapshot was taken.

26. The method of claim 24, wherein the full mapping is created by merging data structures ranging in time from a time a point in time map created prior to a snapshot was taken to a time when the snapshot was taken.

27. The method of claim 24, further comprising the step of periodically creating point in time maps to reduce a number of data structures that are needed when performing a restore.

28. The method of claim 22, wherein data on the secondary volume that is outside of the identified APIT window is discarded.

29. The method of claim 22, wherein data on the secondary volume that is outside of the identified APIT window is phased out according to a retention policy.

30. A currently implemented method for continuously protecting data stored on a volume of a storage system, comprising:

writing data to a primary volume in a block-based order;

duplicating the data to a write log in a sequential order;

creating a block-ordered mapping data structure from the write log, the block-ordered mapping data structure stored on a secondary volume and used to track changed in the data between two points in time, whereby the data is continuously protected; and

merging the mapping data structures that protect contiguous points in time, whereby fewer mapping data structure are needed to protect the data between the same two points in time spanning the merged mapping data structures.

31. The method according to claim 30, wherein the two points in time can be any points in time during which the data is protected.

32. The method according to claim 30, further comprising:

creating an initial full copy snapshot of the primary volume such that changes to the data are relative to the data in the initial full copy snapshot.

33. The method according to claim 30, further comprising:

creating a snapshot of the primary volume at a point in time by inserting a marker into the write log to identify the point in time.