Method and system for storing data using a continuous data protection system

• US 7,315,965 B2
• Filed: 02/04/2004
• Issued: 01/01/2008
• Est. Priority Date: 02/04/2004
• Status: Active Grant

• Current Assignee: NetApp, Inc.
• Original Assignee: Network Appliance Incorporated (NetApp, Inc.)
• Inventors: Chang, Yafen Peggy, Johnston, Craig Anthony, Trimmer, Donald Alvin, Stager, Roger Keith, Johnson, Randall, Saxena, Pawan, Blaser, Rico
• Primary Examiner(s): LE, DIEU MINH T
• Application Number:
  US10/771,613
• Publication Number:
  US 20050193272A1
• Time in Patent Office: 1,427 Days
• Field of Search: 714/42, 714/5, 714/2, 714/13, 714/52, 714/15, 714/11, 707/200, 707/204, 707/202
• US Class Current: 714/42
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery
• CPC Class Codes: G06F 11/2074 Asynchronous techniques

Abstract

A method and system wherein data is structured so that writes may be continuously duplicated and a protected volume may be restored to a particular point in time as desired. Writes are continuously duplicated on a secondary volume and organized into delta maps. The delta maps indicate which memory blocks were written to during a particular time frame.

Claims

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

duplicating a sequence of writes made to a primary volume to a secondary volume, the sequence of writes to the secondary volume being in a sequential order based on a time of a write to the primary volume;

mapping the writes between the primary volume and the secondary volume; and

organizing the mapping of the writes into mapping data structures wherein the structures enable the primary volume to be rewound to any point in time, thereby enabling changes to the primary volume to be tracked between any two points in time.

2. The method of claim 1 wherein a mapping data structure is used to selectively play back portions of the secondary volume.

3. The method of claim 1 further comprising the step of merging mapping data structures together to create a new volume that is identical to the primary volume at a previous point in time.

4. The method of claim 1 further comprising the step of merging mapping data structures that have the same expiration policy to enhance system performance.

5. The method of claim 1 further comprising the step of fading out data by merging the mapping data structures thereby freeing up blocks that are no longer used.

6. The method of claim 1, wherein the mapping data structures are delta maps.

7. The method of claim 1, wherein the sequential order on the secondary volume is sequential in time.

8. The method of claim 1, wherein the sequential order on the secondary volume is sequential with respect to a storage location on the secondary volume.

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

a host computer;

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

a secondary volume wherein the sequence of writes made to the primary volume are duplicated on the secondary volume, the sequence writes to the secondary volume being in a sequential order based on a time of a write to the primary volume; and

a continuous data protection system configured to manage the duplication of writes to the secondary volume and to map data between the primary volume and the secondary volume using a mapping data structure, wherein the mapping data structure is configured to track changes to said primary volume between any two points in time.

10. The system of claim 9 further comprising a volume manager for mirroring writes to the primary volume and the secondary volume.

11. The system of claim 10 wherein the volume manager is a software module running on an intelligent storage switch.

12. The system of claim 10 wherein the volume manager is a software module running on a server.

13. The system of claim 9, wherein the sequential order on said secondary volume is sequential in time.

14. The system of claim 9, wherein the sequential order on said secondary volume is sequential with respect to a storage location on said secondary volume.

15. The system of claim 9, wherein a mapping data structure is used to selectively play back portions of said secondary volume.

16. The system of claim 9, wherein said continuous data protection system is further configured to merge mapping data structures together to create a new volume that is identical to said primary volume at a previous point in time.

17. The system of claim 9, wherein said continuous data protection system is further configured to merge mapping data structures that have the same expiration policy to enhance system performance.

18. The system of claim 9, wherein said continuous data protection system is further configured to fade out data by merging the mapping data structures, thereby freeing up blocks that are no longer used.

19. The system of claim 9, wherein the mapping data structures are delta maps.

20. A method for continuously protecting data on a primary volume, comprising the steps of:

creating an initial snapshot of the primary volume, the initial snapshot located on a secondary volume;

duplicating a sequence of writes made to the primary volume to a write log on the secondary volume, the sequence of writes to the write log being in a sequential order based on a time of a write to the primary volume;

determining whether a snapshot has been triggered;

inserting a marker into the write log if a snapshot has been triggered; and

creating a mapping data structure from the write log, wherein the mapping data structure represents changes to the primary volume between two points in time, whereby the method continuously protects the primary volume from the time of the initial snapshot.

21. The method of claim 20, wherein the sequential order on the secondary volume is sequential in time.

22. The method of claim 20, wherein the sequential order on the secondary volume is sequential with respect to a storage location on the secondary volume.

23. The method of claim 20, wherein the creating step includes converting the write log to a block-ordered mapping data structure.

24. The method of claim 20, wherein the mapping data structure is used to play back portions of the write log.

25. The method of claim 20, further comprising the step of:

periodically merging mapping data structures from a time of a previous snapshot to the current time, whereby the merging step optimizes the mapping data structures.

26. The method of claim 25, wherein the merging step is performed according to a predetermined policy.

27. The method of claim 25, wherein the merging step is performed after a predetermined number of writes to the primary volume.

28. The method of claim 25, wherein the merging step is performed after a predetermined period of time.

29. The method according to claim 25, wherein the merging step includes merging mapping data structures having the same retention policy.

30. A computer-readable storage medium storing a set of instructions for execution by a general purpose computer to provide continuous data protection, the set of instructions comprising:

a duplicating code segment that duplicates a sequence of writes made to a primary volume to a secondary volume, the sequence of writes to the secondary volume being in a sequential order based on a time of a write to the primary volume;

a mapping code segment that maps the writes between the primary volume and the secondary volume; and

an organizing code segment that organizes the mapping of the writes into mapping data structures wherein the structures enable the primary volume to be rewound to any point in time, thereby providing continuous data protection to the primary volume.

31. A computer-readable storage medium storing a set of instructions for execution by a general purpose computer to provide continuous data protection, the set of instructions comprising:

a first creating code segment that creates an initial snapshot of a primary volume, the initial snapshot located on a secondary volume;

a duplicating code segment that duplicates a sequence of writes made to the primary volume to a write log on the secondary volume, the sequence of writes to the write log being in a sequential order based on a time of a write to the primary volume;

a determining code segment that determines whether a snapshot has been triggered;

an inserting code segment that inserts a marker into the write log if a snapshot has been triggered; and

a second creating code segment that creates a mapping data structure from the write log, wherein the mapping data structure represents changes to the primary volume between two points in time, whereby the primary volume is continuously protected from the time of the initial snapshot.