Search Images Maps Play YouTube News Gmail Drive More »
Sign in
Screen reader users: click this link for accessible mode. Accessible mode has the same essential features but works better with your reader.

Patents

  1. Advanced Patent Search
Publication numberUS20060224846 A1
Publication typeApplication
Application numberUS 11/269,512
Publication dateOct 5, 2006
Filing dateNov 7, 2005
Priority dateNov 5, 2004
Also published asCA2583912A1, CA2587055A1, US7472238, US7500053, US7765369, US7809914, US7849266, US7873802, US7958307, US7975061, US8074042, US8112543, US8281028, US8402244, US8443142, US8799613, US20060224852, US20090157881, US20090172319, US20110022814, US20110078295, US20110093672, US20110231606, US20110314120, US20120072695, US20120151014, US20120185657, US20130227239, US20150026401, WO2006052872A2, WO2006052872A3, WO2006053084A2, WO2006053084A3
Publication number11269512, 269512, US 2006/0224846 A1, US 2006/224846 A1, US 20060224846 A1, US 20060224846A1, US 2006224846 A1, US 2006224846A1, US-A1-20060224846, US-A1-2006224846, US2006/0224846A1, US2006/224846A1, US20060224846 A1, US20060224846A1, US2006224846 A1, US2006224846A1
InventorsArun Amarendran, Manoj Vijayan Retnamma
Original AssigneeAmarendran Arun P, Vijayan Retnamma Manoj K
Export CitationBiBTeX, EndNote, RefMan
External Links: USPTO, USPTO Assignment, Espacenet
System and method to support single instance storage operations
US 20060224846 A1
Abstract
Systems and methods for single instance storage operations are provided. Systems constructed in accordance with the principals of the present invention may process data containing a payload and associated metadata. Often, chunks of data are copied to traditional archive storage wherein some or all of the chunk, including the payload and associated metadata are copied to the physical archive storage medium. In some embodiments, chunks of data are designated for storage in single instance storage devices. The system may remove the encapsulation from the chunk and may copy the chunk payload to a single instance storage device. The single instance storage device may return a signature or other identifier for items copied from the chunk payload. The metadata associated with the chunk may be maintained in separate storage and may track the association between the logical identifiers and the signatures for the individual items of the chunk payload which may be generated by the single instance storage device.
Images(6)
Previous page
Next page
Claims(15)
1. A method for performing a storage operation on a computer network comprising:
receiving a request to perform the storage operation on a first set of data;
analyzing the first set of data;
characterizing the first set of data into a first portion and a second portion based on characteristics observed in the analyzing step;
copying the first portion of the data to a first single instance storage location; and
associating an identifier with the first portion of data stored at the first single instance storage location.
2. The method of claim 1 further comprising updating a database associated with a management component of a storage operation cell with the identifier information.
3. The method of claim 1 wherein the copying further comprises routing the first portion of the data to the first single instance storage location via a media agent.
4. The method of claim 1 wherein the second portion of the data is metadata relating to the second portion of data.
5. The method of claim 3 wherein the first portion of the data is payload data.
6. The method of claim 1 wherein the first portion of data is copied to the first single instance location, based at least in part, on the characterization step.
7. The method of claim 6 wherein the first portion of the data is copied item by item to the first single instance storage location.
8. The method of claim 7 further comprising associating an identifier with the first portion of data stored at the first single instance storage location.
9. The method of claim 8 wherein an identifier is associated with the first portion of data stored at the first single instance storage location, the method further comprising correlating the identifier associated with the first portion of data with an identifier associated with the second portion of data.
10. The method of claim 1 wherein the characterization further comprises:
characterizing the first portion of data into first and second sub-portions of data; wherein the first sub-portion of the first portion of data is suitable for single instance storage and the second sub-portion of the first portion is suitable for conventional storage.
11. The method of claim 10 wherein the copying further comprises copying the second sub-portion of the first portion of data to a first storage device.
12. The method of claim 10 wherein the copying further comprises copying the second sub-portion of the first portion of data to a first storage device.
13. The method of claim 10 further comprising:
copying the second sub-portion of the first portion of data to a first storage device;
copying the second sub-portion of the first portion of data to the first storage device; and
updating a database associated with a management component of a storage operation cell to reflect copy operations associated with the data.
14. A method for recreating data stored in a storage network comprising:
receiving a request to retrieve a portion data stored in a storage network;
identifying a location of the of the portion of data, wherein at least some of the portion of data is located in a single instance storage device;
retrieving from the single instance storage device data identified in the identifying step;
consulting the retrieved data to determine whether additional data relating to the retrieved data is available; and
recreating the data portion based, at least in part, on data retrieved from the single instance storage device.
15. The method of claim 16 further comprising retrieving additional data from the single instance storage device if it is determined in the consulting step that additional data relating to the retrieved data is available.
Description
    PRIORITY CLAIM
  • [0001]
    This application claims the benefit of U.S. provisional application No. 60/626,076 titled SYSTEM AND METHOD FOR PERFORMING STORAGE OPERATIONS IN A COMPUTER NETWORK, filed Nov. 8, 2004, and U.S. provisional application No. 60/625,746 titled STORAGE MANAGEMENT SYSTEM filed Nov. 5, 2004, each of which is incorporated herein by reference in its entirety.
  • RELATED APPLICATIONS
  • [0002]
    This application is related to the following patents and pending applications, each of which is hereby incorporated herein by reference in its entirety:
  • [0003]
    application Ser. No. 09/354,058, titled HIERARCHICAL BACKUP AND RETRIEVAL SYSTEM, filed Jul. 15, 1999, attorney docket number 4982/5;
  • [0004]
    U.S. Pat. No. 6,418,478, titled PIPELINED HIGH SPEED DATA TRANSFER MECHANISM, issued Jul. 9, 2002, attorney docket number 4982/6;
  • [0005]
    application Ser. No. 60/460,234, SYSTEM AND METHOD FOR PERFORMING STORAGE OPERATIONS IN A COMPUTER NETWORK, filed Apr. 3, 2003, attorney docket number 4982/35;
  • [0006]
    application Ser. No. 60/482,305, HIERARCHICAL SYSTEM AND METHOD FOR PERFORMING STORAGE OPERATIONS IN A COMPUTER NETWORK, filed Jun. 25, 2003, attorney docket number 4982/39;
  • [0007]
    Application Ser. No. 60/519,526, SYSTEM AND METHOD FOR PERFORMING PIPELINED STORAGE OPERATIONS IN A COMPUTER NETWORK, filed Nov. 13, 2003, attorney docket number 4982/46P;
  • [0008]
    application Ser. No. 10/803,542, METHOD AND SYSTEM FOR TRANSFERRING DATA IN A STORAGE OPERATION, filed Mar. 18, 2004, attorney docket number 4982/49;
  • [0009]
    Application Serial Number to be assigned, titled SYSTEM AND METHOD FOR PERFORMING MULTISTREAM STORAGE OPERATIONS, filed Nov. 7, 2005, attorney docket number 4982-59;
  • [0010]
    Application Serial Number to be assigned, titled METHOD AND SYSTEM OF POOLING STORAGE DEVICES, filed Nov. 7, 2005, attorney docket number 4982-61;
  • [0011]
    Application Serial Number to be assigned, titled METHOD AND SYSTEM FOR SELECTIVELY DELETING STORED DATA, filed Nov. 7, 2005, attorney docket number 4982-67;
  • [0012]
    Application Serial Number to be assigned, titled METHOD AND SYSTEM FOR GROUPING STORAGE SYSTEM COMPONENTS, filed Nov. 7, 2005, attorney docket number 4982-69;
  • [0013]
    Application Serial Number to be assigned, titled SYSTEMS AND METHODS FOR RECOVERING ELECTRONIC INFORMATION FROM A STORAGE MEDIUM, filed Nov. 7, 2005, attorney docket number 4982-68; and
  • [0014]
    Application Serial Number to be assigned, titled METHOD AND SYSTEM FOR MONITORING A STORAGE NETWORK, filed Nov. 7, 2005, attorney docket number 4982-66.
  • COPYRIGHT NOTICE
  • [0015]
    A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever.
  • BACKGROUND OF THE INVENTION
  • [0016]
    The invention disclosed herein relates generally to performing storage operations in a computer network. More particularly, the present invention relates to systems and methods for supporting single instance storage devices in a computer network.
  • [0017]
    Storage of electronic data has evolved through many forms. During the early development of the computer, storage of data was limited to individual computers. Electronic data was stored in the Random Access Memory (RAM) or some other storage medium such as a hard drive or tape drive that was an actual part of the individual computer.
  • [0018]
    Later, with the advent of networked computing, storage of electronic data gradually migrated from the individual computer to stand-alone storage devices and other storage devices accessible via a network, for example a tape library accessible via a network server or other computing device. These network storage devices soon evolved in the form of networked tape drives, libraries, optical libraries, Redundant Arrays of Inexpensive Disks (RAID), CD-ROM jukeboxes, and other devices. System administrators often use network storage devices to perform storage operations and make backup copies and other copies of data stored on individual client computers in order to preserve data against accidental loss, corruption, physical damage, and other risks.
  • [0019]
    Storage systems evolved to handle increasingly complex storage operations and increasingly large volumes of data. For example, some storage management systems began organizing system components and system resources into logical groupings and hierarchies such as storage operation cells of the CommVault QiNetix storage management system, available from CommVault Systems, Inc. of Oceanport, N.J., and as further described as further described in Application Ser. No. 60/482,305 and application Ser. No. 09/354,058 which are hereby incorporated by reference in their entirety.
  • [0020]
    Another factor contributing to increasingly large volumes of data is storage of multiple copies of the same file or data item. For example, a large enterprise might have several hundred users each keeping a copy of the same e-mail attachment. Alternatively, individual users may also lose track of or otherwise retain several copies of a file on their own personal hard drive or network share. Thus, storage space on systems is being wasted by multiple instances of the same data.
  • [0021]
    To address this problem, companies have developed storage devices that support single instance storage. Data items copies to a single instance storage device are processed to determine a unique signature for each file. Thus, copies or instances of the same file will generate the same unique signature. One well known technique for generating such a signature is generating a cryptographic hash of the file or other similar checksum based on the file contents. Storage devices can then compare the signature for a file to be stored with a list of previously stored signatures to determine whether a copy of the file already exists in storage and thus the file need not be copied again. Some storage systems also use content addressable storage (“CAS”) in single instance storage devices in which the signature or hash of the file is also used as the address of the file in the storage device.
  • [0022]
    One problem associated with single instance storage solutions is that they are not designed to process backup data stored as chunks. When a copy of a production data store or other large volume of data is made, the data is often divided into a number of smaller parts for easier transmission to archive media via the network. These smaller parts typically become encapsulated as the payload for chunks of data which include metadata, such as tag headers and footers as previously described in U.S. application Ser. No. 10/803,542 and U.S. Pat. No. 6,418,478 each of which is hereby incorporated by reference in its entirety, and the chunks of data are sent over the network to the archive storage. For example, each chunk may contain a payload of several thousand files from a larger data store containing hundreds of thousands of files with each file or item having a logical identifier such as a filename. Metadata for each chunk describing the contents of the payload (logical identifiers, etc.) and other information may be stored along with the payload data as further described herein. In addition, the metadata from each chunk may be used by system components to track the content of the payload of each chunk and also contains storage preferences and other information useful for performing storage operations.
  • [0023]
    Each chunk of data, however, usually contains different metadata. Thus, two instances of the same file will likely be encapsulated by different metadata in two different chunks eve if the payload of the two chunks is the same. Similarly, current single instance storage systems would generate different signatures for each chunk of data and therefore store a different copy of each chunk of data even though the payload of each chunk is the same.
  • BRIEF SUMMARY OF THE INVENTION
  • [0024]
    Systems and methods for single instance storage operations are provided. Systems constructed in accordance with the principals of the present invention may process data containing a payload and associated metadata. Often, chunks of data are copied to traditional archive storage wherein some or all of the chunk, including the payload and associated metadata are copied to the physical archive storage medium. In some embodiments, chunks of data are designated for storage in single instance storage devices. The system may remove the encapsulation from the chunk and may copy the chunk payload to a single instance storage device. The single instance storage device may return a signature or other identifier for items copied from the chunk payload. The metadata associated with the chunk may be maintained in separate storage and may track the association between the logical identifiers and the signatures for the individual items of the chunk payload which may be generated by the single instance storage device.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • [0025]
    The invention is illustrated in the figures of the accompanying drawings which are meant to be exemplary and not limiting, in which like references are intended to refer to like or corresponding parts, and in which:
  • [0026]
    FIG. 1 is a block diagram of a storage operation cell in a system to perform storage operations on electronic data in a computer network according to an embodiment of the invention;
  • [0027]
    FIG. 2 is a block diagram of a hierarchically organized group of storage operation cells in a system to perform storage operations on electronic data in a computer network according to an embodiment of the invention;
  • [0028]
    FIG. 3 is a block diagram of a hierarchically organized group of storage operation cells in a system to perform storage operations on electronic data in a computer network according to an embodiment of the invention;
  • [0029]
    FIG. 4 is a flow diagram of a method to store chunks of data in a single instance storage device.
  • [0030]
    FIG. 5 is a flow diagram of a method for retrieving chunk payload data from a single instance storage device.
  • DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
  • [0031]
    With reference to FIGS. 1 through 5, embodiments of the invention are presented. Systems and methods are presented for performing multi-stream storage operations including multi-stream storage operations associated with a single sub-client.
  • [0032]
    FIG. 1 presents a block diagram of a storage operation cell in a system to perform storage operations on electronic data in a computer network according to an embodiment of the invention. As shown, the storage operation cell may include a storage management component, such as storage manager 100 and one or more of the following: a client 85, a data store 90, a data agent 95, a media management component, such as a media agent 125, a media management component index cache 130, a storage device 135, a storage management component index cache 105, a jobs agent 110, an interface module 115, and a management agent 120. The system and elements thereof are exemplary of a modular storage management system such as the CommVault QiNetix storage management system, available from CommVault Systems, Inc. of Oceanport, N.J., and further described in application Ser. No. 09/610,738 which is incorporated herein by reference in its entirety.
  • [0033]
    A storage operation cell generally includes combinations of hardware and software components directed to performing storage operations on electronic data. Exemplary storage operation cells according to embodiments of the invention include CommCells as embodied in the QNet storage management system and the QiNetix storage management system by CommVault Systems of Oceanport, N.J., and as further described in Application Ser. No. 60/482,305 and application Ser. No. 09/354,058 which are hereby incorporated by reference in their entirety.
  • [0034]
    According to some embodiments of the invention, storage operations cells are related to backup cells and provide all of the functionality of backup cells as further described in application Ser. No. 09/354,058. Storage operation cells also perform additional types of storage operations and provide other types of storage management functionality. According to embodiments of the invention, storage operation cells perform storage operations which also include, but are not limited to, creation, storage, retrieval, migration, deletion, and tracking of primary or production volume data, secondary volume data, primary copies, secondary copies, auxiliary copies, snapshot copies, backup copies, incremental copies, differential copies, HSM copies, archive copies, Information Lifecycle Management (“ILM”) copies, and other types of copies and versions of electronic data. In some embodiments, storage operation cells also provide an integrated management console for users or system processes to interface with to perform storage operations on electronic data as further described herein.
  • [0035]
    A storage operation cell can be organized and associated with other storage operation cells forming a logical hierarchy among various components of a storage management system as further described herein. Storage operation cells generally include a storage manager 100, and, according to some embodiments, one or more other components including, but not limited to, a client computer 85, a data agent 95, a media management component 125, a storage device 135, and other components as further described herein.
  • [0036]
    For example, a storage operation cell may contain a data agent 95 which is generally a software module that is generally responsible for performing storage operations related to client computer 85 data stored in an data store 90 or other memory location, for example archiving, migrating, and recovering client computer data. In some embodiments, a data agent performs storage operations in accordance with one or more storage policies or other preferences. A storage policy is generally a data structure or other information that may include a set of preferences and other storage criteria for performing a storage operation. The preferences and storage criteria may include, but are not limited to: a storage location, relationships between system components, network pathway to utilize, retention policies, data characteristics, compression or encryption requirements, preferred system components to utilize in a storage operation, and other criteria relating to a storage operation. As further described herein, storage policies may be stored to a storage manager index, to archive media as metadata for use in restore operations or other storage operations, or to other locations or components of the system.
  • [0037]
    Each client computer 85 generally has at least one data agent 95 and the system can support many client computers 85. The system also generally provides a plurality of data agents 95 each of which is intended to perform storage operations related to data associated with a different application, for example to backup, migrate, and recover application specific data. For example, different individual data agents 95 may be designed to handle Microsoft Exchange data, Lotus Notes data, Microsoft Windows 2000 file system data, Microsoft Active Directory Objects data, and other types of data known in the art.
  • [0038]
    If a client computer 85 has two or more types of data, one data agent 95 is generally required for each data type to perform storage operations related to client computer 85 data. For example, to backup, migrate, and restore all of the data on a Microsoft Exchange 2000 server, the client computer 85 would use one Microsoft Exchange 2000 Mailbox data agent 95 to backup the Exchange 2000 mailboxes, one Microsoft Exchange 2000 Database data agent 95 to backup the Exchange 2000 databases, one Microsoft Exchange 2000 Public Folder data agent 95 to backup the Exchange 2000 Public Folders, and one Microsoft Windows 2000 File System data agent 95 to backup the client computer's 85 file system. These data agents 95 would be treated as four separate data agents 95 by the system even though they reside on the same client computer 85. In some embodiments, separate data agents may be combined to form a virtual data agent (not shown) for performing storage operations related to a specific application. Thus, the four separate data agents of the previous example could be combined as a virtual data agent suitable for performing storage operations related to all types of Microsoft Exchange 2000 and/or Windows 2000 data.
  • [0039]
    The storage manager 100 is generally a software module or application that coordinates and controls storage operations performed by the storage operation cell. The storage manager 100 communicates with all elements of the storage operation cell including client computers 85, data agents 95, media management components 125, and storage devices 135 regarding storage operations, for example to initiate and manage system backups, migrations, and recoveries. The storage manager 100 also communicates with other storage operation cells as further described herein.
  • [0040]
    The storage manager 100 includes a jobs agent 110 software module which monitors the status of all storage operations that have been performed, that are being performed, or that are scheduled to be performed by the storage operation cell. The jobs agent 110 is communicatively coupled with an interface agent 115 software module. The interface agent 115 provides presentation logic, such as a graphical user interface (“GUI”), an application program interface (“API), or other interface by which users and system processes can retrieve information about the status of storage operations and issue instructions to the storage operations cell regarding performance of storage operations as further described herein. For example, a user might modify the schedule of a number of pending snapshot copies or other types of copies. As another example, a user might use the GUI to view the status of all storage operations currently pending in all storage operation cells or the status of particular components in a storage operation cell.
  • [0041]
    The storage manager 100 also includes a management agent 120 software module. The management agent 120 generally provides an interface with other management components 100 in other storage operations cells through which information and instructions regarding storage operations may be conveyed. For example, in some embodiments as further described herein, a management agent 120 in first storage operation cell can communicate with a management agent 120 in a second storage operation cell regarding the status of storage operations in the second storage operation cell. In some embodiments, a management agent 120 in first storage operation cell can communicate with a management agent 120 in a second storage operation cell to control the storage manager 100 (and other components) of the second storage operation cell via the management agent 120 contained in the storage manager 100 for the second storage operation cell. In other embodiments, the management agent 120 in the first storage operation cell communicates directly with and controls the components in the second storage management cell and bypasses the storage manager 100 in the second storage management cell. Storage operation cells can thus be organized hierarchically among cells and as further described herein.
  • [0042]
    A media management component 125 is generally a software module that conducts data, as directed by a storage manager 100, between client computers 85 and one or more storage devices 135. The media management component 125 is communicatively coupled with and generally configured to control one or more storage devices 135. For example, the media management component 125 might instruct a storage device 135 to use a robotic arm or other means to load or eject a media cartridge, and to archive, migrate, or restore application specific data. The media management component 125 generally communicates with storage devices 135 via a local bus such as a SCSI adaptor. In some embodiments, the storage device 135 is communicatively coupled to the media management component 125 via a Storage Area Network (“SAN”).
  • [0043]
    Each media management component 125 maintains an index cache 130 which stores index data the system generates during storage operations as further described herein. For example, storage operations for Microsoft Exchange data generate index data. Index data may include, for example, information regarding the location of the stored data on a particular media, information regarding the content of the data stored such as file names, sizes, creation dates, formats, application types, and other file-related criteria, information regarding one or more clients associated with the data stored, information regarding one or more storage policies, storage criteria, or storage preferences associated with the data stored, compression information, retention-related information, encryption-related information, stream-related information, and other types of information. Index data thus provides the system with an efficient mechanism for performing storage operations including locating user files for recovery operations and for managing and tracking stored data. The system generally maintains two copies of the index data regarding particular stored data. A first copy is generally stored with the data copied to a storage device 135. Thus, a tape may contain the stored data as well as index information related to the stored data. In the event of a system restore, the index data stored with the stored data can be used to rebuild a media management component index 130 or other index useful in performing and/or managing storage operations. In addition, the media management component 125 that controls the storage operation also may generally write an additional copy of the index data to its index cache 130. The data in the media management component index cache 130 is generally stored on faster media, such as magnetic media, and is thus readily available to the system for use in storage operations and other activities without having to be first retrieved from the storage device 135.
  • [0044]
    The storage manager 100 may also maintain an index cache 105. Storage manager index data may be, among other things, used to indicate, track, and associate logical relationships and associations between components of the system, user preferences, management tasks, and other useful data. For example, the storage manager 100 might use its index cache 105 to track logical associations between media management components 125 and storage devices 135. The storage manager 100 may also use index cache 105 to track the status of storage operations to be performed, storage patterns associated with the system components such as media use, storage growth, network bandwidth, service level agreement (“SLA”) compliance levels, data protection levels, storage policy information, storage criteria associated with user preferences, retention criteria, storage operation preferences, and other storage-related information. Index caches 105 and 130 typically reside on their corresponding storage component's hard disk or other fixed storage device.
  • [0045]
    For example, jobs agent 110 of a storage manager component 100 may retrieve storage manager index 105 data regarding a storage policy and storage operation to be performed or scheduled for a particular client 85. The jobs agent 110, either directly or via the interface module 115, communicates with the data agent 95 at the client 85 regarding the storage operation. In some embodiments, the jobs agent 110 also retrieves from index cache 105 a storage policy associated with client 85 and uses information from the storage policy to communicate to data agent 95 one or more media management components 125 associated with performing storage operations for that particular client 85 as well as other information regarding the storage operation to be performed such as retention criteria, encryption criteria, streaming criteria, etc. Data agent may 95 then package or otherwise manipulate client data stored in client data store 90 in accordance with the storage policy information and/or according to a user preference, and may communicate this client data to the appropriate media management component(s) 125 for processing. Media management component(s) 125 may store the data according to storage preferences associated with the storage policy including storing the generated index data with the stored data, as well as storing a copy of the generated index data in the media management component index cache 130.
  • [0046]
    In some embodiments, components of the system may reside and execute on the same computer. In some embodiments, a client computer 85 component such as a data agent 95, a media management component 125, or a storage manager 100 coordinates and directs storage operations as further described in application Ser. No. 09/610,738. This client computer 85 component can function independently or together with other similar client computer 85 components.
  • [0047]
    FIG. 2 presents a block diagram of a hierarchically organized group of storage operation cells in a system to perform storage operations on electronic data in a computer network according to an embodiment of the invention. As shown, the system may include a master storage manager component 140, a first storage operation cell 145, a second storage operation cell 150, a third storage operation cell 155, a fourth storage operation cell 160, a fifth storage operation cell 165, and an nth storage operation cell 170.
  • [0048]
    As previously described, storage operation cells are often communicatively coupled and hierarchically organized. For example, as shown in FIG. 2, a master storage manager 140 is associated with, communicates with, and directs storage operations for a first storage operation cell 145, a second storage operation cell 150, a third storage operation cell 155, a fourth storage operation cell 160, a fifth storage operation cell 165, and an nth storage operation cell 170. In some embodiments, the master storage manager 140 is not part of any particular storage operation cell. In other embodiments (not shown), the master storage manager 140 may itself be part of a storage operation cell.
  • [0049]
    Thus, the master storage manager 140 communicates with the manager agent of the storage manager of the first storage operation cell 145 (or directly with the other components of the first cell 145) regarding storage operations performed in the first storage operation cell 145. For example, in some embodiments, the master storage manager 140 instructs the first storage operation cell 145 how and when to perform storage operations including the type of operation to perform and the data on which to perform the operation.
  • [0050]
    In other embodiments, the master storage manager 140 tracks the status of its associated storage operation cells, such as the status of jobs, system components, system resources, and other items, by communicating with manager agents (or other components) in the respective storage operation cells. In other embodiments, the master storage manager 140 tracks the status of its associated storage operation cells by receiving periodic status updates from the manager agents (or other components) in the respective cells regarding jobs, system components, system resources, and other items. For example, in some embodiments, the master storage manager 140 uses methods to monitor network resources such as mapping network pathways and topologies to, among other things, physically monitor storage operations and suggest alternate routes for storing data as further described herein. The master storage manager 140 also uses methods to monitor primary and secondary storage trends, storage status, media usage, data protection levels, and other storage-related information as further described herein.
  • [0051]
    In some embodiments, the master storage manager 140 stores status information and other information regarding its associated storage operation cells and the system in an index cache or other data structure accessible to the master storage manager 140. In some embodiments, as further described herein, the presentation interface of the master storage manager 140 accesses this information to present users and system processes with information regarding the status of storage operations, storage operation cells, system components, and other information of the system.
  • [0052]
    Storage operation cells may thus be organized hierarchically. Consequently, storage operation cells may inherit properties from “parent” or hierarchically superior cells or be controlled by other storage operation cells in the hierarchy. Thus, in some embodiments as shown in FIG. 2, the second storage operation cell 150 controls or is otherwise superior to the third storage operation cell 155, the fourth storage operation cell 160, the fifth storage operation cell 165, and the nth storage operation cell 170. Similarly, the fourth storage operation cell 160 controls the fifth storage operation cell 165, and the nth storage operation cell 170.
  • [0053]
    Storage operation cells may also be organized hierarchically according to criteria such as function (e.g., superior or subordinate), geography, architectural considerations, or other factors useful in performing storage operations. For example, in one embodiment storage operation cells are organized according to types of storage operations: the first storage operation cell 145 may be directed to performing snapshot copies of primary copy data, and the second storage operation cell 150 may be directed to performing backup copies of primary copy data or other data. In another embodiment, the first storage operation cell 145 may represent a geographic segment of an enterprise, such as a Chicago office, and a second storage operation cell 150 represents a different geographic segment, such as a New York office. In this example, the second storage operation cell 150, the third storage operation cell 155, the fourth storage operation cell 160, the fifth storage operation cell 165, and the nth storage operation cell 170 could represent departments within the New York office. Alternatively, these storage operation cells could be further divided by function performing various types of copies for the New York office or load balancing storage operations for the New York office.
  • [0054]
    In some embodiments, hierarchical organization of storage operation cells may facilitate, among other things, system security and other considerations. For example, in some embodiments, only authorized users are allowed to access or control certain storage operation cells. For example, a network administrator for an enterprise might have access to all storage operation cells including the master storage manager 140. But a network administrator for only the New York office, according to a previous example, might only satisfy access criteria to have access to the second storage operation cell 150, the third storage operation cell 155, the fourth storage operation cell 160, the fifth storage operation cell 165, and the nth storage operation cell 170 which comprise the New York office storage management system.
  • [0055]
    In some embodiments, hierarchical organization of storage operation cells facilitates storage management planning and decision-making. For example, in some embodiments, a user of the master storage manager 140 can view the status of all jobs in the associated storage operation cells of the system as well as the status of each component in every storage operation cell of the system. The user can then plan and make decisions based on this global data. For example, the user can view high-level report of summary information regarding storage operations for the entire system, such as job completion status, component availability status, resource usage status (such as network pathways, etc.), and other information. The user can also drill down through menus or use other means to obtain more detailed information regarding a particular storage operation cell or group of storage operation cells.
  • [0056]
    In other embodiments, the master storage manager 140 may alert a user or system administrator when a particular resource is unavailable (e.g., temporary or permanent) or congested. A storage device may be full or require additional media. Alternatively, a storage manager in a particular storage operation cell may be unavailable due to hardware failure, software problems, or other reasons. In some embodiments, the master storage manager 140 (or another storage manager within the hierarchy of storage operation cells) may utilize the global data regarding its associated storage operation cells at its disposal to suggest solutions to such problems when they occur or even before they occur. For example, the master storage manager 140 might alert the user that a storage device in a particular storage operation cell was full or otherwise congested, and then suggest, based on job and data storage information contained in its index cache, an alternate storage device.
  • [0057]
    As another example, in some embodiments the master storage manager 140 (or other network storage manager) contains programming directed to analyzing the storage patterns and resources of its associated storage operation cells and which suggests optimal or alternate methods of performing storage operations. Thus, for example, the master storage manager 140 may analyze traffic patterns to determine that snapshot data should be sent via a different network segment or to a different storage operation cell or storage device. In some embodiments, users can direct specific queries to the master storage manager 140 regarding predicting storage operations or regarding storage operation information.
  • [0058]
    FIG. 3 presents a block diagram of a hierarchically organized group of storage operation cells in a system to perform storage operations on electronic data in a computer network according to an embodiment of the invention. As shown, FIG. 3 includes a first storage operation cell 175, a second storage operation cell 180, a third storage operation cell 185, a client 190 in communication with a primary volume 195 storing production or other “live” data, a storage manager component 200 in communication with a storage manager index data store 205, a media management component 210 in communication with a media management component index 215 a secondary storage device or volume 220, and a master storage manager component 225 in communication with a master storage manager index data store 230.
  • [0059]
    According to an embodiment of the invention, the first storage operation cell 175 may be directed to a particular type storage operation, such as SRM storage operations. For example, the first storage operation cell 175 monitors and performs SRM-related calculations and operations associated with primary volume 195 data. Thus, the first storage operation cell 175 includes a client component 190 in communication with a primary volume 195 storing data. For example, the client 190 may be directed to using Exchange data, SQL data, Oracle data, or other types of production data used in business applications or other applications and stored in primary volume 195. Storage manager component 200 in cell 175 contains SRM modules or other logic directed to monitoring or otherwise interacting with attributes, characteristics, metrics, and other information associated with the data stored in primary volume 195. Storage manager 200 tracks and stores this information and other information in storage manager index 205. For example, in some embodiments, storage manager component 200 tracks the amount of available space and other similar characteristics of data associated with primary volume 195. In some embodiments, as further described herein, storage manager component 200 may also issue alerts or take other actions when the information associated with primary volume 195 satisfies certain criteria, such as alert criteria.
  • [0060]
    The second storage operation cell 180 may be directed to another type storage operation, such as HSM storage operations. For example, the second storage operation cell 180 may perform backups, migrations, snapshots, or other types of HSM-related operations known in the art. For example, in some embodiments, data is migrated from faster and more expensive storage such as magnetic storage to less expensive storage such as tape storage.
  • [0061]
    In some embodiments, storage operation cells may also contain logical groupings of the same physical devices. Thus, the second storage operation cell 180 includes the client component 190 in communication with the primary volume 195 storing data, and client component 190 and primary volume 195 in the second storage operation cell 180 are the same physical devices as the client component 190 and primary volume 195 in the first storage operation cell 175. Similarly, in some embodiments, the storage manager component 200 and index 205 in the second storage operation cell 180 are the same physical devices as the storage manager component and index in the first storage operation cell 175. The storage manager component 200, however, also contains HSM modules or other logic associated with the second storage operation cell 180 directed to performing HSM storage operations on primary volume 195 data.
  • [0062]
    The second storage operation cell 180 therefore also contains a media management component 210, a media management component index 215, and a secondary storage volume 220 directed to performing HSM-related operations on primary copy data. For example, storage manager 200 migrates primary copy data from primary volume 195 to secondary volume 220 using media management component 210. Storage manager 200 also tracks and stores information associated with primary copy migration and other similar HSM-related operations in storage manager index 205. For example, in some embodiments, storage manager component 200 directs HSM storage operations on primary copy data according to according to a storage policy associated with the primary copy 195 and stored in the index 205. In some embodiments, storage manager 200 also tracks where primary copy information is stored, for example in secondary storage 220.
  • [0063]
    The third storage operation cell 185 contains a master storage manager 225 and a master storage manager index 230. In some embodiments (not shown), additional storage operation cells might be hierarchically located between the third storage operation cell 185 and the first storage operation cell 175 or the second storage operation cell 180. In some embodiments, additional storage operation cells hierarchically superior to the third storage operation cell 185 may also be present in the hierarchy of storage operation cells.
  • [0064]
    In some embodiments, the third storage operation cell 185 is also generally directed to performing a type of storage operation, such as integration of SRM and HSM data from other storage operation cells, such as the first storage operation cell 175 and the second storage operation cell 180. In other embodiments, the third storage operation cell 185 also performs other types of storage operations and might also be directed to HSM, SRM, or other types of storage operations. In some embodiments, the master storage manager 225 of the third storage operation cell 185 aggregates and processes network and storage-related data provided by other manager components 200 in other storage operation cells 175 and 180 in order to provide, among other information, reporting information regarding particular cells, groups of cell, or the system as a whole.
  • [0065]
    FIG. 4 presents a flow diagram of a method to store chunks of data in a single instance storage device. The system may receive or generate an instruction to copy one or more chunks of data to a single instance storage device, step 235. For example, the system may receive a message to copy twenty chunks of archive data comprising a client e-mail data store containing thousands of files in each chunk. As discussed, each chunk of data may contain payload information representing the data items from the client data store as well as metadata describing the contents of each chunk, storage preferences associated with each chunk, associations between chunks, etc.
  • [0066]
    The chunk metadata may be separated from the chunk payload at step 240. For example, data pipe modules as further described herein may unencapsulate the chunk to extract payload information or otherwise process the chunk to separate the chunk metadata from the chunk payload. The chunk metadata may be copied to a data store, for example a storage management component index or a media management component index, and associated with the chunk payload to be stored in the single instance storage device as further described herein (step 245). In some embodiments, the chunk metadata may also be copied to a single instance storage device, but be logically or physically separated (e.g., maintained as a separate container or data item from the chunk payload). Thus, the chunk payload may be saved as a single instance while the metadata can still be preserved.
  • [0067]
    Separation of metadata from payload data may be performed in a number of ways. For example, a data agent residing on a client may separate the chunk metadata from the payload data and transmit each portion to a single instance storage device either separately or together to one or more destinations. This may also involve, as described herein, transmitting metadata and payload data to different logical or physical locations, with the appropriate update of management components or indicies to maintain correlation between the payload data and the metadata. Other arrangements may include one or more a media agents examining or analyzing chunks to be transmitted and separating metadata from payload data at the client or sub-client based on direction from a media agent, or such separation may occur while the chunk is substantially in transit, with the media agents routing the payload to one location and the metadata to another. Moreover, such separation may occur at the storage device(s) with certain metadata and/or payload data tagged or otherwise deemed suitable for single instance storage and separated, for example, while queued at the storage device, whereas other metadata and payload data, not suitable for single instance storage, may be stored elsewhere.
  • [0068]
    Items from the chunk payload may be copied on an item-by-item basis to the single instance storage device at step 250. Thus, the chunk payload may contain several thousand e-mail messages and attachments, each of which is copied to the single instance storage device for storage. The single instance storage device may generate a suitable identifier, such as a signature, a cryptographic hash, or other identifier, for each item, and store each item as appropriate according to its identifier (e.g., items previously stored are generally not stored again and may simple be overwritten, new items for which identifiers do not already exist on an index, map, or other tracking means are stored, etc.). The identifier may be communicated for each item to a system component, such as a storage management component or a media management component, responsible for maintaining the index data containing the metadata associated with the chunk payload (step 255).
  • [0069]
    In some embodiments, however, certain sections of payload data may not be suitable for single instance storage. In this case, such data may be separated from the other chunk data and stored using conventional means. Thus, single instance data and other data from the chunk may be stored in logically or physically separate locations. This allows at least certain portions of chunk data to be stored using single instance storage techniques. A data index, database or other management component may keep track of the various locations to facilitate subsequent restore or copy operations.
  • [0070]
    The identifier returned for each item from the single instance storage device may be associated with the identifier for the item maintained in the metadata associated with the chunk (step 260). For example, chunk metadata generally tracks the contents of the payload of each chunk on an item by item basis. A chunk containing a payload of 1000 e-mail messages and attachments may contain metadata identifying the 1000 items of the payload, for example by file name, message index ID, or other identifier. Thus, the chunk metadata may maintain logical identifiers such as file system identifiers or other identifiers corresponding to each item stored in the chunk payload.
  • [0071]
    When single instance storage identifiers are returned for each item processed and stored by the single instance storage device, the single instance identifiers are associated with the logical identifiers previously maintained in the chunk metadata. Thus, a map or other index structure may be created and maintained in the copy of metadata associated with the chunk payload items stored in single instance storage that correlates single instance storage identifiers or physical storage identifiers with the logical identifiers maintained in the original chunk metadata prior to single instance storage. For example, the original chunk metadata may contain separate entries for a File A and a File B which are actually instances of the same copy of data, for example of the same e-mail attachment. When File A and File B are processed by the single instance storage device, they may each generate the same single instance storage identifier, such as a hash or signature, and the single instance storage device would know to only store one copy or instance of the data. Nevertheless, the single instance storage device would still return an identifier for each file. Thus, when File A was sent to the single instance storage device, its signature would be returned and associated with File A in the chunk metadata. Similarly, when File B was sent to the single instance storage device, the same signature would be returned, but this time associated with File B in the chunk metadata. This arrangement allows the single instance of the attachment to be referenced by both files rather than storing two instances of the same attachment.
  • [0072]
    Thus, the chunk metadata can still be used to recreate the original chunk of data or to retrieve various files from the chunk according to the original chunk metadata. For example, a user or other system component could be presented with a logical view of the chunk by recreating a representation of the chunk contents using the chunk metadata. Thus, although only 600 of 1000 files might be stored in single instance storage due to multiple instances of data, etc., the system could still present a logical view of the chunk containing 1000 files (including, for example the same instances of data with different file names, etc.). If a user wanted to retrieve a file, as further described herein, the system may use the map correlating logical identifiers of the original chunk metadata/payload with single instance storage identifiers to retrieve the requested item from single instance storage. Similarly, users can also browse or otherwise navigate or interact with items in the single instance storage device to view items actually stored, etc. For example, a user might wish to interact with contents of a chunk payload containing 1000 files which would normally use 1000 MB of storage space on non-single instanced storage and only occupies 500 MB on single instanced storage.
  • [0073]
    In this case, the user may perform storage operations regarding each of the 1000 files according to the 1000 logical identifiers maintained by the chunk metadata, determine that the 1000 files are only costing the system 500 MB in terms of storage (due to their storage on single instance storage), understand that the 1000 files are stored as 500 files, for example, on the single instance storage device, and also understand that the 1000 files would require 1000 MB of storage space on non-single instanced storage.
  • [0074]
    In some embodiments, the system may also support cross-referencing between copies of metadata regarding different chunks (step 265). For example, the system may cross-reference single instance storage identifiers to identify duplications among items contained in a plurality of chunks of data in order to more accurately provide storage-related information and perform storage operations. For example, the system may track on a system-wide level across all chunks how much data is stored as multiple instances, etc.
  • [0075]
    FIG. 5 presents a flow diagram of a method for retrieving chunk payload data from a single instance storage device. At step 335, the system may receive or generate a request to retrieve data from single instance storage. For example, the system may receive a request to migrate the payload of a chunk to less expensive storage media such as tape media.
  • [0076]
    At step 340, the logical identifier of the first item of the chunk payload as identified by the metadata may be correlated to its corresponding single instance storage identifier. This item may be requested from the single instance storage device using its single instance storage identifier. For example, an item as originally contained in the chunk payload may have been described in the chunk metadata as File A whereas File A may be associated with a single instance storage signature of 207778627604938. To restore File A, the system may request the item having this storage signature from the single instance storage device. Other files in the chunk payload may also have the same single instance identifier, but will likely have different logical identifiers in the chunk metadata. Thus, each item may be retrieved from the single instance storage device using its single instance storage identifier and then reassociated in a new chunk with its previous logical identifier as further described herein (step 345).
  • [0077]
    At step 350, the system may consult the chunk metadata to determine whether additional items remain in the original payload of the chunk. If additional items remain, the system may return to step 340 and the next item logically identified by the chunk metadata is retrieved from the single instance storage device using its single instance storage identifier and then reassociated with it previous logical identifier. When no further items remain to be retrieved from the single instance storage device, the system finishes recreating the chunk by encapsulating all of the items retrieved with the appropriate chunk metadata (step 355), and copies the new copy of the original chunk to the desired storage location (step 360).
  • [0078]
    In some embodiments, the chunk may be recreated on an item by item basis as items are returned from the single instance storage device. In other embodiments, items are first returned to a buffer or other temporary storage location until all items are returned and then the chunk is recreated. Thus, the new copy of the chunk is generally an exact copy of the chunk before it was stored in single instance storage, yet the metadata regarding the chunk is preserved for use in future storage operations.
  • [0079]
    Systems and modules described herein may comprise software, firmware, hardware, or any combination(s) of software, firmware, hardware, or other means suitable for the purposes described herein. Software and other modules may reside on servers, workstations, personal computers, computerized tablets, PDAs, and other devices suitable for the purposes described herein. Software and other modules may be accessible via local memory, via a network, via a browser or other application in an ASP context, or via other means suitable for the purposes described herein. Data structures described herein may comprise computer files, variables, programming arrays, programming structures, or any electronic information storage schemes, methods, or means, or any combinations thereof, suitable for the purposes described herein. User interface elements described herein may comprise elements from graphical user interfaces, command line interfaces, physical interfaces, and other interfaces suitable for the purposes described herein. Screenshots presented and described herein can be displayed differently as known in the art to generally input, access, change, manipulate, modify, alter, and work with information.
  • [0080]
    While the invention has been described and illustrated in connection with preferred embodiments, many variations and modifications as will be evident to those skilled in this art may be made without departing from the spirit and scope of the invention, and the invention is thus not to be limited to the precise details of methodology or construction set forth above as such variations and modification are intended to be included within the scope of the invention.
