Systems and methods for event driven recovery management

• US 7,664,983 B2
• Filed: 08/30/2005
• Issued: 02/16/2010
• Est. Priority Date: 08/30/2004
• Status: Active Grant

• Current Assignee: Veritas Technologies, LLC (Whitehouse Group Ltd.)
• Original Assignee: Symantec Corporation (NortonLifeLock Inc.)
• Inventors: Woychowski, John P., Wadher, Pratik, Narasimhan, Balaji, Anderson, Curtis
• Primary Examiner(s): Maskulinski; Michael C
• Application Number:
  US11/215,958
• Publication Number:
  US 20060047997A1
• Time in Patent Office: 1,631 Days
• Field of Search: None
• US Class Current: 714/6.12
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery

Abstract

The present invention provides an exemplary system and method for event driven recovery management. One or more data blocks that are generated from a computing device are continually copied. At least one event marker is associated with the copies of the one or more data blocks. Access to the copies of the one or more data blocks according to the at least one event marker is allowed in order to provide event driven recovery.

Claims

1. A method for providing event driven recovery management comprising:

continually intercepting and copying one or more data blocks that are generated from a computing device;

associating at least one event marker with the copies of the one or more data blocks, wherein the at least one event marker is associated with an event that occurs independent of the copies of the one or more data blocks; and

allowing access to the copies of the one or more data blocks according to the at least one event marker in order to provide event driven recovery.

2. The method recited in claim 1, wherein the at least one event marker is generated by the computing device.

3. The method recited in claim 1, wherein the at least one event marker is generated by a source other than the computing device.

4. The method recited in claim 1, wherein the at least one event marker is associated with a timestamp associated with the copies of the one or more data blocks.

5. The method recited in claim 1, wherein the at least one event marker is associated with a timestamp distinct from a timestamp associated with the copies of the one or more data blocks.

6. The method recited in claim 1, wherein the at least one event marker is associated with a sequence number associated with the copies of the one or more data blocks.

7. The method recited in claim 1, wherein the at least one event marker is associated with a sequence number distinct from a sequence number associated with the copies of the one or more data blocks.

8. The method recited in claim 1, further comprising storing the copies of the one or more data blocks in a storage medium.

9. The method recited in claim 8, wherein the at least one event marker is associated with the copies of the one or more data blocks after the copies of the one or more data blocks are stored in the storage medium.

10. The method recited in claim 8, further comprising associating a timestamp that coincides with a clock associated with a recovery server that determines where the copies of the one or more data blocks are stored in the storage medium.

11. The method recited in claim 1, wherein the data blocks comprise data of various sizes.

12. A system for providing event driven recovery management comprising:

a data interceptor configured to continually intercept and copy one or more data blocks that are generated;

a first computing device configured to generate the one or more data blocks and to associate at least one event marker with the copies of the one or more data blocks, wherein the at least one event marker is associated with an event that occurs independent of the copies of the one or more data blocks; and

a second computing device configured to allow access to the copies of the one or more data blocks intercepted by the data interceptor according to the at least one event marker in order to provide event driven recovery.

13. The system recited in claim 12, wherein the at least one event marker is generated by the first computing device.

14. The system recited in claim 12, wherein the at least one event marker is generated by a source other than the first computing device.

15. The system recited in claim 12, wherein the at least one event marker is associated with a timestamp associated with the copies of the one or more data blocks.

16. The system recited in claim 12, wherein the at least one event marker is associated with a timestamp distinct from a timestamp associated with the copies of the one or more data blocks.

17. The system recited in claim 12, wherein the at least one event marker is associated with a sequence number associated with the copies of the one or more data blocks.

18. The system recited in claim 12, wherein the at least one event marker is associated with a sequence number distinct from a sequence number associated with the copies of the one or more data blocks.

19. The system recited in claim 12, further comprising a storage medium configured to store the copies of the one or more data blocks.

20. The system recited in claim 19, wherein the at least one event marker is associated with the copies of the one or more data blocks after the copies of the one or more data blocks copies are stored in the storage medium.

21. The system recited in claim 12, wherein the second computing device comprises a recovery server.

22. The system recited in claim 21, further comprising a clock associated with the recovery server for associating a timestamp with the at least one event marker.

23. The system recited in claim 21, wherein the first computing device and the second computing device comprise a single computing device.

24. The system recited in claim 12, wherein the data blocks comprise data of various sizes.

25. A computer program embodied on a computer readable medium having instructions for providing event driven recovery management comprising:

continually intercepting and copying one or more data blocks that are generated from a computing device;

associating at least one event marker with the copies of the one or more data blocks, wherein the at least one event marker is associated with an event that occurs independent of the copies of the one or more data blocks; and

allowing access to the copies of the one or more data blocks according to the at least one event marker in order to provide event driven recovery.

26. The computer program recited in claim 25, wherein the at least one event marker is generated by the computing device.

27. The computer program recited in claim 25, wherein the at least one event marker is generated by a source other than the computing device.

28. The computer program recited in claim 25, wherein the at least one event marker is associated with a timestamp associated with the copies of the one or more data blocks.

29. The computer program recited in claim 25, wherein the at least one event marker is associated with a timestamp distinct from a timestamp associated with the copies of the one or more data blocks.

30. The computer program recited in claim 25, wherein the at least one event marker is associated with a sequence number associated with the copies of the one or more data blocks.

31. The computer program recited in claim 25, wherein the at least one event marker is associated with a sequence number distinct from a sequence number associated with the copies of the one or more data blocks.

32. The computer program recited in claim 25, further comprising storing the copies of the one or more data blocks in a storage medium.

33. The computer program recited in claim 32, wherein the at least one event marker is associated with the copies of the one or more data blocks after the copies of the one or more data blocks are stored in the storage medium.

34. The computer program recited in claim 32, further comprising associating a timestamp that coincides with a clock associated with a recovery server that determines where the copies of the one or more data blocks are stored in the storage medium.

35. The computer program recited in claim 25, wherein the data blocks comprise data of various sizes.