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

• US 8,612,714 B2
• Filed: 09/14/2012
• Issued: 12/17/2013
• Est. Priority Date: 11/28/2005
• Status: Active Grant

• Current Assignee: CommVault Systems Incorporated
• Original Assignee: CommVault Systems Incorporated
• Inventors: Prahlad, Anand, Schwartz, Jeremy A., Ngo, David, Brockway, Brian, Muller, Marcus S.
• Primary Examiner(s): NGUYEN, HIEP T
• Application Number:
  US13/616,197
• Publication Number:
  US 20130013609A1
• Time in Patent Office: 459 Days
• Field of Search: None
• US Class Current: 711/170
• 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 managing storage operations between multiple servers containing instances of a data object, comprising:

a storage operation receiving component that receives a storage request related to the data object;

a metabase component containing metadata that at least identifies one or more locations where instances of the data object can be found, wherein the metadata contains classifications of the data object that identify characteristics of the data object related to performing a storage operation;

a storage manager component that accesses the metadata and determines which of multiple servers should handle the request; and

a storage operation execution component that forwards the storage request to the determined server to handle the request.

2. The system of claim 1 wherein the storage operation receiving component receives requests to read data from a file server.

3. The system of claim 1 wherein the storage operation receiving component receives requests to access data from a web server.

4. The system of claim 1 wherein the metabase component comprises a data classification component that adds one or more data classifications to the metadata, wherein the classifications describe at least some characteristics of the data object not stored with the data object itself.

5. The system of claim 1 wherein the metabase component identifies the one or more locations based on the results of a search for data objects identified in the storage request.

6. The system of claim 1 wherein the storage manager component determines which of multiple servers should handle the request based on one or more criteria received with the storage request.

7. The system of claim 1 wherein the storage manager component determines which of multiple servers should handle the request based on a level of activity of the multiple servers, wherein the level of activity is past, current, or projected.

8. The system of claim 1 wherein the storage manager component determines which of multiple servers should handle the request based on network proximity of each of the multiple servers to the source of the request.

9. The system of claim 1 wherein the storage manager component determines which of multiple servers should handle the request based on a proximity of each of the multiple servers to the data object identified.

10. A method of performing a data storage operation with respect to at least one secondary storage location, the method comprising:

receiving a request to perform a storage operation with respect to the at least one secondary storage location;

determining which of a primary and secondary metabase to access for information related to the storage request, wherein the primary and secondary metabases are not identical;

accessing the determined metabase to obtain information related to the storage request; and

performing the storage request based on the request and the information related to the request.

11. The method of claim 10 wherein the receiving comprises receiving selection criteria for locating one or more data objects.

12. The method of claim 10 wherein the determining is based on a distribution of metadata describing data stored within the secondary storage location.

13. The method of claim 10 wherein the determining is based on a distribution architecture of the primary and secondary metabase.

14. The method of claim 10 wherein the determining is based at least in part on a characteristic of data identified in the storage operation request.

15. The method of claim 10 wherein the determining is based on the availability of the secondary storage location.

16. The method of claim 10 wherein the accessing comprises obtaining parameters for the storage operation.

17. The method of claim 10 wherein the accessing comprises reading a storage policy related to the storage request.

18. The method of claim 10 wherein the received storage request comprises a request to backup or restore data.

19. A method of identifying changed data, comprising:

selecting an entry of a log that journals changes to data and determining if the selected entry refers to data tracked by a data classification system that stores classifications associated with data that describe the manner in which data management operations are performed on data;

if the selected entry refers to data tracked by the data classification system, identifying at least a first change to the data represented by the entry; and

updating the data classification system based on the identified change.

20. A method of finding data objects based on users associated with the data objects, comprising:

receiving a request to identify one or more data objects under the control of a data management system, wherein the request specifies one or more criteria based on a pattern of user interaction with the data objects;

searching a metabase for metadata identifying data objects under the control of the data management system that satisfy the one or more criteria; and

providing the identified data objects in response to the request.