System and method for policy-based data lifecycle management

• US 7,680,830 B1
• Filed: 05/31/2005
• Issued: 03/16/2010
• Est. Priority Date: 05/31/2005
• Status: Expired due to Fees

• Current Assignee: Veritas Technologies, LLC (Whitehouse Group Ltd.)
• Original Assignee: Symantec Operating Corporation (NortonLifeLock Inc.)
• Inventors: Ohr, James Philip, Bunker, Guy Barry Owen, Chandler, Christopher James Elphinstone
• Primary Examiner(s): Corrielus; Jean M
• Assistant Examiner(s): Ruiz; Angelica
• Application Number:
  US11/144,116
• Time in Patent Office: 1,750 Days
• Field of Search: 707200-206
• US Class Current: 1/1
• CPC Class Codes: G06F 16/125 characterised by the use of retention policies retention policies for HSM systems G06F16/185

Abstract

System and method for policy-based lifecycle management of data in file systems. In embodiments, an expiration policy for the files may be stored as part of the file system metadata. The expiration policy may be as simple as an expiration date for the file, or a more complex policy that specifies one or more metrics to be evaluated to determine if a file is expired. The expiration policy may also specify one or more actions to be taken if the file has expired. The expiration policy may be evaluated on attempts to access the files in the file system, on other file systems, and on backup/archive images to determine if the files are expired and thus whether access to the files is to be allowed. In one embodiment, a scan mechanism may periodically or aperiodically delete files in the file system for which the expiration date has passed.

Claims

1. A computer-implemented method, comprising:

storing, by file system software implemented on at least one computing device, expiration policies for at least some files within a file system in file system metadata maintained by the file system software, wherein the file system software is configured to provide for creation of, management of, and access to the files within the file system, wherein each expiration policy is specific to a respective one of the at least some files and specifies one or more metrics for evaluation to determine whether the associated file is ready for expiration, wherein the file system metadata includes information that the file system software maintains on files stored in the file system, wherein a specific expiration policy associated with a file is stored in a portion of the information that the file system software maintains on the files stored in the file system that is specific to the file and that also includes location information for the file;

wherein said storing, for said at least some files, a respective expiration policy for the respective file in a portion of the information that is specific to the respective file and that also includes location information for the file, enables each of the at least some files for moving or copying to another location while maintaining its association with its respective expiration policy; and

evaluating, by the file system software, the expiration policies stored in the file system metadata, wherein said evaluating produces a result indicating at least one file that has passed an expiration date for the respective file according to the expiration policy corresponding to the respective file.

2. The computer-implemented method as recited in claim 1, wherein each expiration policy further specifies one or more actions for taking by the file system software if the expiration date for the associated file has passed.

3. The computer-implemented method as recited in claim 1, further comprising:

specifying the expiration policies for the files in response to user input and in accordance with a data lifecycle management policy for the file system, wherein said specifying is performed by policy management functionality of the file system software; and

implementing one or more security measures to protect the expiration policies from unauthorized access.

4. The computer-implemented method as recited in claim 1, further comprising periodically or aperiodically performing, by the file system software, a scan process to evaluate the expiration policies stored in the file system metadata and delete files from the file system for which the expiration date has passed.

5. The computer-implemented method as recited in claim 1, further comprising denying access, by the file system software, to files in the file system for which said result indicates the expiration date has passed.

6. The computer-implemented method as recited in claim 1, further comprising denying restore, by the file system software, of particular files to the file system from a backup or archive image for which said result indicates the expiration date has passed.

7. The computer-implemented method as recited in claim 1, further comprising:

intercepting access calls to the files in the file system from one or more applications; and

evaluating the expiration policy for files specified by the access calls to determine if access to the specified files is allowed or denied;

wherein said intercepting access calls and said evaluating the expiration policy for files specified by the access calls are performed by a filter driver.

8. The computer-implemented method as recited in claim 1, wherein the file system metadata are one of inodes, directories, indirect blocks, superblocks, and extended attributes for the files.

9. The computer-implemented method as recited in claim 1, further comprising storing copies of the expiration policies in a catalog, wherein said storing copies of the expiration policies in a catalog is performed by an application or utility that periodically or aperiodically scans the files within the file system, and wherein the catalog is maintained by the application or utility.

10. The computer-implemented method as recited in claim 9, wherein the application or utility is a backup system, and wherein the copies of the expiration policies are stored in a backup catalog and in a backup image during a backup operation performed by the backup system that generates the backup image of the file system.

11. The computer-implemented method as recited in claim 9, further comprising accessing, by the file system software, a copy of the expiration policy for a file on the file system stored in the catalog or in a backup or archive image to recover the expiration policy for a copy of the file for which the expiration policy has been lost.

12. The computer-implemented method as recited in claim 9, further comprising modifying a copy of an expiration policy for a file stored in the catalog in response to a modification of the expiration policy stored in the file system metadata for the file.

13. The computer-implemented method as recited in claim 9, further comprising modifying a copy of an expiration policy stored in the catalog for a file that has been deleted from the file system.

14. The computer-implemented method as recited in claim 1, further comprising:

copying a file from the file system to another file system;

copying an expiration policy for the file with the copy of the file from the file system to the other file system; and

evaluating the copy of the expiration policy on the other file system to determine if the copy of the file has passed an expiration date for the file according to the copy of the expiration policy.

15. The computer-implemented method as recited in claim 1, further comprising:

copying a file from the file system to another file system, wherein an expiration policy of the file is not copied to the other file system;

