Apparatus for policy based storage of file data and meta-data changes over time

• US 7,693,891 B2
• Filed: 04/09/2007
• Issued: 04/06/2010
• Est. Priority Date: 10/29/2002
• Status: Expired due to Fees

• Current Assignee: Micro Focus Software, Inc. (Open Text Corporation)
• Original Assignee: Novell Incorporated (Open Text Corporation)
• Inventors: Jones, Richard D., Stokes, Randall K.
• Primary Examiner(s): Fleurantin; Jean B.
• Assistant Examiner(s): Ly; Anh
• Application Number:
  US11/733,103
• Publication Number:
  US 20070180313A1
• Time in Patent Office: 1,093 Days
• Field of Search: 707/9, 707/10, 707203-204, 709223-224, 687/695, 687/704
• US Class Current: 707/695
• CPC Class Codes: G06F 16/10 File systems; File servers
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99939 Privileged access
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

A time domain server includes a version storage. The time domain server declares epochs for a source server, then requests events from the source server. As the time domain server receives events, it uses the events to update the version storage to store versions of files from the source server.

Claims

1. A computer-implemented method for storing changes on a time domain server, comprising:

declaring a start to an epoch, wherein declaring a start to an epoch includes declaring a start to an epoch for a source server;

maintaining the epoch as active until an end to the epoch is declared;

requesting a file event from the source server, the file event identified as having occurred during the epoch and identifying a file whose timestamp lies in the epoch;

associating the file with the epoch;

copying the file from the source server;

saving the file on the time domain server, the file versioned by the timestamp, wherein saving the file includes associating the file with the source server;

retaining an earlier version of the file on the time domain server;

declaring a start to a second epoch for a second source server;

maintaining the second epoch as active until an end to the second epoch is declared;

requesting a second file event from the second source server, the second event identified as having occurred during the second epoch on the second source server and identifying a second file whose timestamp lies in the first epoch;

copying the second file from the second source server; and

saving the second file on the time domain server, the second file versioned by the timestamp and associated with the second source server.

2. A computer-implemented method according to claim 1, further comprising declaring an end to the epoch.

3. A computer-implemented method according to claim 1, further comprising informing the source server that the file event can be removed from an event list.

4. A computer-implemented method according to claim 1, wherein:

the method further comprises determining if the file is to be stored according to a policy; and

copying the file includes copying the file from a first storage the source server if the policy indicates the file is to be stored.

5. A computer-implemented method according to claim 1, further comprising:

determining that a number of earlier versions of the file exist;

determining a maximum number of earlier versions of the file to retain according to a policy; and

removing an oldest version of the file from the time domain server if the policy indicates that too many earlier versions of the file exist.

6. A computer-implemented method according to claim 1, further comprising indexing the file and the earlier version of the file in a search database.

7. A computer-implemented method according to claim 1, further comprising:

copying an access control information for the file from the source server; and

storing the access control information with the file on the time domain server.

8. A computer-implemented method for storing changes on a time domain server, comprising:

declaring a start to an epoch, wherein declaring a start to an epoch includes declaring a start to an epoch for a source server;

maintaining the epoch as active until an end to the epoch is declared;

requesting a file event from the source server, the file event identified as having occurred during the epoch and identifying a file whose timestamp lies in the epoch;

copying the file from the source server;

saving the file on the time domain server, the file versioned by the timestamp, wherein saving the file includes associating the file with the source server;

determining if an earlier version of the file exists on the time domain server;

determining if the earlier version of the file has been stored for a specified time interval according to a policy;

removing the earlier version of the file from the time domain server if the policy indicates that the earlier version of the file is to be removed;

declaring a start to a second epoch for a second source server;

maintaining the second epoch as active until an end to the second epoch is declared;

requesting a second file event from the second source server, the second event identified as having occurred during the second epoch on the second source server and identifying a second file whose timestamp lies in the first epoch;

copying the second file from the second source server; and

saving the second file on the time domain server, the second file versioned by the timestamp and associated with the second source server.

9. A computer-implemented method according to claim 8, further comprising declaring an end to the epoch.

10. A computer-implemented method according to claim 9, further comprising:

monitoring the file event by the source server;

verifying by the source server that the file event occurred after the start of the epoch and before the end of the epoch; and

identifying the file event as having occurred during the epoch by the source server if the event occurred after the start of the epoch and before the end of the epoch.

11. A computer-implemented method according to claim 8, further comprising informing the source server that the file event can be removed from an event list.

12. A computer-implemented method according to claim 8, wherein:

the method further comprises determining if the file is to be stored according to a policy; and

copying the file includes copying the file from a first storage the source server if the policy indicates the file is to be stored.

13. A computer-implemented method according to claim 8, further comprising:

determining that a number of earlier versions of the file exist;

determining a maximum number of earlier versions of the file to retain according to a policy; and

removing an oldest version of the file from the time domain server if the policy indicates that too many earlier versions of the file exist.

14. A computer-implemented method according to claim 8, further comprising indexing the file and the earlier version of the file in a search database.

15. A computer-implemented method according to claim 8, further comprising:

copying an access control information for the file from the source server; and

storing the access control information with the file on the time domain server.

16. A tangible computer-readable medium storing computer-executable instructions that, when executed, result in a computer:

declaring a start to an epoch, wherein declaring a start to an epoch includes declaring a start to an epoch for a source server;

maintaining the epoch as active until an end to the epoch is declared;

requesting a file event from the source server, the file event identified as having occurred during the epoch and identifying a file whose timestamp lies in the epoch;

associating the file with the epoch;

copying the file from the source server;

saving the file on the time domain server, the file versioned by the timestamp, wherein saving the file includes associating the file with the source server;

retaining an earlier version of the file on the time domain server;

declaring a start to a second epoch for a second source server;

maintaining the second epoch as active until an end to the second epoch is declared;

requesting a second file event from the second source server, the second event identified as having occurred during the second epoch on the second source server and identifying a second file whose timestamp lies in the first epoch;

copying the second file from the second source server; and

saving the second file on the time domain server, the second file versioned by the timestamp and associated with the second source server.

17. A tangible computer-readable medium according to claim 16, wherein the computer-executable instructions, when executed, further result in the computer declaring an end to the epoch.

18. A tangible computer-readable medium according to claim 16, wherein the computer-executable instructions, when executed, further result in the computer informing the source server that the file event can be removed from an event list.

19. A tangible computer-readable medium according to claim 16, wherein the computer-executable instructions, when executed, further result in the computer determining if the file is to be stored according to a policy, and wherein copying the file includes copying the file from a first storage the source server if the policy indicates the file is to be stored.

20. A tangible computer-readable medium according to claim 16, wherein the computer-executable instructions, when executed, further result in the computer:

determining that a number of earlier versions of the file exist;

determining a maximum number of earlier versions of the file to retain according to a policy; and

removing an oldest version of the file from the time domain server if the policy indicates that too many earlier versions of the file exist.

21. A tangible computer-readable medium according to claim 16, wherein the computer-executable instructions, when executed, further result in the computer indexing the file and the earlier version of the file in a search database.

22. A tangible computer-readable medium according to claim 16, wherein the computer-executable instructions, when executed, further result in the computer:

copying an access control information for the file from the source server; and

storing the access control information with the file on the time domain server.