Systems and methods for using metadata to enhance data management operations

• US 8,131,680 B2
• Filed: 11/02/2009
• Issued: 03/06/2012
• Est. Priority Date: 11/28/2005
• Status: Expired due to Fees

• Current Assignee: CommVault Systems Incorporated
• Original Assignee: CommVault Systems Incorporated
• Inventors: Prahlad, Anand, Schwartz, Jeremy Alan, Ngo, David, Brockway, Brian, Muller, Marcus S.
• Primary Examiner(s): Trujillo, James
• Assistant Examiner(s): Moser, Bruce M
• Application Number:
  US12/610,931
• Publication Number:
  US 20100114829A1
• Time in Patent Office: 855 Days
• Field of Search: 707/204, 707/999.204, 707/640, 707/648, 707/653
• US Class Current: 707/648
• 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 managing electronic data are disclosed. Various data management operations can be performed based on a metabase formed from metadata. Such metadata can be identified from an index of data interactions generated by a journaling module, and obtained from their associated data objects stored in one or more storage devices. In various embodiments, such processing of the index and storing of the metadata can facilitate, for example, enhanced data management operations, enhanced data identification operations, enhanced storage operations, data classification for organizing and storing the metadata, cataloging of metadata for the stored metadata, and/or user interfaces for managing data. In various embodiments, the metabase can be configured in different ways. For example, the metabase can be stored separately from the data objects so as to allow obtaining of information about the data objects without accessing the data objects or a data structure used by a file system.

Claims

1. A system for managing the transfer of electronic data between a plurality of storage devices, the system comprising:

a first storage device having a plurality of data objects;

a second storage device;

a selected criteria for copying at least one of the plurality of data objects on the first storage device to the second storage device;

at least one metabase having a plurality of records comprising metadata associated with the plurality of data objects;

a classification module executing in one or more computer processors, the classification module configured to evaluate a plurality of entries populated by a journal program, the entries comprising information about interactions between at least one application and the plurality of data objects, the classification module is further configured to automatically tag one or more of the entries that related to information shared among a group of users such that tagged entries exist, the classification module further configured to update the metadata stored in the at least one metabase based on the tagged entries; and

a management module configured migrate a first data object from a first storage location to a second storage device based on the metadata stored in the metabase.

2. The system of claim 1, wherein the management module is further configured to migrate the first data object based on selected criteria, wherein the selected criteria comprises at least one of the group consisting of a schedule policy, a storage policy and a migration policy.

3. The system of claim 1, wherein the management module is further configured to access the metadata stored in the metabase without accessing the first data object stored in the first storage device.

4. The system of claim 1, wherein a file reference number is associated with the first data object.

5. The system of claim 1, wherein the management module stores a path indicative of a location of the first data object on the first storage device.

6. The system of claim 1, wherein the management module is configured to update the metabase to reflect the second location of the first data object on the second storage device.

7. The system of claim 1, wherein the metabase comprises first and second metabases, wherein the first metabase is associated with the first storage device and the second metabase is associated with the second storage device.

8. The system of claim 1, additionally comprising storing on the first storage device reference data that identifies the second location of the first data object on the second storage device.

9. The system of claim 1, wherein the journaling application is different than the at least one application.

10. A method for managing the transfer of electronic data in a storage system, the method comprising:

receiving a plurality of entries identifying information about data interactions with at least one application and a plurality of data objects, the entries being populated by a journaling application that monitors the data interactions;

tagging the entries based on user groups such that tagged entries exist;

updating, based on the tagged entries, metadata stored in a metabase with information about the data interactions associated with the tagged entries; and

migrating a first data object from a first storage location to a second storage device based on the metadata stored in the metabase.

11. The method of claim 10, further comprising migrating the first data object based on selected criteria, wherein the selected criteria comprises at least one of the group consisting of a schedule policy, a storage policy and a migration policy.

12. The method of claim 10, wherein said accessing of the metadata stored in the metabase is performed without accessing the first data object stored in the first storage device.

13. The method of claim 10, further comprising providing a file reference number associated with the first data object.

14. The method of claim 10, further comprising providing a path indicative of a location of the first data object on the first storage device.

15. The method of claim 10, additionally comprising updating the metabase to reflect the second location of the first data object on the second storage device.

16. The method of claim 10, wherein the metabase comprises first and second metabases, wherein the first metabase is associated with the first storage device and the second metabase is associated with the second storage device.

17. The method of claim 10, additionally comprising storing on the first storage device reference data that identifies the second location of the first data object on the second storage device.

18. The method of claim 10, wherein the journaling application is different than the at least one application.