Generating a recovery snapshot and creating a virtual view of the recovery snapshot

1. A method, comprising:

generating a recovery snapshot of backed up data at a predetermined interval;

creating a virtual view of the recovery snapshot around a recovery point using an algorithm tied to an original data, a change log data, and a consistency data related to an event associated with the recovery point and storing the virtual view instead of a data view of the recovery snapshot to reduce a time consumption and a capacity consumption associated therewith, the virtual view being created following at least one of a pause and a suspension of operation of a client device configured to originate a request associated with the backed up data, and the recovery point capable of being a system crash, a login failure, a configuration change and an automatic backup operation of data; and

providing, through the recovery snapshot, an ability to position forward and backward from the recovery point when a delayed roll back algorithm is applied based on the virtual view, thereby providing an ability to roll to a data state occurring earlier in time compared to the recovery point and to a data state occurring later in time compared to the recovery point.

2. The method of claim 1 , further comprising redirecting an access request to the original data based on metadata information provided in the virtual view.

3. The method of claim 1 , further comprising substantially retaining a timestamp data, a location of a change, and a time offset of the change as compared to the original data.

4. The method of claim 1 , further comprising utilizing a relational database to process the change log data in metadata format, and to process other on-disk data using a binary-tree format.

5. The method of claim 1 , wherein the virtual view is specific to a volume object in a kernel that imitates a volume having the original data.

6. The method of claim 5 , comprising managing the virtual view through a kernel space that is configured to process an access request through at least one table using metadata created in a retention log.

7. The method of claim 1 , further comprising exporting the virtual view as a virtual volume using at least one of an Internet Small Computer System (iSCSI) and a fiber channel transport to an external processing device.

8. The method of claim 1 , comprising applying the change log data when the virtual view is unfrozen after a user session reaches a level state.

9. The method of claim 1 , further comprising:

generating a series of indexes of the virtual view to enable linking to an event description of the virtual view rather than to an actual data in the original data; and

automatically creating the virtual view in at least one of a scheduled and an event driven manner

10. The method of claim 1 , further comprising automatically exporting the virtual view to a physical storage medium.

11. The method of claim 1 , comprising executing instructions associated with enabling operations thereof through a processor communicatively coupled to a physical memory.

12. A non-transitory medium, readable through a computing system and including instructions embodied therein configured to be executable through the computing system comprising:

instructions associated with generating a recovery snapshot of backed up data;

instructions associated with creating a virtual view of the recovery snapshot around a recovery point using an algorithm tied to an original data, a change log data, and a consistency data related to an event associated with the recovery point and storing the virtual view instead of a data view of the recovery snapshot to reduce a time consumption and a capacity consumption associated therewith, the virtual view being created following at least one of a pause and a suspension of operation of a client device configured to originate a request associated with the backed up data, and the recovery point capable of being a system crash, a login failure, a configuration change and an automatic backup operation of data; and

instructions associated with providing, through the recovery snapshot, an ability to position forward and backward from the recovery point when a delayed roll back algorithm is applied based on the virtual view, thereby providing an ability to roll to a data state occurring earlier in time compared to the recovery point and to a data state occurring later in time compared to the recovery point.

13. The non-transitory medium of claim 12 , further comprising instructions associated with redirecting an access request to the original data based on metadata information provided in the virtual view.

14. The non-transitory medium of claim 12 , further comprising instructions associated with substantially retaining a timestamp data, a location of a change, and a time offset of the change as compared to the original data.

15. The non-transitory medium of claim 12 , further comprising instructions associated with utilizing a relational database to process the change log data in a metadata format, and to process other on-disk data using a binary-tree format.

16. The non-transitory medium of claim 12 , comprising instructions associated with rendering the virtual view specific to a volume object in a kernel that imitates a volume having the original data.

17. The non-transitory medium of claim 16 , comprising managing the virtual view through a kernel space that is configured to process an access request through at least one table using metadata created in a retention log.

18. A system, comprising:

a memory; and

a processor communicatively coupled to the memory, the processor being configured to execute instructions associated with enabling:

generating a recovery snapshot of backed up data at a predetermined interval,

creating a virtual view of the recovery snapshot around a recovery point using an algorithm tied to an original data, a change log data, and a consistency data related to an event associated with the recovery point and storing the virtual view instead of a data view of the recovery snapshot to reduce a time consumption and a capacity consumption associated therewith, the virtual view being created following at least one of a pause and a suspension of operation of a client device configured to originate a request associated with the backed up data, and the recovery point capable of being a system crash, a login failure, a configuration change and an automatic backup operation of data, and

providing, through the recovery snapshot, an ability to position forward and backward from the recovery point when a delayed roll back algorithm is applied based on the virtual view, thereby providing an ability to roll to a data state occurring earlier in time compared to the recovery point and to a data state occurring later in time compared to the recovery point.

19. The system of claim 18 , wherein the processor is further configured to execute instructions associated with enabling redirection of an access request to the original data based on metadata information provided in the virtual view.

20. The system of claim 18 , wherein the processor is further configured to execute instructions associated with enabling substantial retention of a timestamp data, a location of a change, and a time offset of the change as compared to the original data.