Patent Citations
Cited PatentFiling datePublication dateApplicantTitle
US4686620 *Jul 26, 1984Aug 11, 1987American Telephone And Telegraph Company, At&T Bell LaboratoriesDatabase backup method
US4995035 *Oct 31, 1988Feb 19, 1991International Business Machines CorporationCentralized management in a computer network
US5005122 *Sep 8, 1987Apr 2, 1991Digital Equipment CorporationArrangement with cooperating management server node and network service node
US5093912 *Jun 26, 1989Mar 3, 1992International Business Machines CorporationDynamic resource pool expansion and contraction in multiprocessing environments
US5133065 *Jul 27, 1989Jul 21, 1992Personal Computer Peripherals CorporationBackup computer program for networks
US5193154 *Oct 25, 1991Mar 9, 1993Hitachi, Ltd.Buffered peripheral system and method for backing up and retrieving data to and from backup memory device
US5212772 *Feb 11, 1991May 18, 1993Gigatrend IncorporatedSystem for storing data in backup tape device
US5226157 *Mar 2, 1989Jul 6, 1993Hitachi, Ltd.Backup control method and system in data processing system using identifiers for controlling block data transfer
US5239647 *Sep 7, 1990Aug 24, 1993International Business Machines CorporationData storage hierarchy with shared storage level
US5241668 *Apr 20, 1992Aug 31, 1993International Business Machines CorporationMethod and system for automated termination and resumption in a time zero backup copy process
US5241670 *Apr 20, 1992Aug 31, 1993International Business Machines CorporationMethod and system for automated backup copy ordering in a time zero backup copy session
US5276860 *Dec 19, 1989Jan 4, 1994Epoch Systems, Inc.Digital data processor with improved backup storage
US5276867 *Dec 19, 1989Jan 4, 1994Epoch Systems, Inc.Digital data storage system with improved data migration
US5287500 *Jun 3, 1991Feb 15, 1994Digital Equipment CorporationSystem for allocating storage spaces based upon required and optional service attributes having assigned piorities
US5321816 *Dec 9, 1992Jun 14, 1994Unisys CorporationLocal-remote apparatus with specialized image storage modules
US5333315 *Jun 27, 1991Jul 26, 1994Digital Equipment CorporationSystem of device independent file directories using a tag between the directories and file descriptors that migrate with the files
US5347653 *Jun 28, 1991Sep 13, 1994Digital Equipment CorporationSystem for reconstructing prior versions of indexes using records indicating changes between successive versions of the indexes
US5410700 *Sep 4, 1991Apr 25, 1995International Business Machines CorporationComputer system which supports asynchronous commitment of data
US5448724 *Mar 17, 1994Sep 5, 1995Fujitsu LimitedData processing system having double supervising functions
US5491810 *Mar 1, 1994Feb 13, 1996International Business Machines CorporationMethod and system for automated data storage system space allocation utilizing prioritized data set parameters
US5495607 *Nov 15, 1993Feb 27, 1996Conner Peripherals, Inc.Network management system having virtual catalog overview of files distributively stored across network domain
US5504873 *Nov 12, 1993Apr 2, 1996E-Systems, Inc.Mass data storage and retrieval system
US5544345 *Nov 8, 1993Aug 6, 1996International Business Machines CorporationCoherence controls for store-multiple shared data coordinated by cache directory entries in a shared electronic storage
US5544347 *Apr 23, 1993Aug 6, 1996Emc CorporationData storage system controlled remote data mirroring with respectively maintained data indices
US5559957 *May 31, 1995Sep 24, 1996Lucent Technologies Inc.File system for a data storage device having a power fail recovery mechanism for write/replace operations
US5619644 *Sep 18, 1995Apr 8, 1997International Business Machines CorporationSoftware directed microcode state save for distributed storage controller
US5638509 *Jun 13, 1996Jun 10, 1997Exabyte CorporationData storage and protection system
US5673381 *Jan 25, 1996Sep 30, 1997Cheyenne Software International Sales Corp.System and parallel streaming and data stripping to back-up a network
US5699361 *Jul 18, 1995Dec 16, 1997Industrial Technology Research InstituteMultimedia channel formulation mechanism
US5729743 *Nov 30, 1995Mar 17, 1998Deltatech Research, Inc.Computer apparatus and method for merging system deltas
US5751997 *Jan 19, 1996May 12, 1998Apple Computer, Inc.Method and apparatus for transferring archival data among an arbitrarily large number of computer devices in a networked computer environment
US5758359 *Oct 24, 1996May 26, 1998Digital Equipment CorporationMethod and apparatus for performing retroactive backups in a computer system
US5761677 *Jan 3, 1996Jun 2, 1998Sun Microsystems, Inc.Computer system method and apparatus providing for various versions of a file without requiring data copy or log operations
US5764972 *Jun 7, 1995Jun 9, 1998Lsc, Inc.Archiving file system for data servers in a distributed network environment
US5778395 *Oct 23, 1995Jul 7, 1998Stac, Inc.System for backing up files from disk volumes on multiple nodes of a computer network
US5812398 *Jun 10, 1996Sep 22, 1998Sun Microsystems, Inc.Method and system for escrowed backup of hotelled world wide web sites
US5813008 *Jul 12, 1996Sep 22, 1998Microsoft CorporationSingle instance storage of information
US5813009 *Jul 28, 1995Sep 22, 1998Univirtual Corp.Computer based records management system method
US5813017 *Sep 3, 1996Sep 22, 1998International Business Machines CorporationSystem and method for reducing storage requirement in backup subsystems utilizing segmented compression and differencing
US5875478 *Dec 3, 1996Feb 23, 1999Emc CorporationComputer backup using a file system, network, disk, tape and remote archiving repository media system
US5887134 *Jun 30, 1997Mar 23, 1999Sun MicrosystemsSystem and method for preserving message order while employing both programmed I/O and DMA operations
US5901327 *Mar 17, 1997May 4, 1999Emc CorporationBundling of write data from channel commands in a command chain for transmission over a data link between data storage systems for remote data mirroring
US5924102 *May 7, 1997Jul 13, 1999International Business Machines CorporationSystem and method for managing critical files
US5950205 *Sep 25, 1997Sep 7, 1999Cisco Technology, Inc.Data transmission over the internet using a cache memory file system
US5974563 *Oct 2, 1998Oct 26, 1999Network Specialists, Inc.Real time backup system
US6021415 *Oct 29, 1997Feb 1, 2000International Business Machines CorporationStorage management system with file aggregation and space reclamation within aggregated files
US6026414 *Mar 5, 1998Feb 15, 2000International Business Machines CorporationSystem including a proxy client to backup files in a distributed computing environment
US6052735 *Apr 10, 1998Apr 18, 2000Microsoft CorporationElectronic mail object synchronization between a desktop computer and mobile device
US6076148 *Dec 26, 1997Jun 13, 2000Emc CorporationMass storage subsystem and backup arrangement for digital data processing system which permits information to be backed up while host computer(s) continue(s) operating in connection with information stored on mass storage subsystem
US6094416 *May 9, 1997Jul 25, 2000I/O Control CorporationMulti-tier architecture for control network
US6131095 *Dec 11, 1996Oct 10, 2000Hewlett-Packard CompanyMethod of accessing a target entity over a communications network
US6131190 *May 5, 1999Oct 10, 2000Sidwell; Leland P.System for modifying JCL parameters to optimize data storage allocations
US6148412 *Sep 3, 1997Nov 14, 2000International Business Machines CorporationAvailability and recovery of files using copy storage pools
US6154787 *Jan 21, 1998Nov 28, 2000Unisys CorporationGrouping shared resources into one or more pools and automatically re-assigning shared resources from where they are not currently needed to where they are needed
US6161111 *Mar 31, 1998Dec 12, 2000Emc CorporationSystem and method for performing file-handling operations in a digital data processing system using an operating system-independent file map
US6167402 *Apr 27, 1998Dec 26, 2000Sun Microsystems, Inc.High performance message store
US6212512 *Jan 6, 1999Apr 3, 2001Hewlett-Packard CompanyIntegration of a database into file management software for protecting, tracking and retrieving data
US6260069 *Feb 10, 1998Jul 10, 2001International Business Machines CorporationDirect data retrieval in a distributed computing system
US6269431 *Aug 13, 1998Jul 31, 2001Emc CorporationVirtual storage and block level direct access of secondary storage for recovery of backup data
US6275953 *Sep 26, 1997Aug 14, 2001Emc CorporationRecovery from failure of a data processor in a network server
US6301592 *Nov 4, 1998Oct 9, 2001Hitachi, Ltd.Method of and an apparatus for displaying version information and configuration information and a computer-readable recording medium on which a version and configuration information display program is recorded
US6324581 *Mar 3, 1999Nov 27, 2001Emc CorporationFile server system using file system storage, data movers, and an exchange of meta data among data movers for file locking and direct access to shared file systems
US6328766 *Jun 25, 1998Dec 11, 2001Overland Data, Inc.Media element library with non-overlapping subset of media elements and non-overlapping subset of media element drives accessible to first host and unaccessible to second host
US6330570 *Feb 26, 1999Dec 11, 2001Hewlett-Packard CompanyData backup system
US6330642 *Jun 29, 2000Dec 11, 2001Bull Hn Informatin Systems Inc.Three interconnected raid disk controller data processing system architecture
US6343324 *Sep 13, 1999Jan 29, 2002International Business Machines CorporationMethod and system for controlling access share storage devices in a network environment by configuring host-to-volume mapping data structures in the controller memory for granting and denying access to the devices
US6356801 *May 19, 2000Mar 12, 2002International Business Machines CorporationHigh availability work queuing in an automated data storage library
US6389432 *Apr 5, 1999May 14, 2002Auspex Systems, Inc.Intelligent virtual volume access
US6421711 *Jun 29, 1998Jul 16, 2002Emc CorporationVirtual ports for data transferring of a data storage system
US6487561 *Dec 31, 1998Nov 26, 2002Emc CorporationApparatus and methods for copying, backing up, and restoring data using a backup segment size larger than the storage block size
US6519679 *Jun 11, 1999Feb 11, 2003Dell Usa, L.P.Policy based storage configuration
US6538669 *Jul 15, 1999Mar 25, 2003Dell Products L.P.Graphical user interface for configuration of a storage system
US6564228 *Jan 14, 2000May 13, 2003Sun Microsystems, Inc.Method of enabling heterogeneous platforms to utilize a universal file system in a storage area network
US6658526 *Oct 20, 1999Dec 2, 2003Storage Technology CorporationNetwork attached virtual data storage subsystem
US6757794 *Nov 1, 2002Jun 29, 2004Microsoft CorporationBuffering data in a hierarchical data storage environment
US6952756 *May 6, 2002Oct 4, 2005Lewiz CommunicationsMethod and apparatus for speculative loading of a memory
US7117246 *Dec 12, 2000Oct 3, 2006Sendmail, Inc.Electronic mail system with methodology providing distributed message store
US7246272 *Jan 16, 2004Jul 17, 2007International Business Machines CorporationDuplicate network address detection
US7287252 *Sep 27, 2002Oct 23, 2007The United States Of America Represented By The Secretary Of The NavyUniversal client and consumer
US20020107877 *Dec 29, 1997Aug 8, 2002Douglas L. WhitingSystem for backing up files from disk volumes on multiple nodes of a computer network
US20030033308 *Nov 9, 2001Feb 13, 2003Patel Sujal M.System and methods for providing a distributed file system utilizing metadata to track information about data stored throughout the system
US20050033756 *Apr 5, 2004Feb 10, 2005Rajiv KottomtharayilSystem and method for dynamically sharing storage volumes in a computer network
US20050086443 *Feb 20, 2004Apr 21, 2005Yoichi MizunoStorage system and method for backup
US20050131900 *Dec 12, 2003Jun 16, 2005International Business Machines CorporationMethods, apparatus and computer programs for enhanced access to resources within a network
US20060005048 *Jul 2, 2004Jan 5, 2006Hitachi Ltd.Method and apparatus for encrypted remote copy for secure data backup and restoration
US20060010227 *Sep 16, 2005Jan 12, 2006Rajeev AtluriMethods and apparatus for accessing data from a primary data storage system for secondary storage
US20060053305 *Sep 9, 2004Mar 9, 2006Microsoft CorporationMethod, system, and apparatus for creating saved searches and auto discovery groups for a data protection system
US20060230244 *Nov 8, 2005Oct 12, 2006Amarendran Arun PSystem and method for performing auxillary storage operations
US20060242489 *Dec 19, 2005Oct 26, 2006Brian BrockwayStored data reverification management system and method
USRE37601 *Nov 15, 1995Mar 19, 2002International Business Machines CorporationMethod and system for incremental time zero backup copying of data
Referenced by
Citing PatentFiling datePublication dateApplicantTitle
US7441092 *Apr 20, 2006Oct 21, 2008Microsoft CorporationMulti-client cluster-based backup and restore
US7447857 *Feb 28, 2008Nov 4, 2008Microsoft CorporationMulti-client cluster-based backup and restore
US7536291Nov 8, 2005May 19, 2009Commvault Systems, Inc.System and method to support simulated storage operations
US7739459Jan 14, 2009Jun 15, 2010Commvault Systems, Inc.Systems and methods for performing storage operations in a computer network
US7747579Nov 28, 2006Jun 29, 2010Commvault Systems, Inc.Metabase for facilitating data classification
US7769961Aug 3, 2010Commvault Systems, Inc.Systems and methods for sharing media in a computer network
US7801864 *Nov 28, 2006Sep 21, 2010Commvault Systems, Inc.Systems and methods for using metadata to enhance data identification operations
US7809914Nov 7, 2005Oct 5, 2010Commvault Systems, Inc.Methods and system of pooling storage devices
US7813913Oct 12, 2010Storage Appliance CorporationEmulation component for data backup applications
US7818160Aug 18, 2006Oct 19, 2010Storage Appliance CorporationData backup devices and methods for backing up data
US7822595 *Oct 26, 2010Storage Appliance CorporationSystems and methods for selectively copying embedded data files
US7827363Jul 22, 2008Nov 2, 2010Commvault Systems, Inc.Systems and methods for allocating control of storage media in a network environment
US7836174Nov 16, 2010Commvault Systems, Inc.Systems and methods for grid-based data scanning
US7840537Dec 21, 2007Nov 23, 2010Commvault Systems, Inc.System and method for storing redundant information
US7844445May 8, 2007Nov 30, 2010Storage Appliance CorporationAutomatic connection to an online service provider from a backup system
US7849059Nov 28, 2006Dec 7, 2010Commvault Systems, Inc.Data classification systems and methods for organizing a metabase
US7849266Feb 25, 2009Dec 7, 2010Commvault Systems, Inc.Method and system for grouping storage system components
US7894639 *Feb 22, 2011International Business Machines CorporationDigital life recorder implementing enhanced facial recognition subsystem for acquiring a face glossary data
US7899662Nov 28, 2006Mar 1, 2011Storage Appliance CorporationData backup system including a data protection component
US7900002 *Mar 1, 2011Microsoft CorporationMulti-client cluster-based backup and restore
US7949512May 24, 2011Commvault Systems, Inc.Systems and methods for performing virtual storage operations
US7953706May 31, 2011Commvault Systems, Inc.System and method for storing redundant information
US7958307Dec 3, 2010Jun 7, 2011Commvault Systems, Inc.Method and system for grouping storage system components
US7962452Dec 28, 2007Jun 14, 2011International Business Machines CorporationData deduplication by separating data from meta data
US7962642Jun 14, 2011Commvault Systems, Inc.Pipeline systems and method for transferring data in a network environment
US7962714Jun 14, 2011Commvault Systems, Inc.System and method for performing auxiliary storage operations
US8005272Dec 31, 2008Aug 23, 2011International Business Machines CorporationDigital life recorder implementing enhanced facial recognition subsystem for acquiring face glossary data
US8010531 *Aug 30, 2011Verizon Patent And Licensing Inc.Management of user interface elements
US8010769Nov 4, 2010Aug 30, 2011Commvault Systems, Inc.Systems and methods for classifying and transferring information in a storage network
US8019963Aug 24, 2009Sep 13, 2011Commvault Systems, Inc.Systems and methods for transferring data in a block-level storage operation
US8032718Oct 4, 2011Commvault Systems, Inc.Systems and methods for sharing media in a computer network
US8037028Oct 11, 2011Commvault Systems, Inc.System and method for storing redundant information
US8037031Oct 11, 2011Commvault Systems, Inc.Method and system for offline indexing of content and classifying stored data
US8041905Oct 18, 2011Commvault Systems, Inc.Systems and methods for allocating control of storage media in a network environment
US8055614 *Dec 23, 2008Nov 8, 2011Symantec CorporationMethod and apparatus for providing single instance restoration of data files
US8055618Nov 8, 2011International Business Machines CorporationData deduplication by separating data from meta data
US8069271May 30, 2008Nov 29, 2011Storage Appliance CorporationSystems and methods for converting a media player into a backup device
US8074042Oct 1, 2010Dec 6, 2011Commvault Systems, Inc.Methods and system of pooling storage devices
US8090683Mar 11, 2009Jan 3, 2012Iron Mountain IncorporatedManaging workflow communication in a distributed storage system
US8112548 *Sep 28, 2004Feb 7, 2012Yahoo! Inc.Method for providing a clip for viewing at a remote device
US8131680Nov 2, 2009Mar 6, 2012Commvault Systems, Inc.Systems and methods for using metadata to enhance data management operations
US8131725Sep 20, 2010Mar 6, 2012Comm Vault Systems, Inc.Systems and methods for using metadata to enhance data identification operations
US8131964Dec 15, 2010Mar 6, 2012Commvault Systems, Inc.Systems and methods for combining data streams in a storage operation
US8140637 *Sep 26, 2008Mar 20, 2012Hewlett-Packard Development Company, L.P.Communicating chunks between devices
US8140786Dec 4, 2007Mar 20, 2012Commvault Systems, Inc.Systems and methods for creating copies of data, such as archive copies
US8145598 *Feb 23, 2009Mar 27, 2012Iron Mountain IncorporatedMethods and systems for single instance storage of asset parts
US8161255Jan 6, 2009Apr 17, 2012International Business Machines CorporationOptimized simultaneous storing of data into deduplicated and non-deduplicated storage pools
US8166263Jul 3, 2008Apr 24, 2012Commvault Systems, Inc.Continuous data protection over intermittent connections, such as continuous data backup for laptops or wireless devices
US8170584May 1, 2012Yahoo! Inc.Providing an actionable event in an intercepted text message for a mobile device based on customized user information
US8176268Jun 10, 2010May 8, 2012Comm Vault Systems, Inc.Systems and methods for performing storage operations in a computer network
US8185498Sep 27, 2011May 22, 2012International Business Machines CorporationData deduplication by separating data from meta data
US8195444Jan 29, 2007Jun 5, 2012Storage Appliance CorporationSystems and methods for automated diagnosis and repair of storage devices
US8209293Jun 26, 2012Commvault Systems, Inc.System and method for extended media retention
US8219524Jul 10, 2012Commvault Systems, Inc.Application-aware and remote single instance data management
US8229954Jan 4, 2012Jul 24, 2012Commvault Systems, Inc.Managing copies of data
US8230171Jul 24, 2012Commvault Systems, Inc.System and method for improved media identification in a storage device
US8230195May 13, 2011Jul 24, 2012Commvault Systems, Inc.System and method for performing auxiliary storage operations
US8234249Jul 31, 2012Commvault Systems, Inc.Method and system for searching stored data
US8239654Aug 18, 2011Aug 7, 2012Commvault Systems, Inc.Systems and methods for transferring data in a block-level storage operation
US8271548Sep 18, 2012Commvault Systems, Inc.Systems and methods for using metadata to enhance storage operations
US8285681Oct 9, 2012Commvault Systems, Inc.Data object store and server for a cloud storage environment, including data deduplication and data management across multiple cloud storage sites
US8285683 *Oct 9, 2012Commvault Systems, Inc.System and method for storing redundant information
US8285685Jun 23, 2010Oct 9, 2012Commvault Systems, Inc.Metabase for facilitating data classification
US8285964Jul 21, 2011Oct 9, 2012Commvault Systems, Inc.Systems and methods for classifying and transferring information in a storage network
US8291177Oct 16, 2012Commvault Systems, Inc.Systems and methods for allocating control of storage media in a network environment
US8296301Oct 23, 2012Commvault Systems, Inc.Systems and methods for probabilistic data classification
US8307177Nov 6, 2012Commvault Systems, Inc.Systems and methods for management of virtualization data
US8312323Dec 21, 2007Nov 13, 2012Commvault Systems, Inc.Systems and methods for remote monitoring in a computer network and reporting a failed migration operation without accessing the data being moved
US8326915Jun 10, 2011Dec 4, 2012Commvault Systems, Inc.Pipeline systems and method for transferring data in a network environment
US8341182Dec 25, 2012Commvault Systems, Inc.Systems and methods of media management, such as management of media to and from a media storage library
US8341359Dec 25, 2012Commvault Systems, Inc.Systems and methods for sharing media and path management in a computer network
US8346733Mar 30, 2007Jan 1, 2013Commvault Systems, Inc.Systems and methods of media management, such as management of media to and from a media storage library
US8346734Jan 1, 2013Commvault Systems, Inc.Systems and methods of media management, such as management of media to and from a media storage library
US8352472Mar 2, 2012Jan 8, 2013Commvault Systems, Inc.Systems and methods for using metadata to enhance data identification operations
US8352954Jan 8, 2013Commvault Systems, Inc.Data storage resource allocation by employing dynamic methods and blacklisting resource request pools
US8356018Jan 15, 2013Commvault Systems, Inc.Systems and methods for grid-based data scanning
US8364652Dec 30, 2010Jan 29, 2013Commvault Systems, Inc.Content aligned block-based deduplication
US8364914May 7, 2012Jan 29, 2013Commvault Systems, Inc.Systems and methods for performing storage operations in a computer network
US8370442Aug 27, 2009Feb 5, 2013Commvault Systems, Inc.Method and system for leveraging identified changes to a mail server
US8370542Feb 5, 2013Commvault Systems, Inc.Combined stream auxiliary copy system and method
US8380957Feb 19, 2013Commvault Systems, Inc.Continuous data protection over intermittent connections, such as continuous data backup for laptops or wireless devices
US8392677Mar 5, 2013Commvault Systems, Inc.Systems and methods for creating copies of data, such as archive copies
US8396838Sep 7, 2010Mar 12, 2013Commvault Systems, Inc.Legal compliance, electronic discovery and electronic document handling of online and offline copies of data
US8397051Jun 15, 2009Mar 12, 2013Autonomy, Inc.Hybrid hash tables
US8397084Jun 12, 2008Mar 12, 2013Microsoft CorporationSingle instance storage of encrypted data
US8401996Mar 19, 2013Commvault Systems, Inc.Storing a variable number of instances of data objects
US8402000Mar 19, 2013Commvault Systems, Inc.Systems and methods of media management, such as management of media to and from a media storage library
US8407190Mar 26, 2013Commvault Systems, Inc.Performing data storage operations with a cloud environment, including containerized deduplication, data pruning, and data transfer
US8412677Apr 2, 2013Commvault Systems, Inc.Systems and methods for byte-level or quasi byte-level single instancing
US8413137Feb 4, 2011Apr 2, 2013Storage Appliance CorporationAutomated network backup peripheral device and method
US8417908Apr 9, 2013Commvault Systems, Inc.Systems and methods for combining data streams in a storage operation
US8429428Jun 8, 2010Apr 23, 2013Commvault Systems, Inc.System and method for providing encryption in storage operations in a storage network, such as for use by application service providers that provide data storage services
US8433682Dec 27, 2010Apr 30, 2013Commvault Systems, Inc.Systems and methods for analyzing snapshots
US8433872Mar 20, 2012Apr 30, 2013Commvault Systems, Inc.Snapshot storage and management system with indexing and user interface
US8434131Apr 30, 2013Commvault Systems, Inc.Managing connections in a data storage system
US8442944May 14, 2013Commvault Systems, Inc.System and method for generating and managing quick recovery volumes
US8442983May 14, 2013Commvault Systems, Inc.Asynchronous methods of data classification using change journals and other data structures
US8443142May 14, 2013Commvault Systems, Inc.Method and system for grouping storage system components
US8447728Sep 30, 2011May 21, 2013Commvault Systems, Inc.System and method for storage operation access security
US8463753Jun 11, 2013Commvault Systems, Inc.System and method for extended media retention
US8463994Jun 26, 2012Jun 11, 2013Commvault Systems, Inc.System and method for improved media identification in a storage device
US8478755Apr 20, 2006Jul 2, 2013Microsoft CorporationSorting large data sets
US8484162Mar 15, 2010Jul 9, 2013Commvault Systems, Inc.De-duplication systems and methods for application-specific data
US8484165Mar 31, 2008Jul 9, 2013Commvault Systems, Inc.Systems and methods of media management, such as management of media to and from a media storage library
US8495032Oct 1, 2008Jul 23, 2013International Business Machines CorporationPolicy based sharing of redundant data across storage pools in a deduplicating system
US8505010Mar 28, 2011Aug 6, 2013Commvault Systems, Inc.Storage of application specific profiles correlating to document versions
US8510516 *Sep 14, 2012Aug 13, 2013Commvault Systems, Inc.Systems and methods for sharing media in a computer network
US8527472Mar 29, 2011Sep 3, 2013Kaseya International LimitedMethod and apparatus of securely processing data for file backup, de-duplication, and restoration
US8533478 *Oct 24, 2008Sep 10, 2013Hewlett-Packard Development Company, L. P.System for and method of writing and reading redundant data
US8539118Jun 27, 2012Sep 17, 2013Commvault Systems, Inc.Systems and methods of media management, such as management of media to and from a media storage library, including removable media
US8543594 *Jul 29, 2011Sep 24, 2013Verizon Patent And Licensing Inc.Management of user interface elements
US8560503 *Jan 26, 2006Oct 15, 2013Netapp, Inc.Content addressable storage system
US8572340Dec 30, 2010Oct 29, 2013Commvault Systems, Inc.Systems and methods for retaining and using data block signatures in data protection operations
US8577851Dec 30, 2010Nov 5, 2013Commvault Systems, Inc.Content aligned block-based deduplication
US8578109Dec 30, 2010Nov 5, 2013Commvault Systems, Inc.Systems and methods for retaining and using data block signatures in data protection operations
US8578120Dec 28, 2009Nov 5, 2013Commvault Systems, Inc.Block-level single instancing
US8583594Sep 14, 2012Nov 12, 2013Commvault Systems, Inc.System and method for performing integrated storage operations
US8595191Dec 27, 2010Nov 26, 2013Commvault Systems, Inc.Systems and methods for performing data management operations using snapshots
US8612394Sep 30, 2011Dec 17, 2013Commvault Systems, Inc.System and method for archiving objects in an information store
US8612439Mar 31, 2010Dec 17, 2013Commvault Systems, Inc.Performing data storage operations in a cloud storage environment, including searching, encryption and indexing
US8612707Feb 14, 2013Dec 17, 2013Commvault Systems, Inc.Continuous data protection over intermittent connections, such as continuous data backup for laptops or wireless devices
US8612714Sep 14, 2012Dec 17, 2013Commvault Systems, Inc.Systems and methods for classifying and transferring information in a storage network
US8615523Jun 29, 2012Dec 24, 2013Commvault Systems, Inc.Method and system for searching stored data
US8620870Sep 30, 2011Dec 31, 2013Commvault Systems, Inc.Efficient data management improvements, such as docking limited-feature data management modules to a full-featured data management system
US8645333 *May 29, 2008Feb 4, 2014International Business Machines CorporationMethod and apparatus to minimize metadata in de-duplication
US8650445Sep 13, 2012Feb 11, 2014Commvault Systems, Inc.Systems and methods for remote monitoring in a computer network
US8655846May 14, 2013Feb 18, 2014Commvault Systems, Inc.System and method for generating and managing quick recovery volumes
US8655914Mar 30, 2007Feb 18, 2014Commvault Systems, Inc.System and method for storage operation access security
US8656068Jul 15, 2013Feb 18, 2014Commvault Systems, Inc.Systems and methods of media management, such as management of media to and from a media storage library, including removable media
US8667189Jan 18, 2013Mar 4, 2014Commvault Systems, Inc.Combined stream auxiliary copy system and method
US8688931Jan 25, 2013Apr 1, 2014Commvault Systems, Inc.Systems and methods for performing storage operations in a computer network
US8706867Mar 31, 2011Apr 22, 2014Commvault Systems, Inc.Realtime streaming of multimedia content from secondary storage devices
US8706976Sep 2, 2008Apr 22, 2014Commvault Systems, Inc.Parallel access virtual tape library and drives
US8707070Aug 28, 2008Apr 22, 2014Commvault Systems, Inc.Power management of data processing resources, such as power adaptive management of data storage operations
US8712969 *Sep 14, 2012Apr 29, 2014Commvault Systems, Inc.System and method for storing redundant information
US8719264Mar 31, 2011May 6, 2014Commvault Systems, Inc.Creating secondary copies of data based on searches for content
US8719767Mar 31, 2011May 6, 2014Commvault Systems, Inc.Utilizing snapshots to provide builds to developer computing devices
US8725687Apr 2, 2013May 13, 2014Commvault Systems, Inc.Systems and methods for byte-level or quasi byte-level single instancing
US8725688Sep 3, 2009May 13, 2014Commvault Systems, Inc.Image level copy or restore, such as image level restore without knowledge of data object metadata
US8725731Jan 23, 2012May 13, 2014Commvault Systems, Inc.Systems and methods for retrieving data in a computer network
US8725737Sep 11, 2012May 13, 2014Commvault Systems, Inc.Systems and methods for using metadata to enhance data identification operations
US8725964Sep 7, 2012May 13, 2014Commvault Systems, Inc.Interface systems and methods for accessing stored data
US8725973Nov 2, 2012May 13, 2014Commvault Systems, Inc.Systems and methods for management of virtualization data
US8732168Jul 25, 2012May 20, 2014Deacon JohnsonSystem and method for controlling and organizing metadata associated with on-line content
US8745365Aug 6, 2009Jun 3, 2014Imation Corp.Method and system for secure booting a computer by booting a first operating system from a secure peripheral device and launching a second operating system stored a secure area in the secure peripheral device on the first operating system
US8756203Dec 27, 2012Jun 17, 2014Commvault Systems, Inc.Systems and methods of media management, such as management of media to and from a media storage library
US8762335May 21, 2013Jun 24, 2014Commvault Systems, Inc.System and method for storage operation access security
US8769048Jun 18, 2008Jul 1, 2014Commvault Systems, Inc.Data protection scheduling, such as providing a flexible backup window in a data protection system
US8769635Apr 30, 2013Jul 1, 2014Commvault Systems, Inc.Managing connections in a data storage system
US8782064Jun 29, 2012Jul 15, 2014Commvault Systems, Inc.Managing copies of data
US8799613Mar 5, 2013Aug 5, 2014Commvault Systems, Inc.Methods and system of pooling storage devices
US8806175Feb 6, 2013Aug 12, 2014Longsand LimitedHybrid hash tables
US8832031Mar 16, 2011Sep 9, 2014Commvault Systems, Inc.Systems and methods of hierarchical storage management, such as global management of storage operations
US8832406Dec 11, 2013Sep 9, 2014Commvault Systems, Inc.Systems and methods for classifying and transferring information in a storage network
US8838541Oct 25, 2007Sep 16, 2014Hewlett-Packard Development Company, L.P.Data processing apparatus and method of processing data
US8838923Dec 10, 2013Sep 16, 2014Commvault Systems, Inc.Continuous data protection over intermittent connections, such as continuous data backup for laptops or wireless devices
US8849761Sep 14, 2012Sep 30, 2014Commvault Systems, Inc.Data object store and server for a cloud storage environment, including data deduplication and data management across multiple cloud storage sites
US8849762Mar 31, 2011Sep 30, 2014Commvault Systems, Inc.Restoring computing environments, such as autorecovery of file systems at certain points in time
US8849819May 25, 2012Sep 30, 2014Deacon JohnsonSystem and method for controlling and organizing metadata associated with on-line content
US8849955Mar 31, 2010Sep 30, 2014Commvault Systems, Inc.Cloud storage and networking agents, including agents for utilizing multiple, different cloud storage sites
US8862841 *Apr 25, 2006Oct 14, 2014Hewlett-Packard Development Company, L.P.Method and system for scaleable, distributed, differential electronic-data backup and archiving
US8886853Sep 16, 2013Nov 11, 2014Commvault Systems, Inc.Systems and methods for uniquely identifying removable media by its manufacturing defects wherein defects includes bad memory or redundant cells or both
US8892523Jun 8, 2012Nov 18, 2014Commvault Systems, Inc.Auto summarization of content
US8892826Feb 19, 2014Nov 18, 2014Commvault Systems, Inc.Systems and methods for performing storage operations in a computer network
US8898411Apr 29, 2013Nov 25, 2014Commvault Systems, Inc.Snapshot storage and management system with indexing and user interface
US8909881 *Mar 5, 2013Dec 9, 2014Commvault Systems, Inc.Systems and methods for creating copies of data, such as archive copies
US8924428Dec 21, 2012Dec 30, 2014Commvault Systems, Inc.Systems and methods of media management, such as management of media to and from a media storage library
US8930306Jul 8, 2009Jan 6, 2015Commvault Systems, Inc.Synchronized data deduplication
US8930319Sep 13, 2012Jan 6, 2015Commvault Systems, Inc.Modular backup and retrieval system used in conjunction with a storage area network
US8930496Dec 15, 2006Jan 6, 2015Commvault Systems, Inc.Systems and methods of unified reconstruction in storage systems
US8935492Sep 30, 2011Jan 13, 2015Commvault Systems, Inc.Archiving data objects using secondary copies
US8938481Mar 11, 2013Jan 20, 2015Commvault Systems, Inc.Generic file level restore from a block-level secondary copy
US8950009Mar 7, 2013Feb 3, 2015Commvault Systems, Inc.Information management of data associated with multiple cloud services
US8954446Dec 13, 2011Feb 10, 2015Comm Vault Systems, Inc.Client-side repository in a networked deduplicated storage system
US8959299Sep 14, 2009Feb 17, 2015Commvault Systems, Inc.Using a snapshot as a data source
US8966288Apr 23, 2013Feb 24, 2015Commvault Systems, Inc.System and method for providing encryption in storage operations in a storage network, such as for use by application service providers that provide data storage services
US8972355 *Aug 31, 2009Mar 3, 2015Symantec CorporationSystems and methods for archiving related items
US8977672Jun 8, 2012Mar 10, 2015Commvault Systems, Inc.Intelligent scheduling for remote computers
US8996823Dec 23, 2013Mar 31, 2015Commvault Systems, Inc.Parallel access virtual tape library and drives
US9003117Mar 6, 2013Apr 7, 2015Commvault Systems, Inc.Hierarchical systems and methods for performing storage operations in a computer network
US9003137Mar 6, 2014Apr 7, 2015Commvault Systems, Inc.Interface systems and methods for accessing stored data
US9015181Sep 23, 2009Apr 21, 2015Commvault Systems, Inc.Systems and methods for managing single instancing data
US9020890Mar 11, 2013Apr 28, 2015Commvault Systems, Inc.Smart archiving and data previewing for mobile devices
US9020900Dec 13, 2011Apr 28, 2015Commvault Systems, Inc.Distributed deduplicated storage system
US9021198Jan 20, 2011Apr 28, 2015Commvault Systems, Inc.System and method for sharing SAN storage
US9021213Aug 9, 2013Apr 28, 2015Commvault Systems, Inc.System and method for sharing media in a computer network
US9021282Dec 23, 2013Apr 28, 2015Commvault Systems, Inc.Power management of data processing resources, such as power adaptive management of data storage operations
US9026498Mar 7, 2013May 5, 2015Commvault Systems, Inc.Lightweight mounting of a secondary copy of file system data
US9047296May 14, 2013Jun 2, 2015Commvault Systems, Inc.Asynchronous methods of data classification using change journals and other data structures
US9054864Mar 29, 2011Jun 9, 2015Kaseya LimitedMethod and apparatus of securely processing data for file backup, de-duplication, and restoration
US9058117Oct 9, 2013Jun 16, 2015Commvault Systems, Inc.Block-level single instancing
US9064133 *Mar 29, 2011Jun 23, 2015Kaseya LimitedMethod and apparatus of securely processing data for file backup, de-duplication, and restoration
US9069799Dec 27, 2012Jun 30, 2015Commvault Systems, Inc.Restoration of centralized data storage manager, such as data storage manager in a hierarchical data storage system
US9092378Sep 23, 2014Jul 28, 2015Commvault Systems, Inc.Restoring computing environments, such as autorecovery of file systems at certain points in time
US9092500Mar 10, 2013Jul 28, 2015Commvault Systems, Inc.Utilizing snapshots for access to databases and other applications
US9098495Jun 24, 2008Aug 4, 2015Commvault Systems, Inc.Application-aware and remote single instance data management
US9098514Jun 25, 2013Aug 4, 2015Commvault Systems, Inc.Efficient data management improvements, such as docking limited-feature data management modules to a full-featured data management system
US9098542May 7, 2014Aug 4, 2015Commvault Systems, Inc.Systems and methods for using metadata to enhance data identification operations
US9104340Sep 26, 2013Aug 11, 2015Commvault Systems, Inc.Systems and methods for performing storage operations using network attached storage
US9104623Dec 13, 2011Aug 11, 2015Commvault Systems, Inc.Client-side repository in a networked deduplicated storage system
US9105298Nov 25, 2008Aug 11, 2015International Business Machines CorporationDigital life recorder with selective playback of digital video
US9110602Jan 25, 2013Aug 18, 2015Commvault Systems, Inc.Content aligned block-based deduplication
US9116633Mar 8, 2013Aug 25, 2015Commvault Systems, Inc.Information management of virtual machines having mapped storage devices
US9116850Dec 13, 2011Aug 25, 2015Commvault Systems, Inc.Client-side repository in a networked deduplicated storage system
US9122600Dec 23, 2013Sep 1, 2015Commvault Systems, Inc.Systems and methods for remote monitoring in a computer network
US9124611Mar 14, 2014Sep 1, 2015Commvault Systems, Inc.Systems and methods for writing data and storage system specific metadata to network attached storage device
US9128883Jun 19, 2008Sep 8, 2015Commvault Systems, IncData storage resource allocation by performing abbreviated resource checks based on relative chances of failure of the data storage resources to determine whether data storage requests would fail
US9158787May 13, 2014Oct 13, 2015Commvault Systems, IncSystems and methods for byte-level or quasi byte-level single instancing
US9158835May 1, 2012Oct 13, 2015Commvault Systems, Inc.Method and system for offline indexing of content and classifying stored data
US9164850Dec 17, 2013Oct 20, 2015Commvault Systems, Inc.System and method for archiving objects in an information store
US9164995Dec 31, 2008Oct 20, 2015International Business Machines CorporationEstablishing usage policies for recorded events in digital life recording
US9170890Feb 28, 2014Oct 27, 2015Commvault Systems, Inc.Combined stream auxiliary copy system and method
US9171008Mar 26, 2013Oct 27, 2015Commvault Systems, Inc.Performing data storage operations with a cloud environment, including containerized deduplication, data pruning, and data transfer
US9189167Mar 7, 2013Nov 17, 2015Commvault Systems, Inc.Shared library in a data storage system
US9189170Mar 6, 2013Nov 17, 2015Commvault Systems, Inc.External storage manager for a data storage cell
US9201917Sep 19, 2014Dec 1, 2015Commvault Systems, Inc.Systems and methods for performing storage operations in a computer network
US9213848Jan 5, 2015Dec 15, 2015Commvault Systems, Inc.Information management of data associated with multiple cloud services
US9218374Jun 12, 2013Dec 22, 2015Commvault Systems, Inc.Collaborative restore in a networked storage system
US9218375Jun 12, 2013Dec 22, 2015Commvault Systems, Inc.Dedicated client-side signature generator in a networked storage system
US9218376Jun 12, 2013Dec 22, 2015Commvault Systems, Inc.Intelligent data sourcing in a networked storage system
US9223597Mar 11, 2013Dec 29, 2015Commvault Systems, Inc.Archiving virtual machines in a data storage system
US9239687Sep 27, 2013Jan 19, 2016Commvault Systems, Inc.Systems and methods for retaining and using data block signatures in data protection operations
US9244779Sep 23, 2011Jan 26, 2016Commvault Systems, Inc.Data recovery operations, such as recovery from modified network data management protocol data
US9244927 *Sep 30, 2008Jan 26, 2016Emc CorporationSystem and method for record level multiplexing of backup data to storage media
US9251186Jun 12, 2013Feb 2, 2016Commvault Systems, Inc.Backup using a client-side signature repository in a networked storage system
US9251190 *Mar 26, 2015Feb 2, 2016Commvault Systems, Inc.System and method for sharing media in a computer network
US9262226Jan 8, 2013Feb 16, 2016Commvault Systems, Inc.Data storage resource allocation by employing dynamic methods and blacklisting resource request pools
US9262275Jan 13, 2015Feb 16, 2016Commvault Systems, Inc.Archiving data objects using secondary copies
US9262435Aug 15, 2013Feb 16, 2016Commvault Systems, Inc.Location-based data synchronization management
US9262496Mar 7, 2013Feb 16, 2016Commvault Systems, Inc.Unified access to personal data
US9268602Nov 18, 2013Feb 23, 2016Commvault Systems, Inc.Systems and methods for performing data management operations using snapshots
US9270950May 30, 2008Feb 23, 2016International Business Machines CorporationIdentifying a locale for controlling capture of data by a digital life recorder based on location
US9274803Aug 6, 2013Mar 1, 2016Commvault Systems, Inc.Storage of application specific profiles correlating to document versions
US9275086Mar 6, 2013Mar 1, 2016Commvault Systems, Inc.Systems and methods for database archiving
US9286086Mar 11, 2013Mar 15, 2016Commvault Systems, Inc.Archiving virtual machines in a data storage system
US9286110Jun 24, 2013Mar 15, 2016Commvault Systems, Inc.Seamless virtual machine recall in a data storage system
US9286327Mar 7, 2013Mar 15, 2016Commvault Systems, Inc.Data storage recovery automation
US9292815Mar 6, 2013Mar 22, 2016Commvault Systems, Inc.Automation of data storage activities
US9298559Apr 30, 2013Mar 29, 2016Commvault Systems, Inc.Systems and methods for analyzing snapshots
US9311121Mar 11, 2013Apr 12, 2016Commvault Systems, Inc.Archiving virtual machines in a data storage system
US9313143Sep 4, 2013Apr 12, 2016Commvault Systems, Inc.Systems and methods for granular resource management in a storage network
US9323466Jul 25, 2014Apr 26, 2016Commvault Systems, Inc.System and method for client policy assignment in a data storage system
US9336226Aug 15, 2013May 10, 2016Commvault Systems, Inc.Criteria-based data synchronization management
US9348819 *Dec 21, 2012May 24, 2016Parallels IP Holdings GmbHMethod and system for file data management in virtual environment
US9367702Sep 30, 2013Jun 14, 2016Commvault Systems, Inc.Automatic file encryption
US9372827Mar 8, 2013Jun 21, 2016Commvault Systems, Inc.Migration of an existing computing system to new hardware
US9372941Oct 25, 2007Jun 21, 2016Hewlett Packard Enterprise Development LpData processing apparatus and method of processing data
US9378035Feb 12, 2013Jun 28, 2016Commvault Systems, Inc.Systems and methods for repurposing virtual machines
US9390109Nov 19, 2013Jul 12, 2016Commvault Systems, Inc.Systems and methods to detect deleted files
US9400803Jun 9, 2015Jul 26, 2016Commvault Systems, Inc.Systems and methods for restoring data from network attached storage
US9405635Apr 15, 2014Aug 2, 2016Commvault Systems, Inc.Multi-source restore in an information management system
US9405763Jun 28, 2013Aug 2, 2016Commvault Systems, Inc.De-duplication systems and methods for application-specific data
US9405928Sep 17, 2014Aug 2, 2016Commvault Systems, Inc.Deriving encryption rules based on file content
US9411986Aug 7, 2013Aug 9, 2016Commvault Systems, Inc.System and method for encrypting secondary copies of data
US20060085731 *Sep 28, 2004Apr 20, 2006Yahoo! Inc.Method for providing a clip for viewing at a remote device
US20060230244 *Nov 8, 2005Oct 12, 2006Amarendran Arun PSystem and method for performing auxillary storage operations
US20070083355 *Aug 18, 2006Apr 12, 2007Storage Appliance CorporationData backup devices and methods for backing up data
US20070143096 *Nov 28, 2006Jun 21, 2007Storage Appliance CorporationData backup system including a data protection component
US20070162271 *Mar 6, 2007Jul 12, 2007Storage Appliance CorporationSystems and methods for selecting and printing data files from a backup system
US20070179995 *Nov 28, 2006Aug 2, 2007Anand PrahladMetabase for facilitating data classification
US20070225962 *May 8, 2007Sep 27, 2007Storage Appliance CorporationAutomatic connection to an online service provider from a backup system
US20070250664 *Apr 20, 2006Oct 25, 2007Microsoft CorporationSorting large data sets
US20070250671 *Apr 20, 2006Oct 25, 2007Microsoft Corporation Microsoft Patent GroupMulti-client cluster-based back up and restore
US20070250674 *Apr 25, 2006Oct 25, 2007Fineberg Samuel AMethod and system for scaleable, distributed, differential electronic-data backup and archiving
US20070282954 *Jun 6, 2006Dec 6, 2007Yahoo! Inc.Providing an actionable event in an intercepted text message for a mobile device based on customized user information
US20080091747 *Mar 30, 2007Apr 17, 2008Anand PrahladSystem and method for storage operation access security
US20080126446 *Nov 27, 2007May 29, 2008Storage Appliance CorporationSystems and methods for backing up user settings
US20080168067 *Jun 8, 2007Jul 10, 2008Verizon Data Services Inc.Management of user interface elements
US20080168111 *Feb 28, 2008Jul 10, 2008Microsoft CorporationMulti-client cluster-based backup and restore
US20080226082 *Mar 12, 2008Sep 18, 2008Storage Appliance CorporationSystems and methods for secure data backup
US20080243466 *May 30, 2008Oct 2, 2008Storage Appliance CorporationSystems and methods for converting a media player into a backup device
US20080243879 *Dec 21, 2007Oct 2, 2008Parag GokhaleSystem and method for storing redundant information
US20090030955 *Sep 24, 2008Jan 29, 2009Storage Appliance CorporationAutomated data backup with graceful shutdown for vista-based system
US20090031298 *Jun 11, 2008Jan 29, 2009Jeffrey BrunetSystem and method for automated installation and/or launch of software
US20090113145 *Sep 26, 2008Apr 30, 2009Alastair SlaterData transfer
US20090171888 *Dec 28, 2007Jul 2, 2009International Business Machines CorporationData deduplication by separating data from meta data
US20090174787 *Dec 31, 2008Jul 9, 2009International Business Machines CorporationDigital Life Recorder Implementing Enhanced Facial Recognition Subsystem for Acquiring Face Glossary Data
US20090175510 *Nov 25, 2008Jul 9, 2009International Business Machines CorporationDigital Life Recorder Implementing Enhanced Facial Recognition Subsystem for Acquiring a Face Glossary Data
US20090175599 *Nov 25, 2008Jul 9, 2009International Business Machines CorporationDigital Life Recorder with Selective Playback of Digital Video
US20090177700 *Dec 31, 2008Jul 9, 2009International Business Machines CorporationEstablishing usage policies for recorded events in digital life recording
US20090295911 *Dec 3, 2009International Business Machines CorporationIdentifying a Locale for Controlling Capture of Data by a Digital Life Recorder Based on Location
US20090300321 *May 29, 2008Dec 3, 2009International Business Machines CorporationMethod and apparatus to minimize metadata in de-duplication
US20090313483 *Jun 12, 2008Dec 17, 2009Microsoft CorporationSingle Instance Storage of Encrypted Data
US20100070725 *Mar 18, 2010Anand PrahladSystems and methods for management of virtualization data
US20100082558 *Oct 1, 2008Apr 1, 2010International Business Machines CorporationPolicy-based sharing of redundant data across storage pools in a deduplicating system
US20100106974 *Oct 24, 2008Apr 29, 2010Aguilera Marcos KSystem For And Method Of Writing And Reading Redundant Data
US20100169560 *Mar 13, 2010Jul 1, 2010Jeffrey BrunetMethods for Selectively Copying Data Files to Networked Storage and Devices for Initiating the Same
US20100174881 *Jul 8, 2010International Business Machines CorporationOptimized simultaneous storing of data into deduplicated and non-deduplicated storage pools
US20100198792 *Oct 25, 2007Aug 5, 2010Peter Thomas CambleData processing apparatus and method of processing data
US20100215175 *Aug 26, 2010Iron Mountain IncorporatedMethods and systems for stripe blind encryption
US20100217931 *Mar 11, 2009Aug 26, 2010Iron Mountain IncorporatedManaging workflow communication in a distributed storage system
US20100217953 *Aug 26, 2010Beaman Peter DHybrid hash tables
US20100228784 *Sep 9, 2010Iron Mountain IncorporatedMethods and Systems for Single Instance Storage of Asset Parts
US20100228906 *Sep 9, 2010Arunprasad Ramiya MothilalManaging Data in a Non-Volatile Memory System
US20100332454 *Mar 31, 2010Dec 30, 2010Anand PrahladPerforming data storage operations with a cloud environment, including containerized deduplication, data pruning, and data transfer
US20100332456 *Mar 31, 2010Dec 30, 2010Anand PrahladData object store and server for a cloud storage environment, including data deduplication and data management across multiple cloud storage sites
US20100332818 *Mar 31, 2010Dec 30, 2010Anand PrahladCloud storage and networking agents, including agents for utilizing multiple, different cloud storage sites
US20110047180 *Feb 24, 2011Commvault Systems, Inc.Systems and methods for classifying and transferring information in a storage network
US20110093672 *Dec 16, 2010Apr 21, 2011Parag GokhaleSystems and methods for recovering electronic information from a storage medium
US20110196848 *Aug 11, 2011International Business Machines CorporationData deduplication by separating data from meta data
US20120011145 *Jan 12, 2012Verizon Data Services Inc.Management of user interface elements
US20120254136 *Mar 29, 2011Oct 4, 2012Kaseya International LimitedMethod and apparatus of securely processing data for file backup, de-duplication, and restoration
US20130006946 *Jan 3, 2013Commvault Systems, Inc.System and method for storing redundant information
US20140201153 *Jan 10, 2014Jul 17, 2014Commvault Systems, Inc.Partial file restore in a data storage system
US20140201154 *Jan 10, 2014Jul 17, 2014Commvault Systems, Inc.Sharing of secondary storage data
US20150058532 *Nov 21, 2013Feb 26, 2015Kabushiki Kaisha ToshibaMemory device, information-processing device and information-processing method
US20150177999 *May 9, 2014Jun 25, 2015Lyve Minds, Inc.Storage network data retrieval
WO2009110912A1 *Mar 17, 2008Sep 11, 2009Nec Laboratories America, Inc.System and method for content addressable storage
WO2010036754A1 *Sep 24, 2009Apr 1, 2010Commvault Systems, Inc.Systems and methods for managing single instancing data
WO2015172093A1 *May 8, 2015Nov 12, 2015Lyve Minds, Inc.Storage network data retrieval
Classifications
U.S. Classification711/162
International ClassificationG06F12/16
Cooperative ClassificationG06F12/02, G06F3/0604, G06F3/0665, G06F11/1453, H04L41/046, G06F3/0608, G06F3/0683, H04L41/22, G06F3/064, H04L67/1097, G06F3/0605, G06F3/0686, G06F3/0631, G06F12/00, G06F2201/815
European ClassificationG06F11/14A10D4, G06F3/06A6L4L, G06F3/06A2A2, G06F3/06A4C1, G06F3/06A4F2, G06F3/06A2C, G06F3/06A6L4, H04L29/08N9S
Legal Events
DateCodeEventDescription
May 8, 2006ASAssignment
Owner name: SILICON VALLEY BANK, CALIFORNIA
Free format text: SECURITY AGREEMENT;ASSIGNOR:COMMVAULT SYSTEMS, INC.;REEL/FRAME:017586/0261
Effective date: 20060502
Owner name: SILICON VALLEY BANK,CALIFORNIA
Free format text: SECURITY AGREEMENT;ASSIGNOR:COMMVAULT SYSTEMS, INC.;REEL/FRAME:017586/0261
Effective date: 20060502
Sep 11, 2006ASAssignment
Owner name: COMMVAULT SYSTEMS, INC., NEW JERSEY
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:AMARENDRAN, ARUN P.;RETNAMMA, MANOJ K. VIJAYAN;REEL/FRAME:018289/0171
Effective date: 20060418
Jul 7, 2008ASAssignment
Owner name: COMMVAULT SYSTEMS, INC., NEW JERSEY
Free format text: RELEASE;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:021217/0246
Effective date: 20080626
Owner name: COMMVAULT SYSTEMS, INC.,NEW JERSEY
Free format text: RELEASE;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:021217/0246
Effective date: 20080626