recovering an expiration policy for the file on the other file system, wherein said recovering comprises;

determining that the file on the other file system is a copy of the file on the file system; and

associating the expiration policy of the file on the file system with the copy of the file on the other file system;

attempting to copy the copy of the file back to the file system or attempting to access the copy of the file on the other file system; and

evaluating the expiration policy associated with the copy of the file in response to the copy attempt or the access attempt to determine if the file has passed an expiration date for the file, wherein the copy attempt or access attempt is denied if the expiration date for the file is passed and allowed if the expiration date for the file is not passed.

16. The computer-implemented method as recited in claim 1, further comprising:

generating a copy of a file on the file system; and

copying the expiration policy including the expiration date of the original file to the file system metadata for the copy of the file.

23. The computer-implemented method as recited in claim 1, wherein the one or more metrics include an expiration date.

17. A data storage system, comprising:

one or more storage devices comprising a file system;

a host system comprising a memory medium storing program instructions, wherein the program instructions are executable on the host system to implement file system software configured to manage and control access to the file system; and

one or more client systems each comprising a memory medium storing program instructions, wherein the program instructions are executable on the client system to implement one or more applications configured to access files in the file system via the file system software;

wherein the file system software is configured to;

store expiration policies for at least some files within the file system in file system metadata maintained by the file system software, wherein each expiration policy is specific to a respective one of the at least some files and specifies one or more metrics for evaluation to determine whether the associated file is ready for expiration, wherein the file system metadata includes information that the file system software maintains on files stored in the file system, wherein a specific expiration policy associated with a file is stored in a portion of the information that the file system software maintains on the files stored in the file system that is specific to the file and that also includes location information for the file;

wherein said storing, for said at least some files, a respective expiration policy for the respective file in a portion of the information that is specific to the respective file and that also includes location information for the file, enables each of the at least some files for moving or copying to another location while maintaining its association with its respective expiration policy;

evaluate the expiration policies stored in the file system metadata to determine files that have passed an expiration date; and

grant or deny access to particular ones of the files in the file system by the applications according to results of said evaluation of the expiration policies, wherein access is denied for files that have passed the expiration date.

18. The data storage system as recited in claim 17, wherein the file system software is further configured to periodically or aperiodically delete files from the file system for which said evaluation of the expiration policies determines that the expiration date has passed.

24. The data storage system as recited in claim 17, wherein the one or more metrics include an expiration date.

25. The data storage system as recited in claim 17, wherein the file system metadata are one of inodes, directories, indirect blocks, superblocks, and extended attributes of files.

19. A system, comprising:

a processor; and

a memory comprising program instructions, wherein the program instructions are executable by the processor to implement file system software configured to manage and control access to a file system, wherein the file system software comprises a file expiration mechanism configured to;

store expiration policies for at least some files within the file system in file system metadata maintained by the file system software, wherein each expiration policy is specific to a respective one of the at least some files and specifies one or more metrics for evaluation to determine whether the associated file is ready for expiration, wherein the file system metadata includes information that the file system software maintains on files stored in the file system, wherein a specific expiration policy associated with a file is stored in a portion of the information that the file system software maintains on the files stored in the file system that is specific to the file and that also includes location information for the file;

wherein said storing, for said at least some files, a respective expiration policy for the respective file in a portion of the information that is specific to the respective file and that also includes location information for the file, enables each of the at least some files for moving or copying to another location while maintaining its association with its respective expiration policy;

evaluate the expiration policies stored in the file system metadata to determine if the files have passed an expiration date; and

grant or deny access to particular ones of the files in the file system in accordance with results of said evaluation of the expiration policies.

20. The system as recited in claim 19, wherein the file expiration mechanism is further configured to periodically or aperiodically delete files from the file system for which said evaluation of the expiration policies determines that the expiration date has passed.

26. The system as recited in claim 19, wherein the one or more metrics include an expiration date.

27. The system as recited in claim 19, wherein the file system metadata are one of inodes, directories, indirect blocks, superblocks, and extended attributes of files.

21. A computer-accessible storage medium comprising program instructions, wherein the program instructions are computer-executable to implement:

storing expiration policies for at least some files within a file system in file system metadata maintained by file system software, wherein each expiration policy is specific to a respective one of the at least some files and specifies one or more metrics for evaluation to determine whether the associated file is ready for expiration, wherein the file system metadata includes information that the file system software maintains on files stored in the file system, wherein a specific expiration policy associated with a file is stored in a portion of the information that the file system software maintains on the files stored in the file system that is specific to the file and that also includes location information for the file, and wherein the file system software is configured to manage and control access to the file system;

wherein said storing, for said at least some files, a respective expiration policy for the respective file in a portion of the information that is specific to the respective file and that also includes location information for the file, enables each of the at least some files for moving or copying to another location while maintaining its association with its respective expiration policy;

evaluating the expiration policies stored in the file system metadata to determine files that have passed an expiration date; and

granting or denying access to particular ones of the files in the file system according to results of said evaluation of the expiration policies, wherein access is denied for files that have passed the expiration date.

22. The computer-accessible storage medium as recited in claim 21, wherein the program instructions are computer-executable to implement periodically or aperiodically deleting files from the file system for which said evaluating the expiration policies determines that the expiration date has passed.

28. The computer-accessible storage medium as recited in claim 21, wherein the one or more metrics include an expiration date.

29. The computer-accessible storage medium as recited in claim 21, wherein the file system metadata are one of inodes, directories, indirect blocks, superblocks, and extended attributes of files.