IP Library Granted Patent US 7,631,217
Granted Patent B2
US 7,631,217 · App. 11/215,958 · Granted Dec 8, 2009

Systems and methods for event driven recovery management

Assignee: Symantec Corporation
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,631,217
App. No.
11/215,958
Filed
Aug 30, 2005
Granted
Dec 8, 2009
Kind
B2
Art Unit
2113
USPC
714/6
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 (44)

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.

Assignments (16)
AMENDMENT NO. 1 TO PATENT SECURITY AGREEMENT Recorded Apr 8, 2025
From: VERITAS TECHNOLOGIES LLC; COHESITY, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 070779/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 26, 2025
From: VERITAS TECHNOLOGIES LLC
To: COHESITY, INC.
Reel/Frame 070335/0013 →
RELEASE OF SECURITY INTEREST Recorded Dec 16, 2024
From: ACQUIOM AGENCY SERVICES LLC, AS COLLATERAL AGENT
To: VERITAS TECHNOLOGIES LLC (F/K/A VERITAS US IP HOLDINGS LLC)
Reel/Frame 069712/0090 →
RELEASE OF SECURITY INTEREST Recorded Dec 13, 2024
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: VERITAS TECHNOLOGIES LLC
Reel/Frame 069634/0584 →
SECURITY INTEREST Recorded Dec 9, 2024
From: VERITAS TECHNOLOGIES LLC; COHESITY, INC.
To: JPMORGAN CHASE BANK. N.A.
Reel/Frame 069890/0001 →
ASSIGNMENT OF SECURITY INTEREST IN PATENT COLLATERAL Recorded Nov 25, 2024
From: BANK OF AMERICA, N.A., AS ASSIGNOR
To: ACQUIOM AGENCY SERVICES LLC, AS ASSIGNEE
Reel/Frame 069440/0084 →
TERMINATION AND RELEASE OF SECURITY IN PATENTS AT R/F 037891/0726 Recorded Nov 30, 2020
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
To: VERITAS US IP HOLDINGS, LLC
Reel/Frame 054535/0814 →
SECURITY INTEREST Recorded Aug 20, 2020
From: VERITAS TECHNOLOGIES LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
Reel/Frame 054370/0134 →
MERGER AND CHANGE OF NAME Recorded Apr 18, 2016
From: VERITAS US IP HOLDINGS LLC; VERITAS TECHNOLOGIES LLC
To: VERITAS TECHNOLOGIES LLC
Reel/Frame 038455/0752 →
SECURITY INTEREST Recorded Feb 23, 2016
From: VERITAS US IP HOLDINGS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 037891/0726 →
SECURITY INTEREST Recorded Feb 23, 2016
From: VERITAS US IP HOLDINGS LLC
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 037891/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 4, 2016
From: SYMANTEC CORPORATION
To: VERITAS US IP HOLDINGS LLC
Reel/Frame 037697/0412 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 17, 2008
From: MENDOCINO SOFTWARE, INC.
To: SYMANTEC CORPORATION
Reel/Frame 021096/0825 →
RELEASE Recorded Mar 7, 2008
From: TRIPLEPOINT CAPITAL LLC
To: MENDOCINO SOFTWARE
Reel/Frame 020632/0001 →
SECURITY AGREEMENT Recorded Feb 8, 2008
From: MENDOCINO SOFTWARE, INC.
To: TRIPLEPOINT CAPITAL LLC
Reel/Frame 020486/0198 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 30, 2005
From: ANDERSON, CURTIS; WOYCHOWSKI, JOHN P.; WADHER, PRATIK; NARASIMHAN, BALAJI
To: MENDOCINO SOFTWARE, INC.
Reel/Frame 016948/0573 →
Continuity (2)
Provisional Application 6060516800 · Aug 30, 2004
Related Publication 20060047997A1 · Mar 2, 2006