Recovery point data view shift through a direction-agnostic roll algorithm

1. A method comprising:

generating, at a predetermined interval, backed up data on a snapshot comprising a read-only copy of a data set frozen at a point in time;

forming a data view of the backed up data around a recovery point associated with an event, wherein the event is at least one of a system crash, a login failure, a configuration change, and an automatic backup operation of data;

shifting the data view around the recovery point through a direction-agnostic roll algorithm configured to utilize a roll-forward algorithm to shift the data view to a time after the recovery point and a roll-backward algorithm to shift the data view to a time before the recovery point, wherein the data view is specific to a volume object in a kernel that imitates another volume having original data and wherein the data view is managed by a kernel space that processes an access request through at least one table using a meta-data created in a retention log;

generating a marking data at the recovery point to enable the direction-agnostic roll algorithm to operate and to reduce a recovery time objective when an algorithm is applied; and

coalescing data around the recovery point and other determinable recovery points at a threshold interval to reduce storage requirements.

2. The method of claim 1 , further comprising determining that data integrity is consistent at the recovery point by examining data and meta-data associated with the recovery point.

3. The method of claim 2 , further comprising associating the recovery point with at least one of an automatically generated event, a user definable event, and a prepackaged event.

4. The method of claim 3 , further comprising maintaining data adjacent to the recovery point in a log data structure that is stored in a file system as a multitude of files.

5. The method of claim 4 , further comprising retaining differing quantities of data around the recovery point based on a programmatic methodology that considers space utilization and data consistency associated with the time after the recovery point and the time before the recovery point.

6. A method comprising:

generating, at a predetermined interval, backed up data on a snapshot comprising a read-only copy of a data set frozen at a point in time;

forming a data view of the backed up data around a recovery point associated with an event, wherein the event is at least one of a system crash, a login failure, a configuration change, and an automatic backup operation of data;

shifting the data view around the recovery point through a direction-agnostic roll algorithm configured to utilize a roll-forward algorithm to shift the data view to a time after the recovery point and a roll-backward algorithm to shift the data view to a time before the recovery point, wherein the data view is specific to a volume object in a kernel that imitates another volume having original data and wherein the data view is managed by a kernel space that processes an access request through at least one table using a meta-data created in a retention log;

retaining differing quantities of data around the recovery point based on a programmatic methodology that considers space utilization and data consistency associated with the time after the recovery point and the time before the recovery point; and

coalescing data around the recovery point and other determinable recovery points at a threshold interval to reduce storage requirements.

7. The method of claim 6 , further comprising determining that data integrity is consistent at the recovery point by examining data and meta-data associated with the recovery point.

8. The method of claim 7 , further comprising associating the recovery point with at least one of an automatically generated event, a user definable event, and a prepackaged event.

9. The method of claim 8 , further comprising generating a marking data at the recovery point to enable the direction-agnostic roll algorithm to operate and to reduce a recovery time objective when the direction-agnostic roll algorithm is applied.

10. The method of claim 9 , further comprising maintaining data adjacent to the recovery point in a log data structure that is stored in a file system as a multitude of files.

11. A method comprising:

generating, at a predetermined interval, backed up data on a snapshot comprising a read-only copy of a data set frozen at a point in time;

forming a data view of the backed up data around a recovery point associated with an event, wherein the event is at least one of a system crash, a login failure, a configuration change, and an automatic backup operation of data;

shifting the data view around the recovery point through a direction-agnostic roll algorithm configured to utilize a roll-forward algorithm to shift the data view to a time after the recovery point and a roll-backward algorithm to shift the data view to a time before the recovery point, wherein the data view is managed by a kernel space that processes an access request through at least one table using a meta-data created in a retention log, and wherein the data view is specific to a volume object in a kernel that imitates another volume having original data;

determining that data integrity is consistent at the recovery point by examining data and meta-data associated with the recovery point;

maintaining data adjacent to the recovery point in a log data structure that is stored in a file system as a multitude of files; and

coalescing data around the recovery point and other determinable recovery points at a threshold interval to reduce storage requirements.

12. The method of claim 11 , further comprising associating the recovery point with at least one of an automatically generated event, a user definable event, and a prepackaged event.

13. The method of claim 12 , further comprising generating a marking data at the recovery point to enable the direction-agnostic roll algorithm to operate and to reduce a recovery time objective when the direction-agnostic roll algorithm is applied.

14. The method of claim 13 , further comprising retaining differing quantities of data around the recovery point based on a programmatic methodology that considers space utilization and data consistency associated with the time after the recovery point and the time before the recovery point.