Systems and methods for classifying and transferring information in a storage network

• US 7,660,800 B2
• Filed: 11/28/2006
• Issued: 02/09/2010
• Est. Priority Date: 11/28/2005
• Status: Active Grant

• Current Assignee: CommVault Systems Incorporated
• Original Assignee: CommVault Systems Incorporated
• Inventors: Brockway, Brian, Schwartz, Jeremy A., Ngo, David, Prahlad, Anand, Muller, Marcus S.
• Primary Examiner(s): Trujillo; James
• Assistant Examiner(s): Moser; Bruce M.
• Application Number:
  US11/564,153
• Publication Number:
  US 20070185916A1
• Time in Patent Office: 1,169 Days
• Field of Search: 707/10, 707/200, 709/201
• US Class Current: 707/802
• CPC Class Codes: G06F 11/1435 using file system or storage system metadata
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1461 Backup scheduling policy
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 11/1466 to make the backup process non-disruptive
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery
• CPC Class Codes: G06F 16/11 File system administration, e.g. details of archiving or snapshots file system backup G06F11/14
• CPC Class Codes: G06F 16/119 Details of migration of file systems migration mechanisms in storage systems G06F3/0647
• CPC Class Codes: G06F 16/122 using management policies backup systems G06F11/1446; file migration policies for HSM systems G06F16/185
• CPC Class Codes: G06F 16/134 Distributed indices
• CPC Class Codes: G06F 16/14 Details of searching files based on file metadata
• CPC Class Codes: G06F 16/148 File search processing
• CPC Class Codes: G06F 16/16 File or folder operations, e.g. details of user interfaces specifically adapted to file systems
• CPC Class Codes: G06F 16/1727 Details of free space management performed by the file system saving storage space on storage systems G06F3/0608; management of blocks in storage devices G06F3/064
• CPC Class Codes: G06F 16/1734 Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs
• CPC Class Codes: G06F 16/182 Distributed file systems
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/2228 Indexing structures
• CPC Class Codes: G06F 16/245 Query processing
• CPC Class Codes: G06F 16/24575 using context
• CPC Class Codes: G06F 16/285 : Clustering or classification
• CPC Class Codes: G06F 2201/80 : Database-specific techniques
• CPC Class Codes: G06F 3/0604 : Improving or facilitating administration, e.g. storage management
• CPC Class Codes: G06F 3/0605 : by facilitating the interaction with a user or administrator
• CPC Class Codes: G06F 3/0649 : Lifecycle management
• CPC Class Codes: G06F 3/0685 : Hybrid storage combining heterogeneous device types, e.g. hierarchical storage, hybrid arrays
• CPC Class Codes: Y10S 707/99942 : Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99948 : Application of database or data structure, e.g. distributed, multimedia, or image
• CPC Class Codes: Y10S 707/99955 : Archiving or backup

Abstract

Systems and methods for data classification to facilitate and improve data management within an enterprise are described. The disclosed systems and methods evaluate and define data management operations based on data characteristics rather than data location, among other things. Also provided are methods for generating a data structure of metadata that describes system data and storage operations. This data structure may be consulted to determine changes in system data rather than scanning the data files themselves.

Claims

1. A system for distributing metadata related to data stored in a network, comprising:

a first storage device containing first data accessible via the network;

a second storage device containing second data accessible via the network;

a first metabase containing metadata and having a first characteristic, wherein the metadata includes classifications of the data stored on the first and second storage devices, the classifications including information used to facilitate performance of a data storage operation on the first data or on the second data; and

a second metabase containing metadata and having a second characteristic, wherein the metadata includes classifications of the data stored on the first and second storage devices, the classifications including information used to facilitate performance of a data storage operation on first data or on the second data; and

a metabase manager component in communication with the first metabase and the second metabase over the network, wherein the metabase manager component is programmed to direct requests to perform data storage operations to the first metabase or the second metabase based on the characteristics of the metabases, wherein the metabase manager component directs a request to perform a data storage operation by;

determining the first characteristic of the first metabase and the second characteristic of the second metabase;

evaluating the first and second characteristics against one or more criteria; and

directing the request to perform the data storage operation to the first metabase or the second metabase based on the evaluation.

2. The system of claim 1 wherein the first metabase contains metadata classifying the data stored on the first storage device and the second metabase contains metadata classifying the data stored on the second storage device.

3. The system of claim 1 wherein both the first and second metabases contain copies of metadata classifying the data stored on the first and second storage devices.

4. The system of claim 1, wherein the metabase manager component directs requests to perform data storage operations based at least in part on a past level of activity of the metabases.

5. The system of claim 1 wherein the metabase manager component directs requests to perform data storage operations based at least in part on a current level of activity of the metabases.

6. The system of claim 1 wherein the metabase manager component directs requests to perform data storage operations based at least in part on a projected level of activity of the metabases.

7. The system of claim 1 wherein the metabase manager component directs requests to perform data storage operations based on the data to be accessed by the storage request.

8. The system of claim 1 wherein the metabase manager component directs requests to perform data storage operations based on access control information for the metabases.

9. The system of claim 1 wherein the first and second characteristics of the metabases are associated with a location of the metabases.

10. The system of claim 1 wherein the first and second characteristics of the metabases are associated with a hierarchy of departments within a business organization that stores data to the first and second storage devices.

11. The system of claim 1 wherein the first and second characteristics of the metabases are associated with subsidiaries of a business organization that stores data to the first and second storage devices.

12. The method of claim 1 wherein the metabase manager component determines the first and second characteristics by monitoring the first and second metabases.

13. The method of claim 1 wherein the metabase manager component evaluates the first and second characteristics against one or more criteria relating to availability of the first and second metabases.