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.

Abstract: System and method for performing restores from backups while applications are active and accessing the data being restored. A map correlating destination locations on primary storage to source locations on backup storage for files to be restored may be generated. A restore of the files from the backup storage to the primary storage may be started. During the restore, one or more blocks of data of a file needed by an application may be determined. The map may be accessed to determine if the blocks have been restored. If the blocks have not been restored, the blocks may be restored from the backup storage to the primary storage. The restored blocks of data are accessible by the application while the restore is in progress. The map may be updated to indicate blocks of data that have been restored to the primary storage.