Localized intelligent data management for a storage system

• US 20040098394A1
• Filed: 02/12/2003
• Published: 05/20/2004
• Est. Priority Date: 02/12/2002
• Status: Abandoned Application

• Current Assignee: Perry Wayde Merritt
• Original Assignee: Perry Wayde Merritt
• Inventors: Miller, Jay, Oister, Dan, Merritt, Perry Wayde
• Application Number:
  US10/366,063
• Publication Number:
  US 20040098394A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1458 Management of the backup or restore process
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 16/10 File systems; File servers

Abstract

An intelligent data management utility is disposed between a storage system and a data source to automatically and transparently initiate appropriate data management operations without interfering with normal data flow between the data source and the storage system. According to one embodiment, the intelligent data management utility resides within a storage controller and includes a mechanism for intercepting events, such as file activity. Based upon the file activity (e.g., file creation, file open, file read, file write, file close, and the like), the intelligent data management utility invokes one or more appropriate data management applications using a tightly-coupled transport and policy store. The transport queries the policy store for actions to be performed and invokes the appropriate data management application or applications. Upon completion of the data management tasks, status is returned through the transport to the file system filter.

Claims

1. A method comprising:

determining the existence of a predetermined event at a storage controller;

responsive to the predetermined event, initiating data management activity for a storage device associated with the storage controller.

2. The method of claim 1, wherein the predetermined event is a file system event.

3. The method of claim 2, wherein the data management activity includes one or more of the following:

(a) hierarchical storage management;

(b) storage aggregation or virtualization;

(c) file replication;

(d) backup;

(e) virus scanning;

or

(f) encryption.

4. The method of claim 3, wherein said determining the existence of a predetermined event at a storage controller is accomplished by way of a file system filter in the operating system of the storage controller.

5. The method of claim 1, wherein the predetermined event relates to a file, and wherein said initiating data management activity for a storage device associated with the storage controller comprises determining an appropriate data management activity to perform on the file based upon the predetermined event by querying a policy store to identify one or more policies associated with the file.

6. The method of claim 1, further comprising associating policies with file system activity.

7. The method of claim 1, further comprising associating one or more data management applications with file system activity.

8. The method of claim 1, further comprising capturing file system metadata describing access and reference patterns for one or more files for future analysis.

9. The method of claim 1, further comprising capturing file system metadata describing access and reference patterns for one or more files for future action.

10. The method of claim 9, wherein the captured file system metadata is used to support one or more hierarchical storage management features by allowing active files to be distinguished from less frequently referenced files.

11. The method of claim 10, further comprising:

maintaining the active files on primary storage media; and

releasing the less frequently referenced files to backup storage media.

12. A storage controller comprising:

an application environment including one or more data management applications each associated with a data management activity, and a policy store to associate the one or more data management applications with file system requests; and

a kernel environment coupled in communication with the application environment via a transport mechanism, the kernel environment including a file system, a virtual file system, and a file system filter logically interposed between the file system and the virtual file system to capture the file system requests and locally initiate appropriate data management activity in response thereto by communicating the file system requests to the application environment via the transport mechanism.

13. The storage controller of claim 12, wherein the data management activity includes one or more of the following:

(a) hierarchical storage management;

(b) storage aggregation or virtualization;

(c) file replication;

(d) backup;

(e) virus scanning;

or

(f) encryption.

14. The storage controller of claim 12, wherein the file system filter further facilitates capturing of file system metadata describing access and reference patterns for one or more files.

15. The storage controller of claim 14, wherein the captured file system metadata is used to support one or more hierarchical storage management features by allowing active files to be distinguished from less frequently referenced files.