AUTOMATIC FILE VERSIONING

• US 20090024674A1
• Filed: 07/17/2008
• Published: 01/22/2009
• Est. Priority Date: 07/17/2007
• Status: Abandoned Application

• Current Assignee: Gridlron Software Incorporated
• Original Assignee: Gridlron Software Incorporated
• Inventors: GALLAGHER, Warren
• Application Number:
  US12/175,238
• Publication Number:
  US 20090024674A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/1873 Versioning file systems, temporal file systems, e.g. file system supporting different historic versions of files
• CPC Class Codes: G06F 40/197 Version control for software G06F8/71

Abstract

A method and system are provided to automatically and transparently version files across many desktop applications without requiring the user to take specific action to cause the versioning to occur. Previous versions and versioning information can both be stored using hard links, and the versioning information can be used to determine a version history for a file. Embodiments of the present invention do not require applications to be modified to support this versioning method. Further, using one approach, the application does not even know that the versioning is occurring. The present invention provides an automatic versioning solution that is completely transparent to the user, which causes overwrite operations to be seamlessly co-opted into versioning operations which retain previous document versions instead of overwriting them.

Claims

1. A method of automatic file versioning in a computing environment, comprising:

detecting initiation of a file system event wherein an updated version of an original file stored at an original storage location is written to a new storage location;

identifying the file system event as a first component of a file versioning event; and

creating a hard link to the original storage location, the hard link indicating a version relationship between the original file and the updated version,

the step of creating the hard link occurring prior to occurrence of a final component of the file versioning event wherein an original file storage location identifier is scheduled to be disassociated from the original storage location.

2. The method of claim 1 wherein the hard link includes a hard link storage location identifier derived from an updated file storage location identifier associated with the updated file, the hard link storage location identifier indicating the version relationship between the original file and the updated version.

3. The method of claim 2 wherein the hard link storage location identifier comprises a hard link directory path and file name derived from a directory path and file name associated with the updated file.

4. The method of claim 1 wherein the steps of detecting, identifying and creating are performed transparently without input from a user.

5. The method of claim 4 wherein the steps of detecting, identifying and creating are performed as background processes in the computing environment.

6. The method of claim 1 wherein performance of the steps of detecting, identifying and creating is application-independent having regard to an application associated with the file system event.

7. The method of claim 1 wherein performance of the steps of detecting, identifying and creating is file-format independent having regard to a file format associated with the file system event.

8. A system for automatic file versioning in a computing environment comprising:

a file system event monitor, in communication with a file system events engine, for detecting initiation of a file system event wherein an updated version of an original file stored at an original storage location is written to a new storage location, and for identifying the file system event as a first component of a file versioning event; and

a file versioner, in communication with the file system event monitor, for creating a hard link to the original storage location upon receipt of a communication from the file system event monitor indicating that the first component of the file versioning event has been identified, the hard link indicating a version relationship between the original file and the updated version,

wherein the file versioner creates the hard link prior to occurrence of a final component of the file versioning event wherein an original storage location identifier is scheduled to be disassociated from a file system location for the original file.

9. The system of claim 8 wherein the file versioner derives a hard link storage location identifier from an updated file storage location identifier associated with the updated file, the hard link storage location identifier indicating the version relationship between the original file and the updated version.

10. The system of claim 9 wherein the hard link storage location identifier comprises a directory path and file name derived from a directory path and file name associated with the updated file.

11. The system of claim 8 wherein the file system event monitor and the file versioner operate transparently without input from a user.

12. The system of claim 11 wherein the file system event monitor and file versioner operate as background processes in the computing environment.

13. The system of claim 8 wherein operation of the file system event monitor and file versioner is application-independent having regard to an application associated with the file system event.

14. The system of claim 8 wherein operation of the file system event monitor and file versioner is file-format-independent having regard to a file format associated with the file system event.

15. The system of claim 8 further comprising a user preferences module for restricting the operation of the file versioner according to stored file versioning preferences.

16. A computer readable medium containing computer instructions which, when executed, cause a processor to perform a method of automatic file versioning, comprising:

instructions for detecting initiation of a file system event wherein an updated version of an original file stored at an original storage location is written to a new storage location;

instructions for identifying the file system event as a first component of a file versioning event; and

instructions for creating a hard link to the original storage location, the hard link indicating a version relationship between the original file and the updated version,

the instructions for creating the hard link ensuring that the hard link is created prior to occurrence of a final component of the file versioning event wherein an original file storage location identifier is scheduled to be disassociated from the original storage location.

17. The computer readable medium of claim 16 wherein the instructions for creating the hard link further comprise instructions for ensuring that the hard link is provided with a hard link storage location identifier derived from an updated file storage location identifier associated with the updated file, the hard link storage location identifier indicating the version relationship between the original file and the updated version.

18. The computer readable medium of claim 17 wherein the instructions for creating the hard link further comprise instructions for ensuring that the hard link is provided with a storage location identifier comprising a hard link directory path and file name derived from a directory path and file name associated with the updated file.

19. The computer readable medium of claim 18 further comprising instructions for ensuring that, when the instructions contained within the computer readable medium are executed, the instructions for detecting, identifying and creating are executed transparently without input from a user.

20. The computer readable medium of claim 19 further comprising instructions for ensuring that, when the instructions contained within the computer readable medium are executed, the instructions for detecting, identifying and creating are executed as background processes in the computing environment.

21. The computer readable medium of claim 16 wherein the instructions for detecting, identifying and creating are application-independent having regard to an application associated with the file system event.

22. The computer readable medium of claim 16 wherein the instructions for detecting, identifying and creating are file-format independent having regard to a file format associated with the file system event.

23. A method of automatic file versioning in a computing environment comprising:

detecting initiation by an application of a file system event in a file system wherein an updated version of an original file stored at an original storage location is written to a new storage location;

identifying the file system event as a first component of a file versioning event;

if the application can hard link and if the file system can hard link, creating a hard link to the original storage location prior to occurrence of a final component of the file versioning event wherein the original storage location is scheduled to be disassociated from a file system location for the original file, the hard link indicating a version relationship between the original file and the updated version;

if the file system is a remote file system and either one of the application and the file system cannot hard link, creating a server-side copy of the file; and

if the file system is a local file system and either the application cannot hard link or the file system cannot hard link, creating a copy of the file.

24. A method of automatic file versioning in a computing environment, comprising:

detecting initiation of a file system event wherein an updated version of an original file stored at an original storage location is written to a new storage location;

identifying the file system event as a first component of a file versioning event;

causing a new file storage location identifier to become associated with the original storage location, the new file storage location identifier indicating a version relationship between the original file and the updated version, and preventing the file system from de-allocating the original storage location,

the step of causing a new file storage location identifier to become associated with the original storage location occurring prior to occurrence of a final component of the file versioning event wherein an original file storage location identifier is scheduled to be disassociated from the original storage location.