US20100312979A1 - Systems and Methods for Migrating Components in a Hierarchical Storage Network - Google Patents

Systems and Methods for Migrating Components in a Hierarchical Storage Network Download PDF

Info

Publication number
US20100312979A1
US20100312979A1 US12/856,995 US85699510A US2010312979A1 US 20100312979 A1 US20100312979 A1 US 20100312979A1 US 85699510 A US85699510 A US 85699510A US 2010312979 A1 US2010312979 A1 US 2010312979A1
Authority
US
United States
Prior art keywords
storage
storage operation
operation cell
resource
data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US12/856,995
Inventor
Srinivas Kavuri
Marcus Muller
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Commvault Systems Inc
Original Assignee
Commvault Systems Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Commvault Systems Inc filed Critical Commvault Systems Inc
Publication of US20100312979A1 publication Critical patent/US20100312979A1/en
Assigned to COMMVAULT SYSTEMS, INC. reassignment COMMVAULT SYSTEMS, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: KAVURI, SRINIVAS, MULLER, MARCUS
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601Interfaces specially adapted for storage systems
    • G06F3/0602Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/061Improving I/O performance
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/17Details of further file system functions
    • G06F16/178Techniques for file synchronisation in file systems
    • G06F16/1787Details of non-transparently synchronising file systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21Design, administration or maintenance of databases
    • G06F16/217Database tuning
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601Interfaces specially adapted for storage systems
    • G06F3/0628Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0629Configuration or reconfiguration of storage systems
    • G06F3/0631Configuration or reconfiguration of storage systems by allocating resources to storage systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601Interfaces specially adapted for storage systems
    • G06F3/0628Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0653Monitoring storage devices or systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601Interfaces specially adapted for storage systems
    • G06F3/0668Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/067Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/50Allocation of resources, e.g. of the central processing unit [CPU]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1097Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1446Point-in-time backing up or restoration of persistent data
    • G06F11/1458Management of the backup or restore process
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1446Point-in-time backing up or restoration of persistent data
    • G06F11/1458Management of the backup or restore process
    • G06F11/1469Backup restoration techniques
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601Interfaces specially adapted for storage systems
    • G06F3/0628Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0646Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
    • G06F3/0647Migration mechanisms

Definitions

  • the invention disclosed herein relates generally to performing storage operations on electronic data in a computer network. More particularly, the present invention relates to migrating resources used in performing storage operations from one storage operation cell to another.
  • Storage management systems have evolved over time into complex entities with many components including hardware and software modules designed to perform a variety of different storage operations on electronic data.
  • Current storage management systems employ a number of different methods to perform storage operations on electronic data.
  • data can be stored in primary storage as a primary copy or in secondary storage as various types of secondary copies including, as a backup copy, a snapshot copy, a hierarchical storage management copy (“HSM”), as an archive copy, and as other types of copies.
  • HSM hierarchical storage management copy
  • a primary copy of data is generally a production copy or other “live” version of the data which is used by a software application and is typically in the native format of that application.
  • Primary copy data may be maintained in a local memory or other high-speed storage device that allows for relatively fast data access.
  • Such primary copy data is typically retained for a period of time (e.g., a number of seconds, minutes, hours or days) before some or all of the data is stored as one or more secondary copies, for example, to prevent loss of data in the event a problem occurs with the data stored in primary storage.
  • Secondary copies may include point-in-time data and may be intended for long-term retention (e.g., weeks, months or years depending on retention criteria, for example as specified in a storage policy as further described herein) before some or all of the data is moved to other storage or discarded. Secondary copies may be indexed so users can browse and restore the data at another point in time. After certain primary copy data is copied to secondary storage, a pointer or other location indicia such as a stub may be placed in the primary copy to indicate the current location of that data.
  • a backup copy is generally a point-in-time copy of the primary copy data stored in a backup format as opposed to in native application format.
  • a backup copy may be stored in a backup format that is optimized for compression and efficient long-term storage.
  • Backup copies generally have relatively long retention periods and may be stored on media with slower retrieval times than other types of secondary copies and media. In some cases, backup copies may be stored at an offsite location.
  • a snapshot may be thought of as a representation or image of the primary copy data at a given point in time.
  • a snapshot generally creates a bit map or block level representation of a primary copy volume at a particular moment in time. Users typically gain a read-only access to the record of files and directories of the snapshot. By electing to restore primary copy data from a snapshot taken at a given point in time, users may also return the current file system to the prior state of the file system that existed when the snapshot was taken.
  • a snapshot may be created instantly, using a minimum of file space, but may still function as a conventional file system backup.
  • a snapshot may not actually create another physical copy of all the data, but may simply create pointers that are mapped to specific blocks of data taken at the point in time of the snapshot.
  • the initial snapshot may use only a small amount of disk space needed to record a mapping or other data structure representing or otherwise tracking the blocks that correspond to the current state of the volume (e.g., a bit map). Additional disk space is usually only required when files are actually modified later.
  • a Hierarchical Storage Management (“HSM”) copy is generally a copy of the primary copy data, but typically includes only a subset of the primary copy data that meets a certain criteria and is usually stored in a format other than the native application format.
  • an HSM copy might include only that data from the primary copy that is larger than a given size threshold or older than a given age threshold and that is stored in a backup format.
  • HSM data is removed from the primary copy, and a stub is stored in the primary copy to indicate its new location.
  • systems then use the stub to locate the data and often make recovery of the data appear transparent, even though the HSM data may be stored at a location different from the remaining primary copy data.
  • An archive copy is generally similar to an HSM copy, however, the data satisfying criteria for removal from the primary copy is generally completely removed with no stub left in the primary copy to indicate the new location (i.e., where it has been moved to).
  • Archive copies of data are generally stored in a backup format or other non-native application format.
  • archive copies are generally retained for very long periods of time (e.g., years) and in some cases are never deleted. Such archive copies may be made and kept for extended periods in order to meet compliance regulations or for other permanent storage applications.
  • data may be moved over its lifetime moves from expensive quick access storage, to less expensive slower access storage.
  • This process of moving data through these various tiers of storage is sometimes referred to as information lifecycle management (“mM”).
  • MM information lifecycle management
  • the QINETIX system provides a modular storage management architecture that may include, among other things, storage manager components, client or data agent components, and media agent components as further described in U.S. patent application Ser. No. 10/818,749 which is hereby incorporated herein by reference in its entirety.
  • the QINETIX system also provides for hierarchically configuring storage operation cells to perform certain other types of storage operations including snapshot copies, HSM copies, archive copies, and certain other types of copies of electronic data, as further described in U.S. patent application Ser. No. 11/120,619 which is hereby incorporated by reference in its entirety.
  • the QINETIX system also provides for meaningful integration between and among HSM systems and Storage Resource Management (“SRM”) systems.
  • SRM systems are typically concerned with monitoring the health, status, and other information associated with primary copies of data (e.g., live or production line copies). For example, an SRM application may monitor the capacity of a volume storing a primary copy of data, and the rate of data transfer relative to the available storage of that volume.
  • HSM systems are typically concerned with data transport to secondary storage, such as the parameters and particulars associated with the storage and migration of secondary copy data as opposed to monitoring of information associated with primary copy data.
  • HSM systems are thus generally directed to secondary copies and other archival data volumes. For example, an HSM system may be directed to migrating or otherwise transferring data to a secondary copy.
  • Transferring data to any one of the aforementioned secondary copy types may be performed using a storage management system, using one or more copy devices, components or other data transfer resources.
  • secondary copy operations or other storage operations may be performed at various times which may result in an undesirably high number of storage operations being performed at a particular time using the same or similar resources.
  • other secondary copy resources may be underutilized.
  • component migration, reallocation or movement may be desired or necessary, such as in a disaster recovery (DR) situation where data and/or resources are temporarily or permanently moved to another storage operation cell.
  • DR disaster recovery
  • aspects of the present invention are directed towards systems and methods for selectively or automatically migrating storage system resources between various storage operation cells.
  • a management component within the storage operation system may monitor system operation and migrate components from storage operation cell to another to facilitate failover recovery, promote load balancing within the system and improve overall system performance as further described herein.
  • Another aspect of the invention may involve performing certain predictive analyses on system operation to identify trends and/or tendencies within the system. Such information may be used as the basis for potentially migrating components from one storage operation cell to another to improve system performance and reduce or eliminate resource exhaustion or congestion conditions.
  • a method for automatically transferring a resource from a first storage operation cell to a second storage operation cell includes monitoring a first operational characteristic of a first resource in the first storage operation cell wherein the first operational characteristic has an associated first threshold; identifying a second storage operation cell including a second resource having a second operational characteristic that does not exceed a second threshold; determining whether the first resource may be transferred to the second storage operation cell such that the transfer is capable of causing the first operational characteristic to remain within the first threshold; and automatically transferring the first resource to the second storage operation cell if the first operational characteristic is near or exceeds the first threshold.
  • a system for optimizing performance of storage operations in a storage system including a plurality of storage operation cells and resources may include a storage manager that monitors an operational characteristic of a plurality of storage operation cells in the storage system; wherein the storage manager identifies a group first resources in a first storage operation cell and identifies a plurality of second storage operation cells to which the group of first resources may be transferred; and wherein the storage manager determines a potential effect that a transfer of the group of first resources to the plurality of second storage operation cells would have on the performance storage operations, and if the determined potential effect of a transfer of the group of first resources improves the performance of storage operations, the storage manager transfers the group of first resources to the plurality of second storage operation cells.
  • 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
  • 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
  • FIG. 3 is a block diagram of a hierarchically organized group of storage operation cells in a system to perform resource migration between storage operation cells according to an embodiment of the invention
  • FIG. 4 schematically depicts migration of various clients and media agents between storage operation cells in the hierarchically organized network of FIG. 3 , according to an embodiment of the invention
  • FIG. 5 is a flow diagram of a method for migrating one or more resources from one storage operation cell to another, according to an embodiment of the invention
  • FIG. 6 is a flow diagram of a method for dynamic resource allocation, according to an embodiment of the invention.
  • FIG. 7 is a flow diagram of a method for resource allocation based on predictive analysis, according to an embodiment of the invention.
  • the present invention provides for migrating or “reallocating” resources or components from one storage operation cell to another storage operation cell such that the migrated resources from the “source” storage operation cell become part of and operate with resources in the destination or “target” storage operation cell.
  • migrating or “reallocating” resources or components from one storage operation cell to another storage operation cell such that the migrated resources from the “source” storage operation cell become part of and operate with resources in the destination or “target” storage operation cell.
  • Such migration typically involves logical reassignment of certain resources from one storage operation cell to another (i.e., no actual physical movement), but, in some embodiments, may include a physical movement of resources or components.
  • a change of a logical association or reassignment of resources or components may include modifying associations or groups as defined in certain management software components which may involve changing a pointer, address or other referential element in a storage management system index or database and may indicate a new or changed network pathway to a migrated resource.
  • Physical movement may involve actual physical movement of some or all components from one location to another (which also, in some embodiments, may involve logical reassignment or update in management software, e.g., new cabling, routing, etc.).
  • Migrated resources may include clients, media agents, storage managers, storage devices and/or certain associated storage media, clients, transmission resources such as pathways, switches, routers or other resources or components.
  • the migration of resources between storage operation cells may occur in various situations, and may be temporary or permanent.
  • Some examples of scenarios in which resource migration maybe desirable include: failure of one or more storage operation cell resources (e.g., if one or more storage operation cell resources fails, a resource may be identified in another storage operation cell to replace the failed storage operation cell), merging storage operation cell resources (e.g., due to certain conditions within an enterprise or environment, storage operation cells may be merged to improve system performance or otherwise consolidate system resources, or to be substituted for other storage operation cells which may be removed), assisting in alleviating or reducing network congestion (e.g., one or more data pathways may be overburdened with a high volume of data transfers), changes or efficiency in using network pathways (e.g., one network pathway may be taken offline, or a network pathway may have comparatively faster/slower data transfer characteristics), load balancing (e.g., one or more media agents, storage devices or other component may be migrated to handle a high volume of data transfer streams or to more evenly distribute workload), addition or
  • storage operation cell resources may be migrated to more evenly distribute workload, promote failover response and system robustness, take advantage of particular storage characteristics of a particular resource for a storage operation, merge, reorganize or otherwise reconfigure system resources, information, or data, improve or maintain network accessibility and data protection, or improve any other performance characteristics as contemplated by various aspects of the invention.
  • resource migration may be performed under user supervision (e.g., by commands or scripts input by a user via a GUI); or automatically (i.e., without user supervision; e.g., by migration or management components throughout a network or by storage managers) based on user set parameters, a threshold, a storage policy, storage preference or other preference as further described herein; or through any combination of user commands and automatically executing components.
  • Storage operation cell migration operations may be initiated automatically as a suggested, corrective, or preemptive action with respect to enhancing system performance (e.g., to improve performance in various storage operation scenarios as described herein); or for other reasons (e.g., consolidation or reconfiguration, etc.).
  • FIG. 1 illustrates a block diagram of an illustrative storage operation cell 50 that may perform storage operations on electronic data in a computer network in accordance with an embodiment of the present invention.
  • storage operation cell 50 may generally include a storage manager 100 , a data agent 95 , a media agent 105 , a storage device 115 , and, in some embodiments, may include certain other components such as a client 85 , a data or information store 90 , databases 110 and 111 , jobs agent 120 , an interface module 125 , and a management agent 130 .
  • Such system and elements thereof are exemplary of a modular storage operation system such as the COMMVAULT QINETIX system, and also the COMMVAULT GALAXY storage operation system, available from COMMVAULT Systems, Inc. of Oceanport, N.J., and further described in U.S. Pat. No. 7,035,880, which is incorporated herein by reference in its entirety.
  • a storage operation cell such as cell 50
  • Exemplary storage operation cells according to embodiments of the invention may include, as further described herein, CommCells as embodied in the QNet storage management system and the QINETIX storage management system by COMMVAULT Systems of Oceanport, N.J.
  • Additional storage operations performed by storage operation cells may include creating, storing, retrieving, and migrating primary data copies and secondary data copies (which may include, for example, snapshot copies, backup copies, HSM copies, archive copies, and other types of copies of electronic data).
  • storage operation cells may also provide one or more integrated management consoles for users or system processes to interface with in order to perform certain storage operations on electronic data as further described herein. Such integrated management consoles may be displayed at a central control facility or several similar consoles distributed throughout multiple network locations to provide global or geographically specific network data storage information.
  • a storage policy is generally a data structure or other information source that includes 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.
  • a storage policy may indicate that certain data is to be stored in a specific storage device, retained for a specified period of time before being aged to another tier of secondary storage, copied to secondary storage using a specified number of streams, etc.
  • a storage policy may be stored to a storage manager database 111 , to archive media as metadata for use in restore operations or other storage operations, or to other locations or components of the system.
  • a schedule policy may specify when to perform storage operations and how often and may also specify performing certain storage operations on sub-clients of data and how to treat those sub-clients.
  • a sub-client may represent static or dynamic associations of portions of data of a volume that are mutually exclusive. Thus, a portion of data may be given a label, and the association may be stored as a static entity in an index, database or other storage location used by the system.
  • Sub-clients may also be used as an effective administrative scheme of organizing data according to data type, department within the enterprise, storage preferences, etc. For example, an administrator may find it preferable to separate e-mail data from financial data using two different sub-clients having different storage preferences, retention criteria, etc.
  • Storage operation cells may contain not only physical devices, but also may represent logical concepts, organizations, and hierarchies.
  • a first storage operation cell 50 may be configured to perform HSM operations, such as data backup or other types of data migration, and may include a variety of physical components including a storage manager 100 (or management agent 130 ), a media agent 105 , a client component 85 , and other components as described herein.
  • a second storage operation cell may contain the same or similar physical components, however, it may be configured to perform other storage operations, such as monitoring a primary data copy or performing other known storage operations.
  • each storage operation cell may contain the same or similar physical devices.
  • different storage operation cells may contain some or none of the same physical devices.
  • a storage operation cell 50 configured to perform SRM tasks may contain a media agent 105 , client 85 , or other network device connected to a primary storage volume
  • a storage operation cell 50 configured to perform HSM tasks may instead include a media agent 105 , client 85 , or other network device connected to a secondary storage volume and not contain the elements or components associated with and including the primary storage volume.
  • These two storage operation cells may each include a different storage manager 100 that coordinates storage operations via the same media agents 105 and storage devices 115 .
  • This “overlapping” configuration allows storage resources to be accessed by more than one storage manager 100 such that multiple paths exist to each storage device 115 facilitating failover, load balancing, and promoting robust data access via alternative routes.
  • the same storage manager 100 may control two or more storage operation cells 50 (whether or not each storage operation cell 50 has its own dedicated storage manager 100 ).
  • the extent or type of overlap may be user-defined (e.g., through a control console (not shown)) or may be automatically configured to optimize data storage and/or retrieval.
  • Data agent 95 may be a software module or part of a software module that is generally responsible for archiving, migrating, identifying, and recovering data from client computer 85 stored in an information store 90 or other memory location. Each client computer 85 may have at least one data agent 95 and the system can support multiple client computers 85 . In some embodiments, data agents 95 may be distributed between client 85 and storage manager 100 (and any other intermediate components (not shown)) or may be deployed from a remote location or its functions approximated by a remote process that performs some or all of the functions of data agent 95 .
  • Embodiments of the present invention may employ multiple data agents 95 each of which may perform a storage operation, e.g., backup, migrate, and recover data associated with a different application.
  • 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.
  • Other embodiments may employ one or more generic data agents 95 that can handle and process multiple data types rather than using the specialized data agents described above.
  • one data agent 95 may be required for each data type to archive, migrate, and restore the client computer 85 data.
  • the client computer 85 may 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 .
  • one or more generic data agents 95 may be used to back up, migrate and restore MICROSOFT EXCHANGE® 2000 Mailbox data and MICROSOFT EXCHANGE® 2000 Database data while another generic data agent may handle MICROSOFT EXCHANGE® 2000 Public Folder data and MICROSOFT WINDOWS® 2000 File System data, etc.
  • storage manager 100 may be a software module or other application that coordinates and controls storage operations performed by storage operation cell 50 .
  • Storage manager 100 may communicate with some or all elements of the storage operation cell 50 including client computers 85 , data agents 95 , media agents 105 , and storage devices 115 , to initiate and manage system backups, migrations, and data recovery.
  • Storage manager 100 may include a jobs agent 120 that monitors the status of some or all storage operations previously performed, currently being performed, or scheduled to be performed by storage operation cell 50 .
  • Jobs agent 120 may be communicatively coupled with an interface agent 125 (typically a software module or application).
  • Interface agent 125 may include information processing and display software, such as a graphical user interface (“GUI”), an application program interface (“API”), or other interactive interface through which users and system processes can retrieve information about the status of storage operations.
  • GUI graphical user interface
  • API application program interface
  • users may optionally issue instructions to various storage operation cells 50 regarding performance of the storage operations as described and contemplated by the present invention. For example, a user may modify a schedule concerning the number of pending snapshot copies (or other types of copies) scheduled as needed to suit particular needs or requirements.
  • a user may employ the GUI to view the status of pending storage operations in some or all of the storage operation cells in a given network; or to monitor the status of certain components in a particular storage operation cell (e.g., the amount of storage capacity left in a particular storage device).
  • interface 125 may display the cost metrics associated with a particular type of data storage and may allow a user to determine overall and target cost metrics associated with a particular data type, or certain storage operation cell 50 or other storage operation as predefined or user-defined (discussed in more detail below).
  • Storage manager 100 may also include a management agent 130 that is typically implemented as a software module or application program.
  • management agent 130 provides an interface that allows various management components 100 in other storage operation cells 50 to communicate with one another.
  • a certain network configuration includes multiple storage operation cells 50 adjacent to one another or otherwise logically related in a WAN or LAN configuration (not shown).
  • each storage operation cell 50 may be connected to the other through each respective interface module 125 . This allows each storage operation cell 50 to send and receive certain pertinent information from other storage operation cells 50 , including status information, routing information, information regarding capacity and utilization, etc. These communication paths may also be used to convey information and instructions regarding storage operations.
  • a management agent 130 in first storage operation cell 50 may communicate with a management agent 130 in a second storage operation cell 50 regarding the status of storage operations in the second storage operation cell.
  • Another illustrative example includes the case where a management agent 130 in first storage operation cell 50 communicates with a management agent 130 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 130 contained in the storage manager 100 .
  • management agent 130 in the first storage operation cell 50 communicates directly with and controls the components in the second storage operation cell 50 and bypasses the storage manager 100 in the second storage operation cell.
  • storage operation cells 50 can also be organized hierarchically such that hierarchically superior storage operation cells control or pass information to hierarchically subordinate storage operation cells or vice versa. More information regarding hierarchical organization of operation storage cells 50 will be provided below.
  • Storage manager 100 may also maintain an index cache, a database, or other data structure 111 .
  • the data stored in database 111 may be used to indicate logical associations between components of the system, user preferences, management tasks, or other useful data. As further described herein, some of this information may be stored in a media agent database or other local data store according to some embodiments. For example, the storage manager 100 may use data from database 111 to track logical associations between media agents 105 and storage devices 115 .
  • a media agent 105 may be implemented as software module that conveys data, as directed by a storage manager 100 , between a client computer 85 and one or more storage devices 115 such as a tape library, a magnetic media storage device, an optical media storage device, or any other suitable storage device.
  • media agents 105 may be communicatively coupled with and control a storage device 115 associated with that particular media agent.
  • a media agent 105 may be considered to be associated with a particular storage device 115 if that media agent 105 is capable of routing and storing data to particular storage device 115 .
  • a media agent 105 associated with a particular storage device 115 may instruct the storage device to use a robotic arm or other retrieval means to load or remove a certain storage media, and to subsequently archive, migrate, or restore data to or from that media.
  • Media agents 105 may communicate with a storage device 115 via a suitable communications path such as a SCSI or fiber channel communications link.
  • the storage device 115 may be communicatively coupled to a media agent 105 via a Storage Area Network (“SAN”).
  • SAN Storage Area Network
  • Each media agent 105 may maintain an index cache, a database, or other data structure 110 which stores index data generated during backup, migration, and restore and other storage operations as described herein. For example, performing storage operations on MICROSOFT EXCHANGE® data may generate index data. Such index data provides a media agent 105 or other external device with a fast and efficient mechanism for locating data stored or backed up.
  • a storage manager database 111 may store data associating a client 85 with a particular media agent 105 or storage device 115 , for example, as specified in a storage policy, while media agent database 110 may indicate where specifically the client 85 data is stored in storage device 115 , what specific files were stored, and other information associated with storage of client 85 data.
  • index data may be stored along with the data backed up in a storage device 115 , with an additional copy of the index data written to index cache 110 .
  • the data in index cache 110 is thus readily available for use in storage operations and other activities without having to be first retrieved from the storage device 115 .
  • a client computer 85 such as a data agent 95 , a media agent 105 , or a storage manager 100 coordinates and directs local archiving, migration, and retrieval application functions as further described in U.S. Pat. No. 7,035,880.
  • This client computer 85 can function independently or together with other similar client computers 85 .
  • FIG. 2 presents a generalized 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 in accordance with an embodiment of the present invention. It will be understood that although the storage operation cells generally depicted in FIG. 2 have different reference numbers from the storage operation cell 50 shown in FIG. 1 , these storage operation cells may be configured the same as or similar to the storage operation cell 50 depicted in FIG. 1 .
  • the system illustrated in FIG. 2 may include a master storage manager component 135 and various other storage operation cells.
  • the illustrative embodiment in FIG. 2 includes a first storage operation cell 140 , a second storage operation cell 145 , a third storage operation cell 150 , a fourth storage operation cell 155 , a fifth storage operation cell 160 , and an nth storage operation cell 165 .
  • this illustration is only exemplary and that fewer or more storage operation cells may be present or interconnected differently if desired.
  • Storage operation cells may be communicatively coupled and hierarchically organized.
  • a master storage manager component 135 may be associated with, communicate with, and direct storage operations for, a first storage operation cell 140 , a second storage operation cell 145 , a third storage operation cell 150 , a fourth storage operation cell 155 , a fifth storage operation cell 160 , and an nth storage operation cell 165 .
  • the master storage manager component 135 may not be part of any particular storage operation cell. In other embodiments (not shown), master storage manager component 135 may itself be part of a certain storage operation cell.
  • master storage manager component 135 may communicate with a management agent of the storage manager of the first storage operation cell 140 (or directly with the other components of first storage operation cell 140 ) with respect to storage operations performed in the first storage operation cell 140 .
  • master storage manager component 135 may instruct the first storage operation cell 140 with certain commands regarding a desired storage operation such as how and when to perform particular storage operations including the type of operation and the data on which to perform the operation.
  • master storage manager component 135 may track the status of its associated storage operation cells, such as the status of jobs, system components, system resources utilization, and other items, by communicating with manager agents (or other components) in the respective storage operation cells. Moreover, master storage manager component 135 may track the status of its associated storage operation cells by receiving periodic status updates from the manager agents (or other components) in the respective storage operation cells regarding jobs, system components, system resources, and other items. For example, master storage manager component 135 may use methods to monitor network resources such as mapping network pathways and topologies to, among other things, physically monitor storage operations and suggest, for example, alternate routes for storing data as further described herein.
  • master storage manager component 135 may store status information and other information regarding its associated storage operation cells and other system information in an index cache, database 137 or other data structure accessible to mater storage manager component 135 .
  • a presentation interface included in certain embodiments of master storage manager component 135 may access this information and present it to users and system processes with information regarding the status of storage operations, storage operation cells, system components, and other information of the system.
  • storage operation cells may be organized hierarchically. With this configuration, storage operation cells may inherit properties from hierarchically superior storage operation cells or be controlled by other storage operation cells in the hierarchy (automatically or otherwise). Thus, in the embodiment shown in FIG. 2 , storage operation cell 145 may control or is otherwise hierarchically superior to storage operation cells 150 , 155 , 160 , and 165 . Similarly, storage operation cell 155 may control storage operation cells 160 and 165 . Alternatively, in some embodiments, storage operation cells may inherit (or otherwise be associated with) storage policies, storage preferences, storage metrics, or other properties or characteristics according to their relative position in a hierarchy of storage operation cells.
  • Storage operation cells may also be organized hierarchically according to function, geography, architectural considerations, or other factors useful or desirable in performing storage operations. For example, in one embodiment, storage operation cell 140 may be directed to create snapshot copies of primary copy data, while storage operation cell 145 may be directed to create backup copies of primary copy data or other data.
  • storage operation cell 140 may represent a geographic segment of an enterprise, such as a Chicago office, and storage operation cell 145 may represents a different geographic segment, such as a New York office.
  • the second storage operation cells 145 , 150 , 155 , 160 , and 165 may represent departments within the New York office.
  • these storage operation cells could be further divided by function performing various storage operations for the New York office or load balancing storage operations for the New York office.
  • different storage operation cells directed to different functions may also contain the same or a subset of the same set of physical devices.
  • one storage operation cell in accordance with some embodiments of the present invention may be configured to perform SRM operations (such as a QSM cell in the COMMVAULT QINETIX system) and may contain the same, similar or a subset of the same physical devices as a cell configured to perform HSM or other types of storage operations.
  • SRM operations such as a QSM cell in the COMMVAULT QINETIX system
  • Each storage operation cell may, however, share the same parent or, alternatively, may be located on different branches of a storage operation cell hierarchy tree.
  • storage operation cell 140 may be directed to SRM operations whereas storage operation cell 155 may be directed to HSM operations.
  • storage operation cell 150 may be configured to perform SRM operations and storage operation cell 155 may be configured to perform HSM operations.
  • SRM operations SRM operations
  • HSM operations HSM operations
  • hierarchical organization of storage operation cells facilitates, among other things, system security and other considerations. For example, in some embodiments, only authorized users may be allowed to access or control certain storage operation cells.
  • a network administrator for an enterprise may have access to many or all storage operation cells including master storage manager 135 . But a network administrator for the New York office, according to a previous example, may only have access to storage operation cells 145 - 165 , which form the New York office storage management system.
  • the hierarchical organization of storage operation cells may facilitate storage management planning and decision-making.
  • data and other information related to HSM storage operation cells and SRM storage operation cells may be normalized (e.g., converted into a common format with normalized identifiers and other information) and combined by a master storage manager component or other hierarchically superior (or, if desired, hierarchically subordinate) component, and a user of master storage manager component 135 may view the status of some or all jobs in associated storage operation cells as well as the status of each component of the storage operation cells present in the system. Users may then plan and make decisions based on this global data.
  • a user may view high-level information regarding storage operations for the entire system, such as job status, component status, resource status (such as network pathways, etc.), and other information. This may be done from an SRM perspective to view primary copy information or from an HSM perspective to view secondary copy information. A user may 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.
  • master storage manager component 135 may alert a user such as a system administrator when a particular resource is unavailable or congested. For example, a particular storage device might be full or require additional media.
  • a master storage manager component may use information from an HSM storage operation cell and an SRM storage operation cell to present indicia or otherwise alert a user or otherwise identify aspects of storage associated with the storage management system and hierarchy of storage operation cells.
  • master storage manager component 135 may utilize the global data regarding its associated storage operation cells to suggest solutions to such problems when they occur (or act as a warning prior to occurrence). For example, master storage manager component 135 may alert the user that a storage device or other resource in a particular storage operation cell is full or otherwise congested, and then suggest, based on job and data storage information contained in its database, an alternate storage device or resource to migrate to the storage operation cell.
  • corrective actions based on such information may include suggesting an alternate data path to a particular storage device, or dividing data to be stored among various available storage devices as a load balancing measure or to otherwise optimize storage or retrieval time. In some embodiments, such suggestions or corrective actions may be performed automatically, if desired.
  • Examples of the types of information that may be monitored for an application such as MICROSOFT EXCHANGE® include:
  • HSM and SRM components may be aware of each other due to a common database or metabase of information, which may include normalized data. Therefore, in those embodiments there is no need for such information to pass through a master storage manager as these components may be able to communicate directly with one another.
  • storage operation cell 150 may communicate directly with storage operation cell 165 and vice versa. This may be accomplished through a direct communications link between the two (not shown) or by passing data through intermediate storage operation cells, such as storage operation cells 145 - 160 in this case.
  • FIG. 3 illustrates a block diagram of a hierarchically organized group of storage operation cells in a system to perform SRM and HSM storage operations on electronic data in a computer network in accordance with various illustrative implementations for migrating resources between storage operation cells in accordance with the present invention.
  • implementing storage operation cell component migration according to the present invention is not limited to having a particular organization of storage operation cells, nor to having storage operation cells with HSM and/or SRM component functionality.
  • the storage operation cells may be organized non-hierarchically or hierarchically, and may be implemented with or without a storage operation cell having a storage manager that functions as a master storage manager.
  • the network is not required to include a storage operation cell that performs SRM operations and not HSM storage operations.
  • First storage operation cell 170 includes a client 185 in communication with a primary volume 190 storing data, and a storage manager component 195 in communication with a storage manager database 200 and with client 185 .
  • Second storage operation cell 173 includes a client 186 in communication with a primary volume 191 , a media agent 206 in communication with a secondary storage media 211 and a secondary storage media 213 , clients 236 - 244 in communication with respective primary volumes (not shown for clarity of illustration), media agents 208 , 210 , and 212 in communication with one or more of storage volumes 211 , 213 , 217 , and 219 , and storage manager 196 in communication with each of the media agents 206 , 208 , 210 , and 212 in storage operation cell 173 .
  • Third storage operation cell 175 includes clients 246 and 250 in communication with respective primary volumes (not shown), media agents 214 , 216 , and 218 in respective communication with secondary storage media 221 , 223 , and 225 , and storage manager 260 in communication with each of the media agents in storage operation cell 175 .
  • Fourth storage operation cell includes a master storage manager component 215 in communication with a master storage manager database 220 .
  • databases 220 and 200 respectively associated with storage managers 215 and 195 are expressly depicted, storage managers 196 and 260 are similarly each in communication with a respective database; however, these databases are not separately depicted and may be considered as being included in storage managers 196 and 260 , in accordance with the illustrative storage manager 100 of FIG. 1 .
  • each depicted client device in storage operation cells 173 and 175 is in communication with the storage manager within its storage operation cell, but connecting lines are not shown for clarity of illustration. Depicted lines connecting media agents with clients and with storage volumes represent possible data flow paths according to the illustrative configuration.
  • a given media agent may be operative in storage operations (e.g., backup, archiving, restoring) with respect to any storage volume and any client to which it is illustrated as being connected by a solid line.
  • storage operations e.g., backup, archiving, restoring
  • Depicted lines connecting a media agent to a storage manager represent control information and/or metadata paths.
  • the first storage operation cell 170 may be configured to perform a particular type of storage operation, such as SRM storage operations. For example, the first storage operation cell 170 may monitor and perform SRM-related calculations and operations associated with primary copy data.
  • the first storage operation cell 170 includes a client component 185 in communication with a primary volume 190 for storing data.
  • client 185 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 190 .
  • Storage manager component 195 may contain 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 190 .
  • Storage manager 195 may track and store this and other information in storage manager database 200 which may include index information.
  • storage manager component 195 may track or monitor the amount of available space and other similar characteristics of data associated with primary volume 190 .
  • storage manager component 195 may also issue alerts or take other actions when the information associated with primary volume 190 satisfies certain criteria, such as alert criteria, criteria defined in a storage policy, a threshold, such as a user defined threshold or default threshold, or other criteria.
  • alert criteria such as alert criteria, criteria defined in a storage policy, a threshold, such as a user defined threshold or default threshold, or other criteria.
  • action may be taken or alerts sent if a characteristic relating to a storage manager, media agent, database, storage device, storage library, client or other component matches the criteria.
  • criteria may relate to resource characteristics, including, for example, network bandwidth utilization, resource capacity used or available, time period between storage operations, scheduling conflicts, processor loads, or other characteristics relating to performing a storage operation.
  • Second storage operation cell 173 may be directed to another type of storage operation, such as HSM storage operations.
  • the second storage operation cell 173 may perform backups, data migrations, snapshots, or other types of HSM-related operations known in the art.
  • data is migrated from faster and more expensive storage such as magnetic disk storage (i.e., primary storage) to less expensive storage such as tape storage (i.e., secondary storage).
  • the second storage operation cell 173 includes client component 186 in communication with the primary volume 191 storing data.
  • client component 186 and primary volume 191 are the same physical devices as the client component 185 and primary volume 190 in the first storage operation cell 170 .
  • the storage manager component 196 and its associated database (not shown, and which may include index information) in the second storage operation cell 173 are the same physical devices as the storage manager component and index in the first storage operation cell 170 .
  • Storage manager component 196 typically also contains HSM modules or other logic associated with the second storage operation cell 173 directed to performing HSM storage operations on primary volume 191 data.
  • Storage operation cell 173 therefore may also contain media agent 206 and a secondary storage media 211 configured for performing HSM-related operations on primary copy data stored on primary volume 191 .
  • storage manager 196 may migrate primary copy data from primary volume 191 to secondary volume 211 using media agent 206 .
  • Storage manager 196 may also track and store information associated with primary copy migration and other similar HSM-related operations in its storage manager database (not shown).
  • storage manager component 196 may direct HSM storage operations on primary copy data according to a storage policy associated with the primary copy 191 and stored in an index.
  • storage manager 196 may also track where primary copy information is stored, for example in secondary storage 211 .
  • Storage manager 196 media agents 206 , 208 , 210 , and 212 , and secondary storage media 213 and 217 may also be configured to perform such HSM storage operations with respect to primary copy data associated with clients 236 , 238 , 240 , 242 , and 244 . Further, storage operation cell 175 may similarly be configured for performing such HSM storage operations with respect to primary copy data associated with clients 246 , 248 , and 250 .
  • NOM Storage operation cell 180 may include a master storage manager 215 and a master storage manager 220 .
  • additional storage operation cells may be located hierarchically in between storage operation cell 180 and storage operation cells 170 , 173 , and 175 .
  • additional storage operation cells hierarchically superior to operation cell 180 may also be present in the hierarchy of storage operation cells.
  • storage operation cells 170 , 173 , and 175 may be connected by communications link 197 , which may be any suitable communications link such as a fiber channel or SCSI connection that allows storage operation cells 170 , 173 , and 175 to communicate directly with one another (i.e., without necessarily directly or indirectly involving storage operation cell 180 ).
  • Such communication between cells 170 and 173 may be accomplished, for example, by storage manager 195 communicating with storage manager 196 via link 197 .
  • This allows storage operation cells 170 and 173 to share information such as status or operational characteristics with one another such as availability on primary or secondary storage, trigger events based on such information, etc. This allows for the direct transfer of stored data to and from the storage operation cells (via link 197 ) without the need to communicate with or pass data through master storage manager 215 .
  • Storage operation cell 180 is also generally directed to performing certain types of storage operations, such as integration of SRM and HSM data from other storage operation cells, such as storage operation cells 170 , 173 , and 175 .
  • fourth storage operation cell 180 also performs other types of storage operations and might also be directed to HSM, SRM, or other types of storage operations for other reasons such as convenience, hardware allocation, media managers, administrative or organization reasons, etc.
  • FIG. 4 is a schematic depiction of migration of various components or resources, such as clients, media agents, primary storage, secondary storage databases, storage managers or other components from one storage operation cell to another storage operation cell in accordance with certain aspects of the present invention. As shown, this may include, for example, movement of certain resources from storage operation cell 173 to storage operation cells 170 and 175 in the illustrative configuration of FIG. 3 . As described herein, migration of storage operation cell resources may be used to optimize, consolidate, reorganize or otherwise reconfigure or transfer storage resources or components within the system. As mentioned above, migration of resources typically involves logical reassignment of certain resources, but may, in certain situations, also involve physical movement.
  • components or resources such as clients, media agents, primary storage, secondary storage databases, storage managers or other components from one storage operation cell to another storage operation cell in accordance with certain aspects of the present invention. As shown, this may include, for example, movement of certain resources from storage operation cell 173 to storage operation cells 170 and 175 in the illustrative configuration
  • Logical migration may include associating or assigning a resource to another storage operation cell. This may involve logically reassigning the resource to another storage operation cell by transferring the management information associated with that resource, as well as reassigning that resource itself to another storage operation cell.
  • a media agent may be transferred from one storage operation cell to another by transferring management information regarding the media agent to the new storage operation cell and logically reassigning the media associated with that agent to the new storage operation cell (without any actual physical movement).
  • storage manager database entries may be copied and repopulated with new links, path, and address information, etc. as necessary to complete the transfer and bring the transferred resources to a fully operational state within the new storage operation cell.
  • Migration of resources may be initiated by a storage manager, such as a master storage manager, or other component, or by a user, according to user selections or preferences. For example, a user may identify certain resources within a storage operation cell that are operating beyond a specified capacity or that are underutilized, and mark those resources as possible migration candidates (e.g., placed in a migration pool).
  • a storage manager such as a master storage manager, or other component
  • a user may identify certain resources within a storage operation cell that are operating beyond a specified capacity or that are underutilized, and mark those resources as possible migration candidates (e.g., placed in a migration pool).
  • a storage manager may monitor storage operation cells to determine whether storage operation cell resources are performing adequately or as desired, e.g., within a threshold or according to an operating criteria or characteristic, or otherwise detect that storage operation cell configurations are performing below an optimal, required or desired level. Based on acquired information, resources may be migrated to provide load balancing, promote efficient use of resources (e.g., storage media), improve data throughput, or provide other resource optimization. Resources may also be migrated and/or combined for convenience or administrative or organizational purposes (e.g., merge or close physical offices etc.).
  • migrating a resource from a source storage operation cell to a target storage operation cell may involve logically associating the migrated resource with target storage operation cell (without necessarily requiring actual physical movement).
  • Information relating to the logical association(s) of migrated components may be stored in an index, metabase, or database, for example database 220 (e.g., a storage manager database).
  • Such logical associations may include pointers to a new storage operation cell, a network pathway, or other indication that a storage operation cell resource has migrated.
  • information from the source storage operation cell including information from a storage manager and/or associated media agent(s) may also be migrated to the appropriate resources in the target storage operation cell; and a pointer or other referential element may be placed in the source storage operation cell to indicate the client's new location.
  • substantially all of this information may be moved to the target storage operation cell from the source storage operation cell.
  • some or all information such as management information in an index or metabase may be migrated along with the resource so the resource may be reconstituted and resume normal operation in the target storage operation cell.
  • This may include both data and media (e.g., media agents and their associated media libraries).
  • this management information may remain in the source storage operation cell.
  • a client may be moved from one storage operation cell to another, but one or more storage devices that store data from that client may remain in the source storage operation cell. In this case, this data from that client may remain in the source storage operation cell along with associated management information.
  • the target storage operation cell may include a pointer or other reference to the appropriate location in the source storage operation cell.
  • associated storage devices and/or the data itself associated with the migrated client may be migrated to the target storage operation cell, in which case substantially all management information may be also be migrated to the target storage operation cell.
  • management information may remain in both storage operation cells with both sets of information updated as changes occur.
  • data may be present in one storage operation cell with the client in a different storage operation cell, with pointers and references at the storage managers of each cell for interoperation.
  • a storage policy may indicate that a storage operation, such as a secondary copy operation is to be performed on a daily basis for a particular client using a particular media agent and storage device.
  • a storage operation such as a secondary copy operation
  • the media agent and storage device associated with storage operations for that client may be migrated to another storage operation cell for other uses (even if the media agent is still associated with clients in the original cell).
  • the associated media agent and storage device may be reassigned or referenced to a storage operation cell that is already associated with the other department or domain, or even reassigned or referred to some other storage operation cell.
  • clients may be added to an existing storage operation cell, and may generate data that exceeds media capacity of one or more storage devices in a storage operation cell.
  • a storage device from another storage operation cell may be identified to migrate to the storage operation cell to provide additional media capacity, or alternatively, one or more of the clients may be migrated to another storage operation cell that includes sufficient storage capacity to handle the load.
  • a client may be split or partitioned between two or more storage operation cells. In this case, the data agent associated with the client may be registered for operation in those storage operation cells as well, with some data in a first storage operation cell and some data in other storage operation cells.
  • the outline of the migrated devices or components and the changed data/information communication paths in the source storage operation cell 173 are depicted by dashed lines to indicate their migration, transfer, or removal from the source storage operation cell, and the migrated devices or components (identified by identical reference numerals) are depicted by solid lines in the target storage operation cell (i.e., cells 170 and 175 ) to indicate their migration to that target storage operation cell.
  • client 240 and data from storage manager 196 may be migrated from source storage operation cell 173 to target storage operation cell 175 (including storage manager 260 ) such that media agent 216 (or other media agent(s) of storage operation cell 175 ) is operative in managing data movement (e.g., for a storage operation, such as a backup, recovery, or migration) between primary storage volume of client 240 and secondary storage media 223 .
  • Transferring client 240 may occur and be desirable, for example, in the event that client 240 is moved from one enterprise department to another department, or in the event that media agent 210 previously associated with client 240 becomes overburdened, or is otherwise unavailable to perform specified functions.
  • client 240 may be reassigned without any physical movement of client 240 , but rather by movement of management information and logical reassignment within the system. Such an operation may sometimes be referred to herein as “migration” of one or more resources from one storage operation cell to another.
  • client 244 together with its associated media agent 212 may be migrated from source storage operation cell 173 to storage operation cell 175 , with media agent 212 subsequently being associated with secondary storage media 225 to manage data movement between client 244 (i.e., its primary storage volume) and secondary storage media 225 .
  • client 244 its associated storage manager data and possibly its associated media agent 212 , and media library and any other necessary or useful routing or management data may be migrated or transferred, for example, in the event that a storage volume 219 reaches a capacity that exceeds a threshold or criteria, or in another scenario in which it is desirable to migrate client 244 and media agent 212 .
  • client 186 (including its primary storage volume 191 ans storage manager data) may be migrated from source storage operation cell 173 to storage operation cell 175 such that media agent 214 (or other media agent in cell 175 ) is operative in managing data movement (e.g., for a storage operation, such as a backup, recovery, or migration) between primary storage volume 191 and secondary storage media 221 .
  • client 186 and its associated storage manager data may be migrated or transferred, for example, because media agent 214 is underutilized in storage operations and has capacity which meets a threshold or criteria, or media agent 206 is overburdened and exceeds a bandwidth threshold or criteria, or satisfies other criteria in which it may be desirable to transfer client 186 .
  • media agent 206 may be migrated from source storage operation cell 173 to storage operation cell 170 and associated with secondary storage media 227 to conduct data between client 185 or other clients (not shown) and secondary storage media 227 , providing for a storage operation, or a backup of data on primary storage volume 190 .
  • media agent 206 may remain associated with secondary storage media 211 to direct a storage operation of a primary storage volume 190 thereto, and, in such cases, secondary storage media 211 may also be migrated to storage operation cell 170 , and its association with media agent 208 may be removed.
  • Such migration may occur, for example, in the event that media agent 206 has a characteristic such as bandwidth, meeting a threshold or criteria to perform storage operations relating to client 185 and media agent 208 has a characteristic, such as bandwidth, to take over control of storage media 211 .
  • media agent 206 in addition to handling storage operation data movement between primary storage volume 191 , media agent 206 may also be operative in performing storage operations for primary storage volume 190 of client 185 via link 197 .
  • the workload of handling data movement in a storage operation for both of these primary storage volumes may overload media agent 206 and cause congestion.
  • clients 238 , 240 , and 242 may over utilize media agent 210 , thus causing congestion and delay, for example, in network pathways to media agent 210 , and also rapidly consume the storage capacity of storage media 217 and 219 .
  • performing a storage operation of client 244 via media agent 212 increases the storage capacity consumption rate of media 219 .
  • load balancing techniques and reallocation within a the storage operation cell may not adequately mitigate these problems, or may not represent an optimal solution compared to possibly migrating one or more resources to another storage operation cell (with or without migrating resources within the storage operation cell).
  • Load redistribution may be addressed according to the resource migration described above in connection with FIG. 4 .
  • client 186 (with primary storage volume 191 ) and client 244 and their associated data may be migrated to storage operation cell 175 , assigning each of these clients to a respective media agent and associated secondary storage that will not be overloaded or over-utilized by the addition of these clients.
  • media agent 206 may now be available to manage and control storage operations for client 185 , and thus it may be migrated to storage operation cell 170 .
  • HSM components may be added to storage manager 195 to allow for HSM operations, including collection and reporting of HSM data.
  • client 244 may be migrated to storage operation cell 175 . Because media agent 212 is associated with client 244 , it may be migrated to storage operation cell 175 with client 244 without requiring migration of other clients connected thereto, and without requiring any migration of databases (e.g., indexes) that media agent 212 would maintain for such other clients. In alternative implementations, a media agent already located in storage operation cell 175 may be assigned to client 244 , or a new media agent for client 244 may be installed and configured in storage operation cell 175 .
  • databases e.g., indexes
  • storage preferences, storage policies or other preferences provided for a storage operation cell, media agent or other component of a storage operation cell may be retained by the resource or component after migration to a target storage operation cell, or alternatively the preference may be overwritten with new preferences associated with the target storage operation cell.
  • the ability to migrate or transfer resources across storage operation cells provides for greater flexibility in solving load balancing problems, providing robust failover solutions, and providing means by which systems efficiency may be monitored and improved providing, for improved performance, reliability, and resource utilization.
  • load balancing or failover problems can be monitored and remedied on a system-wide or global basis, as well as on an individual storage component or resource level.
  • resource migration may be implemented or initiated according to a process including any of the following: (1) one or more steps executed automatically in response to user input; (2) one or more steps executed automatically without user input in accordance with certain system operating policies or guidelines; or (3) one or more manually executed steps with certain steps occurring automatically. It will be understood that the process described with reference to FIG. 5 is merely illustrative, and that each operation or series of operations may be implemented automatically, manually, or a combination thereof.
  • a user may initiate the resource migration process by interacting via a GUI (or other user interface) with a network resource management system that provides information and functions for storage operation cell resource allocation (step 505 ).
  • Resource management may be implemented as one or more software modules or applications that may be integrated with, or be a component of, for example, the HSM and/or SRM software. At least some of the information monitored or generated by the HSM and/or SRM components, or other storage manager components may be used by the network resource management system for allocating or migrating resources. For instance, corrective actions recommended by the HSM component may be used by the resource management system in determining whether migration of a resource to another storage operation cell should be recommended.
  • a storage manager or other system component may receive information relating to, or may periodically query storage operation cell or system resources, or consult an index or database or storage policy regarding storage operation cell or system resources to determine current and future scheduled storage operation cell and resource utilization, and initiate the resource migration process, (step 505 ).
  • Such periodic resource query may be the system checks or tests described in commonly owned U.S. patent application Ser. No. 11/269,513, titled SYSTEM AND METHOD FOR MONITORING A STORAGE NETWORK, filed Nov. 7, 2005.
  • a storage manager or other system component may determine current and/or predicted resource needs or requirements for a storage operation cell, for example, based on a storage policy or other information and allocate storage operation cell resources accordingly.
  • the network resource management system may identify one or more resources to be moved or migrated from a given storage operation cell based, for example, on system operating conditions, user preference, and/or combination of the two, which may include additional forecasting or provisioning analysis (step 507 ). For instance, the network resource management system may provide information (e.g., component storage capacity, rate of storage media consumption, scheduled storage operations, network data pathway load metrics, processor loads, and other performance metrics) concerning resources (e.g., clients, media agents, primary or secondary storage media, data paths, or other components) within each of the storage operation cells.
  • information e.g., component storage capacity, rate of storage media consumption, scheduled storage operations, network data pathway load metrics, processor loads, and other performance metrics
  • resources e.g., clients, media agents, primary or secondary storage media, data paths, or other components
  • such information may be obtained by a storage manager, master storage manager or other system component to calculate performance metrics and determine and/or identify storage operation cell resources for migration. This may be performed on a substantially global basis, and a master storage manager component or other management component may analyze operations of the storage operation cells in a network and make recommendations and/or suggestions for resource migration based on this information (e.g., based on certain system optimization or data routing, management, and movement algorithms, etc.).
  • the resource management system or storage manager may also generate alerts identifying operating conditions that require attention in the storage operation cells, such as a pathway or processor bottleneck, one or more storage operations that exceed a threshold relating to system performance which may be remedied by resource reallocation (e.g., as further described in FIG. 6 ).
  • the network resource management system or storage manager may also recommend the migration or reallocation of specific resources, and may also identify one or more potential target locations (within or without the source storage operation cell) for the migration or reallocation.
  • the network may be may correct problems, prior to occurrence to maintain or preserve system operation and data protection criteria and/or prevent service degradation (e.g., a “self-healing” capability in view of identified and impending component failures).
  • the alerts and/or recommendations for migrating one or more resources generated by various storage managers may be based on analysis of certain information (e.g., storage capacity, rate of storage media consumption, data path load metrics, and other performance metrics or other system diagnostics) concerning resources (e.g., clients, media agents, secondary storage media, data paths) within its storage operation cell including existing configurations of the storage operation cell, schedule policy or other preferences in advance of a storage operation.
  • certain information e.g., storage capacity, rate of storage media consumption, data path load metrics, and other performance metrics or other system diagnostics
  • resources e.g., clients, media agents, secondary storage media, data paths
  • the network resource management system may itself analyze information received or acquired directly or indirectly from the storage managers. For instance, such information from each storage operation cell may be stored on a globally accessible database. In a hierarchical configuration, such as shown in FIG. 3 , this information from each storage operation cell may be communicated to, and stored in the database of, the master storage manager. The network resource management system may then access and analyze this information to identify situations for which resource migration, or other corrective or preventative actions, may be recommended. Thus, the network resource migration system may facilitate identifying resources to be migrated. It will be understood, however, that in some situations the decision to migrate a resource across storage operation cells may be identified via the resource management system based on specific performance scenarios, configurations, resource characteristics or other basis.
  • the user may select via the GUI (or other interface means) a resource located in a source storage operation cell for assignment or re-assignment to a specified target storage operation cell (step 509 ).
  • the selection may be made automatically by the system based on system operating conditions and metrics as determined by performance algorithms or other analysis software.
  • the resource automatically selected may be identified as having appropriate utilization for migration to a target storage operation cell.
  • Possible resources that may be selected include a client, a media agent, storage media, transmission resources and a datapath (i.e., a combination of media agent and storage media and transmission path used by the storage policy to perform a data protection operation), or other system component.
  • a storage manager or other system component may direct that storage operations be quiesced or temporarily ceased and that certain confirmatory test(s) be performed to verify that the anticipated or intended storage operations can be performed in the new proposed storage operation cell configurations before allowing the new storage operation cell configurations to be brought online.
  • a storage manager or other system component may observe the source and target storage operation cells and any components which may be associated or affected by the migrated resource to determine whether the migration is operating as anticipated.
  • a storage manager or other system component may simulate the new resource configurations of the source and target storage operation cell in advance of the migration, to determine whether the configuration is desirable and likely to achieve the desired goal.
  • the simulation may take into account existing information relating to each storage operation cell resource and storage operation scheduling or other job related information which may be obtained from a storage policy. This may include simulation of one or more proposed configurations by analysis or optimization software, and choosing the best one based on specified criteria through the use of, for example, a selection algorithm (or user input).
  • the system may then provide for moving management information associated with each selected resource (and stored in the source storage operation cell storage manager) from the source storage manager to the target storage manager (step 511 ).
  • This may include any management information associated with the migrated resource such as index information associated with a media management component, metadata associated with the resource or other information.
  • the communication of this information may occur, for example, directly between storage managers of the source and target storage operation cells, or indirectly through one or more intermediary storage managers, which may include a master storage manager.
  • a copy of all or part of the management information may be physically transferred to the target storage manager.
  • the management information that is transferred to the target storage operation cell includes media records, archive records, application records, job history, source and target network pathway information and some or all storage policy criteria for that client.
  • the transfer of this information may be accomplished by first identifying or obtaining the information in the source storage operation cell, and copying the information, or merging the information in, to the target storage operation cell.
  • This may include the techniques described in co-pending application entitled “Systems and Methods of Unified Reconstruction in Storage Systems” attorney docket 25693/012, which claims priority from U.S. Provisional Application, 60/752,202, filed Dec. 19, 2005, both of which are hereby incorporated by reference in their entirety.
  • the system may create a folder or other destination into which the system stores the information. Then, the target storage operation cell may be confirmed and any other designations that may be required by the system depending on the resource being transferred and/or the target storage operation cell. For example, in migrating a client, it may be required to designate a library and a media agent in the target storage operation cell corresponding to a given storage policy. The system may merge the information stored in the folder into the storage manager of the target storage operation cell.
  • the management information may be stored to a storage manager database or index.
  • metadata or index information relating to the resource being migrated may be copied to a corresponding media management component in the target storage operation cell.
  • This allows the media management component such as a storage manager, media agent or other component in the target storage operation cell to properly to manage and interoperate with the transferred resource in the same or similar manner as in the source storage operation cell.
  • This typically includes associating the management information with the new storage operation cell and associated components and resources, etc., to ensure interoperation.
  • the migrated resource e.g., the client or other component
  • This resource configuration may occur, for example, prior to transferring the management information in step 511 .
  • a restore operation may be performed, such as an incremental restore operation.
  • the restore operation may be implemented in an incremental order, accessing the data and metadata stored on one or more storage media (e.g., from one or more jukeboxes) to restore the data and metadata in reverse time order, thus restoring the metadata in the target storage operation cell (e.g., the metadata stored in the storage manager as well as in clients and/or media agents).
  • information relating to the incremental order may be obtained and restored, (step 515 ).
  • restore methods may be used, if desired, such as by use of copying data blocks from other locations, checking pointers to resources or other components, according to the method described in co-pending commonly owned U.S. Provisional Patent Application Ser. No. 60/752,202, SYSTEMS AND METHODS FOR UNIFIED RECONSTRUCTION OF DATA IN A STORAGE NETWORK filed Dec. 19, 2005, and its corresponding utility application 25963/012.
  • the transferred resource may be assigned to one or more storage devices (step 517 ) by specifying, for example, particular mount paths, network pathways, and/or storage media.
  • the assignment may include logically associating one or more pathways and the migrated resource and may be based on past or predicted performance of resources.
  • Such associations may be stored in an index and may be provided using pointers or other methods.
  • the system may perform certain diagnostics to verify the resource migration configuration is as intended and check for errors (step 519 ).
  • diagnostics or storage operation cell configuration simulation may be performed on the source and/or target storage operation cell in advance of performing a storage operations on the source or target storage operation cells. This may be done to confirm that the resource migration was successful or to identify problems that may be present in the new configurations (and if identified, take steps to address or repair such problems).
  • Simulations of new configurations may include calculating known characteristics of a migrated resource and other storage operation cell resources together with metrics relating to storage operations to provide a confidence factor that may indicate whether the new configuration will provide the intended benefit. Based on one or more configuration confidence factors, a highest scoring configuration may be selected to be implemented. In the event that a resource is migrated, and the storage manager or other system component determines that yet another configuration would provide enhanced storage performance, the storage manager may analyze this information and initiate the migration process in an iterative fashion.
  • information including optimization levels, confidence factors, performance improvement, and other information relating to storage operation cell migration is stored and tracked to provide ongoing metrics that may be used to optimize future storage operation cell configurations.
  • FIG. 6 is a flow chart illustrating some of the steps involved in providing dynamic resource allocation in accordance with certain embodiments of the present invention.
  • this dynamic allocation procedure may be used for various dynamic reallocation of resources including, but not limited to, load balancing and/or failover configurations, predictive or corrective analysis reconfiguration, optimizations etc.
  • the operation of the resources in each storage operation cell may be monitored (step 705 ) by the system.
  • the monitored information may include storage capacity, rate of storage media consumption, data path load metrics, and other performance metrics as further described herein.
  • Such system monitoring may be automatic and established, for example, according to a user preference or default template defined by a system administrator setting forth performance or configuration requirements or preferences. The monitoring may be performed as described in commonly owned U.S. patent application Ser. No. 11/269,513, SYSTEM AND METHOD FOR MONITORING A STORAGE NETWORK, filed Nov. 7, 2005.
  • the system may compare or otherwise evaluate the operation of the resource with respect to one or more thresholds (step 710 ).
  • the thresholds may be established in a storage policy, user preference or other preference as mentioned above.
  • the comparison or evaluation may be based on individual comparisons of monitored metrics, indicia, and other parameters with respective individual thresholds.
  • a threshold for a secondary storage device may be a 70% utilization rate, above which additional media may be required to perform storage operations, or as another example, data path usage exceeding a particular capacity (e.g., 80%).
  • comparisons or evaluations may be made based on a metric that is a function (e.g., a use specified weighted sum or average) of monitored quantities and/or other metrics, and which may characterize the overall operating level of an individual resource or the storage operation cell as a whole (e.g., risk of data loss).
  • media usage and predicated growth metrics may be used to determine whether a particular media library can be continued to be used. If, for example. A media library is within a certain time period of being fully utilized, based on media usage and growth metrics (e.g., 3 days), the system may generate a warning, request new media for the library, and determine alternate destinations, should the library become substantially fully utilized (e.g., 95% capacity).
  • storage operation cell monitoring may continue on a constant or periodic basis. At some point, the monitoring may indicate that a particular resource exceeds a certain threshold or criteria.
  • the system may identify this resource as a potential resource to reallocate and/or identify other resources to allocate to the storage operation cell to remedy the condition causing the threshold to be exceeded.
  • the potential resources for reallocation may be identified by determining whether resources in other storage operation cells for which the operating thresholds are not exceeded (e.g., underutilized resources) are available for migration (step 720 ).
  • a list of such resources may be maintained by one or management components within the system and used to identify and consider which resources may be best be used to solve a particular problem.
  • a list of under utilized resources may be kept track of as a measure of the “reconfigurability” of system to adapt to changing conditions.
  • Resource information may be obtained by locating a pool of resources, querying a list of resources, comparing resources with job scheduling, storage policies or other information, pinging or otherwise communicating with resources to determine what resources may be underutilized or over utilized.
  • Cell information may also be obtained by consulting a storage manager, storage manager index, media agent, or other system component.
  • Potential resource reallocations may also include resources physically located within or logically associated with the storage operation cell of the resource to be transferred. In the case that more than one potential reallocation is identified, the system prioritizes them based on considerations such as how well the resource needs can be satisfied, load balancing, data loss risk, as well as other conditions which may be defined in advance by the user.
  • the system may also determine whether other conditions or constraints exist that prevent allocation or transfer of the resource, (e.g., physical location, lack of communications paths, incompatible with one another, impending or actual hardware failure, etc.) (step 725 ). If the resource cannot be allocated to any of the identified potential target locations, then the system may remove the resource from consideration for migration (step 730 ). Alternatively, the system may alert a user of the condition and allow the user to review the status of the resources. Also, in advance of an automatic migration, the system may send an alert to an administrator for authorization to perform the resource transfer. The system may then return to step 720 to locate other available resources for allocation. and/or for permission to proceed. In other embodiments, the system may have been preauthorized and the migration may occur substantially automatically.
  • other conditions or constraints e.g., physical location, lack of communications paths, incompatible with one another, impending or actual hardware failure, etc.
  • the system may determine (at step 720 ) the potential optimization improvement obtained by transferring the resource.
  • a storage manager or other system component may simulate the operation of a target storage operation cell including a component or resource migrated from a located storage operation cell and the operation of the located storage operation cell without the migrated resource.
  • Such simulation may include determining whether the migration will enhance or otherwise improve performance of storage operations and whether the new target and source storage operation cell configurations will continue to function appropriately. This may involve evaluation of certain system performance metrics such as growth rate of target, future scheduled jobs, routing, pathway and temporal constraints, etc. and simulate operation of proposed new configuration(s) for a certain period of time in the future to confirm the desired benefits, are in fact, likely to be achieved.
  • multiple such proposed configurations may be evaluated, with the m system (or user) selecting the most desirable option.
  • the system may automatically initiate the transfer, (step 735 ), (e.g., identifying and copying data relating to the resource, merging the data and reconfiguring the resource, updating the index with new logical associations of the new configuration, etc.).
  • Data relating to the resource transfer may be stored in a storage manager or media agent index or database.
  • the system may continue to periodically monitor the operation and resource utilization of the storage operation cells.
  • resource reallocation may be based on predictive and other analyses, as will be further understood in view of the illustrative operational flow shown in FIG. 7 .
  • the operation of the resources in each storage operation cell may be monitored by the system.
  • the monitored information may include monitoring trends or patterns such as those relating to storage capacity, rate of storage media consumption, data path load metrics, system congestion, data load with respect to time, or any other performance metrics of interest to a system operator.
  • This information may be communicated among storage operation cells, and/or to a master storage manager or other globally accessible location (step 810 ).
  • the monitored information may be used to perform predictive analysis type operations on a resource, storage operation cell, and/or network wide basis (step 815 ).
  • Predictions may relate to individual monitored parameters or metrics, or functions thereof, and may involve load analysis, level of data protection, risk criteria of a storage characteristics, cost of storing data, data availability, or other indicia or metrics concerning the resources or the state of storage operations in one or more storage operation cells.
  • the predictive analysis may be performed according to user, department, project, or other identifier. Such predictions may be performed in order to identify and correct resource shortages and/or system inefficiencies prior to their occurrence.
  • a user may interact with the system via the GUI (or other interface) to specify and perform a desired analysis, and access and/or generate reports for trends concerning resource allocation.
  • the user may specify alternative configurations of the resources and perform a predictive analysis for such alternative configurations based on the monitored information for the resources in the current configuration.
  • the predictive analysis is performed automatically, for example according to user pre-defined analysis; a storage policy; or other preference. Simulations of storage operation cell operations and/or configurations may also be tracked and used to optimize future storage operation cell operations and/or configurations.
  • Trends and patterns obtained in the predictive analysis may be used together with other information such as storage policy information to determine future resource use required to perform storage operations according to the storage policy and to prevent resource exhaustion, overuse and system inefficiencies.
  • the system may predict, based on growth trends within a certain storage operation cell, the need for additional media agents, storage media, transmission paths or other resources (e.g., within a certain time frame). Such resources may be migrated from one storage operation cell to another prior to a lack or overuse of such resources becomes problematic in a given cell.
  • the system may predict an impending shortage of storage media within a certain storage operation cell.
  • the system may consider various options for solving this problem and choose the optimal solution (including adding additional media to existing storage devices). This may involve migrating certain storage devices into the storage operation cell to help alleviate the predicted impending shortage of storage media.
  • Another example involves migrating additional media agents or data paths to a storage operation cell to help prevent bottlenecks or congestion conditions that may be predicted based on current growth or operational trends. For example, the system may predict media agent utilization will exceed a predefined utilization threshold based on client or data growth. In addition to considering other options, the system may locate and migrate (or prepare to migrate) additional media agents and reconfigure associated transmission paths to help alleviate this problem prior to its occurrence or before reaching certain level of severity.
  • Another scenario involves the case where device or component failure rates are trending above acceptable limits (e.g., for media agent hosts, storage manager hosts, storage devices, storage media, etc.).
  • the system may recognize this emerging problem and reassign certain resources such as clients and/or media agents to other transmission paths to minimize this problem, or the potential for this problem.
  • the system may also keep track of certain system configuration and operational information regarding system components such as hardware type, expected lifespan (in various configurations), current deployment time etc. This information may be evaluated to determine the likelihood of failure and system reconfiguration and/or device replacement recommendations or actions may be made based on this information. This may be accomplished using the systems and methods described in co-pending U.S. patent application Ser. No.
  • the system may monitor client growth in order to predict a point in time when it is desirable to split a storage operation cell into two or more storage operation cells or, alternatively when it may be desirable to combine multiple storage operation cells into one storage operation cell.
  • a storage operation cell may be split into multiple storage operation cells once the number of clients and/or media agent reach a certain threshold point. This point may be determined by certain utilization thresholds set as part of user preferences or system requirements, or may be based on bandwidth of computational abilities of such resources (e.g., predicted inability to or certain resources to handle operations with a certain time frame, etc.).
  • the system may recognize the need to split storage operation cells and create additional storage operation cells and migrate the appropriate resources into those storage operation cells as described above. Similarly, one or storage operation cells may be combined into a single storage operation cell once resource utilization falls below a certain threshold level. Such consolidation may also occur in the event of physical relocation or reallocation of certain resources to promote the efficient grouping or configuration of resources within the system.
  • the system may determine the future resources and future storage operation cell configurations required to perform storage operations and compare the resource requirement and storage operation cell configuration to a current resource allocation (step 820 ), such as existing components associated in one or more storage operation cells. Based on the comparison, resources may be reallocated, (e.g., migrated from a source storage operation cell to a target storage operation cell), either automatically by the system or in response to user specified reallocation, and/or a need for further modifications and/or enhancements to the storage network may be established (step 825 ). After the resources have been reallocated, the system may monitor trends in storage characteristics so that the trend or pattern predictive information may be dynamically updated accordingly and used to configure storage operation cell configurations on an ongoing basis a described herein (step 830 ). Accordingly, the system according to one embodiment is able to continuously maintain an optimized and/or fail-safe storage system even as over time the system changes in its usage, resources, capacity, setup etc.
  • a current resource allocation such as existing components associated in one or more storage operation cells.
  • resources may be real
  • resources or data may be migrated from one storage operation cell to another (existing or new) storage operation cell on a temporary or permanent basis.
  • the system may create a storage operation cell and migrate resources to that storage operation cell on a temporary basis such that the resources may be returned or otherwise reallocated at some point in the future once the problem has been corrected.
  • a certain storage operation cell has lost power and its resources are currently operating with a backup power supply such as a UPS (uninterruptible power supply).
  • UPS uninterruptible power supply
  • the system may be able to operate for only a limited period of time based on the UPS power.
  • the system may recognize the problem, and create a temporary storage operation cell and migrate clients and data from the storage operation cell that has lost power to the temporary storage operation cell.
  • Such a migration may be scheduled to be substantially complete before the UPS runs out of power. This allows data and other system operations to continue to operate substantially uninterrupted until power can be restored to the original storage operation cell.
  • data and storage operation cell resources may be returned to the original storage operation cell.
  • certain resources may be assigned to such temporary storage operation cells to act as a failover storage operation cell in such situations. This may be done to ensure data protection and system robustness even if certain storage operation cells are rendered inoperable by unforeseen or uncontrollable circumstances.
  • Systems and modules described herein may comprise software, firmware, hardware, or any combination(s) of software, firmware, or hardware 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 or methods, 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, and other interfaces suitable for the purposes described herein.

Abstract

System and methods for selectively or automatically migrating resources between storage operation cells are provided. In accordance with one aspect of the invention, a management component within the storage operation system may monitor system operation and migrate components from storage operation cell to another to facilitate failover recovery, promote load balancing within the system and improve overall system performance as further described herein. Another aspect of the invention may involve performing certain predictive analyses on system operation to reveal trends and tendencies within the system. Such information may be used as the basis for potentially migrating components from one storage operation cell to another to improve system performance and reduce or eliminate resource exhaustion or congestion conditions.

Description

    RELATED APPLICATIONS
  • This application is a continuation of U.S. patent application Ser. No. 11/639,808, filed Dec. 15, 2006, which claims the benefit under 35 U.S.C. §120 from Provisional Application No. 60/752,196, filed Dec. 19, 2005, which is incorporated herein by reference.
  • This application is related to the following patents and pending applications, each of which is hereby incorporated herein by reference in its entirety:
      • application Ser. No. 09/354,058, titled HIERARCHICAL BACKUP AND RETRIEVAL SYSTEM, filed Jul. 15, 1999, attorney docket number 4982/5;
      • U.S. Pat. No. 6,418,478, titled PIPELINED HIGH SPEED DATA TRANSFER MECHANISM, issued Jul. 9, 2002, attorney docket number 4982/6;
      • application Ser. No. 10/818,749, SYSTEM AND METHOD FOR DYNAMICALLY PERFORMING STORAGE OPERATIONS IN A COMPUTER NETWORK, filed Apr. 5, 2004, attorney docket number 4982/35;
      • application Ser. No. 10/877,831, HIERARCHICAL SYSTEM AND METHOD FOR PERFORMING STORAGE OPERATIONS IN A COMPUTER NETWORK, filed Jun. 25, 2004, attorney docket number 4982/39;
      • application Ser. No. 10/990,357, SYSTEM AND METHOD FOR COMBINING DATA STREAMS IN PIPELINED STORAGE OPERATIONS IN A STORAGE NETWORK, filed Nov. 15, 2004, attorney docket number 4982/46;
      • application Ser. No. 11/120,619, HIERARCHICAL SYSTEMS AND METHODS FOR PROVIDING STORAGE A UNIFIED VIEW OF STORAGE INFORMATION, filed May 2, 2005, attorney docket number 4982/54;
      • application Ser. No. 11/269,513, SYSTEM AND METHOD FOR MONITORING A STORAGE NETWORK, filed Nov. 7, 2005, attorney docket number 4982/66.
      • Application titled SYSTEMS AND METHODS FOR CLASSIFYING AND TRANSFERRING INFORMATION IN A STORAGE NETWORK, filed Dec. 19, 2005 attorney docket number 4982/75;
      • Application Ser. No. 60/752,198, SYSTEMS AND METHODS FOR GRANULAR RESOURCE MANAGEMENT IN A STORAGE NETWORK, filed Dec. 19, 2005, attorney docket number 4982/84;
      • Application titled SYSTEMS AND METHODS FOR PERFORMING MULTI-PATH STORAGE OPERATIONS filed Dec. 19, 2005, attorney docket number 4982/88;
      • application Ser. No. 60/752,202, SYSTEMS AND METHODS FOR UNIFIED RECONSTRUCTION OF DATA IN A STORAGE NETWORK filed Dec. 19, 2005, attorney docket number 4982/97;
      • application Ser. No. 60/752,201, SYSTEMS AND METHODS FOR RESYNCHRONIZING STORAGE OPERATIONS filed Dec. 19, 2005, attorney docket number 4982/98; and
      • application Ser. No. 60/752,197, SYSTEMS AND METHODS FOR HIERARCHICAL CLIENT GROUP MANAGEMENT filed Dec. 19, 2005, attorney docket number 4982/102.
    BACKGROUND OF THE INVENTION
  • The invention disclosed herein relates generally to performing storage operations on electronic data in a computer network. More particularly, the present invention relates to migrating resources used in performing storage operations from one storage operation cell to another.
  • Storage management systems have evolved over time into complex entities with many components including hardware and software modules designed to perform a variety of different storage operations on electronic data. Current storage management systems employ a number of different methods to perform storage operations on electronic data. For example, data can be stored in primary storage as a primary copy or in secondary storage as various types of secondary copies including, as a backup copy, a snapshot copy, a hierarchical storage management copy (“HSM”), as an archive copy, and as other types of copies.
  • A primary copy of data is generally a production copy or other “live” version of the data which is used by a software application and is typically in the native format of that application. Primary copy data may be maintained in a local memory or other high-speed storage device that allows for relatively fast data access. Such primary copy data is typically retained for a period of time (e.g., a number of seconds, minutes, hours or days) before some or all of the data is stored as one or more secondary copies, for example, to prevent loss of data in the event a problem occurs with the data stored in primary storage.
  • Secondary copies may include point-in-time data and may be intended for long-term retention (e.g., weeks, months or years depending on retention criteria, for example as specified in a storage policy as further described herein) before some or all of the data is moved to other storage or discarded. Secondary copies may be indexed so users can browse and restore the data at another point in time. After certain primary copy data is copied to secondary storage, a pointer or other location indicia such as a stub may be placed in the primary copy to indicate the current location of that data.
  • One type of secondary copy is a backup copy. A backup copy is generally a point-in-time copy of the primary copy data stored in a backup format as opposed to in native application format. For example, a backup copy may be stored in a backup format that is optimized for compression and efficient long-term storage. Backup copies generally have relatively long retention periods and may be stored on media with slower retrieval times than other types of secondary copies and media. In some cases, backup copies may be stored at an offsite location.
  • Another form of secondary copy is a snapshot copy. From an end-user viewpoint, a snapshot may be thought of as a representation or image of the primary copy data at a given point in time. A snapshot generally creates a bit map or block level representation of a primary copy volume at a particular moment in time. Users typically gain a read-only access to the record of files and directories of the snapshot. By electing to restore primary copy data from a snapshot taken at a given point in time, users may also return the current file system to the prior state of the file system that existed when the snapshot was taken.
  • A snapshot may be created instantly, using a minimum of file space, but may still function as a conventional file system backup. A snapshot may not actually create another physical copy of all the data, but may simply create pointers that are mapped to specific blocks of data taken at the point in time of the snapshot.
  • In some conventional systems, once a snapshot has been taken, the original blocks in use at the time at snapshot are preserved in a cache such that only subsequent changes to the file system would overwrite them. Therefore, the initial snapshot may use only a small amount of disk space needed to record a mapping or other data structure representing or otherwise tracking the blocks that correspond to the current state of the volume (e.g., a bit map). Additional disk space is usually only required when files are actually modified later.
  • Furthermore, when files are modified, typically only the pointers which map to blocks are copied, not the blocks themselves. In some systems, for example in the case of copy-on-write snapshots, when a block changes in primary storage, the block is copied to secondary storage before the block is overwritten in primary storage and the snapshot mapping of file system data is updated to reflect the changed block(s) at that particular point in time.
  • A Hierarchical Storage Management (“HSM”) copy is generally a copy of the primary copy data, but typically includes only a subset of the primary copy data that meets a certain criteria and is usually stored in a format other than the native application format. For example, an HSM copy might include only that data from the primary copy that is larger than a given size threshold or older than a given age threshold and that is stored in a backup format. Often, HSM data is removed from the primary copy, and a stub is stored in the primary copy to indicate its new location. When a user subsequently requests access to the HSM data that has been removed or migrated, systems then use the stub to locate the data and often make recovery of the data appear transparent, even though the HSM data may be stored at a location different from the remaining primary copy data.
  • An archive copy is generally similar to an HSM copy, however, the data satisfying criteria for removal from the primary copy is generally completely removed with no stub left in the primary copy to indicate the new location (i.e., where it has been moved to). Archive copies of data are generally stored in a backup format or other non-native application format. In addition, archive copies are generally retained for very long periods of time (e.g., years) and in some cases are never deleted. Such archive copies may be made and kept for extended periods in order to meet compliance regulations or for other permanent storage applications.
  • In some systems, data may be moved over its lifetime moves from expensive quick access storage, to less expensive slower access storage. This process of moving data through these various tiers of storage is sometimes referred to as information lifecycle management (“mM”). This is the process by which data is “aged” from more expensive forms of secondary storage with faster access/restore times down through less expensive secondary storage with slower access/restore times, for example, as the data becomes less important or mission critical over time.
  • Examples of various types of data and copies of data are further described in the above-referenced related applications that are hereby incorporated by reference in their entirety. One example of a system that performs storage operations on electronic data that produce such copies is the QINETIX storage management system by COMMVAULT Systems of Oceanport, N.J.
  • The QINETIX system provides a modular storage management architecture that may include, among other things, storage manager components, client or data agent components, and media agent components as further described in U.S. patent application Ser. No. 10/818,749 which is hereby incorporated herein by reference in its entirety.
  • The QINETIX system also provides for hierarchically configuring storage operation cells to perform certain other types of storage operations including snapshot copies, HSM copies, archive copies, and certain other types of copies of electronic data, as further described in U.S. patent application Ser. No. 11/120,619 which is hereby incorporated by reference in its entirety.
  • The QINETIX system, as further disclosed in U.S. patent application Ser. No. 11/120,619, also provides for meaningful integration between and among HSM systems and Storage Resource Management (“SRM”) systems. SRM systems are typically concerned with monitoring the health, status, and other information associated with primary copies of data (e.g., live or production line copies). For example, an SRM application may monitor the capacity of a volume storing a primary copy of data, and the rate of data transfer relative to the available storage of that volume. In contrast, HSM systems are typically concerned with data transport to secondary storage, such as the parameters and particulars associated with the storage and migration of secondary copy data as opposed to monitoring of information associated with primary copy data. HSM systems are thus generally directed to secondary copies and other archival data volumes. For example, an HSM system may be directed to migrating or otherwise transferring data to a secondary copy.
  • Transferring data to any one of the aforementioned secondary copy types may be performed using a storage management system, using one or more copy devices, components or other data transfer resources. Depending on storage requirements, secondary copy operations or other storage operations may be performed at various times which may result in an undesirably high number of storage operations being performed at a particular time using the same or similar resources. Meanwhile, other secondary copy resources may be underutilized.
  • In some instances, it may be desirable to migrate or reassign storage resources from one storage operation system, or subset of a system, such as a cell, to another to provide additional routing options or to help alleviate any bottlenecks or congestion that may occur based on established commitments or system configuration.
  • There are also situations where storage resources may be physically moved, and certain storage management components should be migrated to new places in the system to continue to support the moved storage resources.
  • Moreover, in certain situations, component migration, reallocation or movement, may be desired or necessary, such as in a disaster recovery (DR) situation where data and/or resources are temporarily or permanently moved to another storage operation cell.
  • SUMMARY OF THE INVENTION
  • Aspects of the present invention are directed towards systems and methods for selectively or automatically migrating storage system resources between various storage operation cells. In accordance with one aspect of the invention, a management component within the storage operation system may monitor system operation and migrate components from storage operation cell to another to facilitate failover recovery, promote load balancing within the system and improve overall system performance as further described herein. Another aspect of the invention may involve performing certain predictive analyses on system operation to identify trends and/or tendencies within the system. Such information may be used as the basis for potentially migrating components from one storage operation cell to another to improve system performance and reduce or eliminate resource exhaustion or congestion conditions.
  • In one illustrative embodiment of the invention, a method for automatically transferring a resource from a first storage operation cell to a second storage operation cell is provided. The method includes monitoring a first operational characteristic of a first resource in the first storage operation cell wherein the first operational characteristic has an associated first threshold; identifying a second storage operation cell including a second resource having a second operational characteristic that does not exceed a second threshold; determining whether the first resource may be transferred to the second storage operation cell such that the transfer is capable of causing the first operational characteristic to remain within the first threshold; and automatically transferring the first resource to the second storage operation cell if the first operational characteristic is near or exceeds the first threshold.
  • In accordance with another embodiment of the present invention, a system for optimizing performance of storage operations in a storage system including a plurality of storage operation cells and resources is provided. The system may include a storage manager that monitors an operational characteristic of a plurality of storage operation cells in the storage system; wherein the storage manager identifies a group first resources in a first storage operation cell and identifies a plurality of second storage operation cells to which the group of first resources may be transferred; and wherein the storage manager determines a potential effect that a transfer of the group of first resources to the plurality of second storage operation cells would have on the performance storage operations, and if the determined potential effect of a transfer of the group of first resources improves the performance of storage operations, the storage manager transfers the group of first resources to the plurality of second storage operation cells.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • Aspects of the invention are 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:
  • 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;
  • 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;
  • FIG. 3 is a block diagram of a hierarchically organized group of storage operation cells in a system to perform resource migration between storage operation cells according to an embodiment of the invention;
  • FIG. 4 schematically depicts migration of various clients and media agents between storage operation cells in the hierarchically organized network of FIG. 3, according to an embodiment of the invention;
  • FIG. 5 is a flow diagram of a method for migrating one or more resources from one storage operation cell to another, according to an embodiment of the invention;
  • FIG. 6 is a flow diagram of a method for dynamic resource allocation, according to an embodiment of the invention; and
  • FIG. 7 is a flow diagram of a method for resource allocation based on predictive analysis, according to an embodiment of the invention;
  • DETAILED DESCRIPTION
  • Systems and methods for migrating one or more components of a storage operation cell in a storage network, and for predicting certain requirements of storage operation cell components within the network are provided. In various illustrative embodiments, the present invention, among other things, provides for migrating or “reallocating” resources or components from one storage operation cell to another storage operation cell such that the migrated resources from the “source” storage operation cell become part of and operate with resources in the destination or “target” storage operation cell. Such migration typically involves logical reassignment of certain resources from one storage operation cell to another (i.e., no actual physical movement), but, in some embodiments, may include a physical movement of resources or components. For example, a change of a logical association or reassignment of resources or components may include modifying associations or groups as defined in certain management software components which may involve changing a pointer, address or other referential element in a storage management system index or database and may indicate a new or changed network pathway to a migrated resource. Physical movement however, may involve actual physical movement of some or all components from one location to another (which also, in some embodiments, may involve logical reassignment or update in management software, e.g., new cabling, routing, etc.). Migrated resources may include clients, media agents, storage managers, storage devices and/or certain associated storage media, clients, transmission resources such as pathways, switches, routers or other resources or components.
  • The migration of resources between storage operation cells may occur in various situations, and may be temporary or permanent. Some examples of scenarios in which resource migration maybe desirable include: failure of one or more storage operation cell resources (e.g., if one or more storage operation cell resources fails, a resource may be identified in another storage operation cell to replace the failed storage operation cell), merging storage operation cell resources (e.g., due to certain conditions within an enterprise or environment, storage operation cells may be merged to improve system performance or otherwise consolidate system resources, or to be substituted for other storage operation cells which may be removed), assisting in alleviating or reducing network congestion (e.g., one or more data pathways may be overburdened with a high volume of data transfers), changes or efficiency in using network pathways (e.g., one network pathway may be taken offline, or a network pathway may have comparatively faster/slower data transfer characteristics), load balancing (e.g., one or more media agents, storage devices or other component may be migrated to handle a high volume of data transfer streams or to more evenly distribute workload), addition or removal of storage operation cell resources (e.g., if a new storage operation cell resource may be migrated to a storage operation cell having the greatest need for such new resource, or if a resource is removed, another resource may be migrated to replace the removed resource), or other situations to facilitate certain system goals such resource optimization or data security which may arise in a storage management system.
  • Thus, in general, to optimize performance of storage operations in a storage management system, storage operation cell resources may be migrated to more evenly distribute workload, promote failover response and system robustness, take advantage of particular storage characteristics of a particular resource for a storage operation, merge, reorganize or otherwise reconfigure system resources, information, or data, improve or maintain network accessibility and data protection, or improve any other performance characteristics as contemplated by various aspects of the invention.
  • As further described herein, resource migration may be performed under user supervision (e.g., by commands or scripts input by a user via a GUI); or automatically (i.e., without user supervision; e.g., by migration or management components throughout a network or by storage managers) based on user set parameters, a threshold, a storage policy, storage preference or other preference as further described herein; or through any combination of user commands and automatically executing components. Storage operation cell migration operations may be initiated automatically as a suggested, corrective, or preemptive action with respect to enhancing system performance (e.g., to improve performance in various storage operation scenarios as described herein); or for other reasons (e.g., consolidation or reconfiguration, etc.).
  • One exemplary storage management system which may provide storage operation cell resource migration is described with reference to FIGS. 1 through 7, although it will be understood other storage management system architectures known in the art may also use the principles of the inventions described herein. FIG. 1 illustrates a block diagram of an illustrative storage operation cell 50 that may perform storage operations on electronic data in a computer network in accordance with an embodiment of the present invention. As shown, storage operation cell 50 may generally include a storage manager 100, a data agent 95, a media agent 105, a storage device 115, and, in some embodiments, may include certain other components such as a client 85, a data or information store 90, databases 110 and 111, jobs agent 120, an interface module 125, and a management agent 130. Such system and elements thereof are exemplary of a modular storage operation system such as the COMMVAULT QINETIX system, and also the COMMVAULT GALAXY storage operation system, available from COMMVAULT Systems, Inc. of Oceanport, N.J., and further described in U.S. Pat. No. 7,035,880, which is incorporated herein by reference in its entirety.
  • A storage operation cell, such as cell 50, may generally include combinations of hardware and software components associated with performing storage operations on electronic data. Exemplary storage operation cells according to embodiments of the invention may include, as further described herein, CommCells as embodied in the QNet storage management system and the QINETIX storage management system by COMMVAULT Systems of Oceanport, N.J.
  • Additional storage operations performed by storage operation cells may include creating, storing, retrieving, and migrating primary data copies and secondary data copies (which may include, for example, snapshot copies, backup copies, HSM copies, archive copies, and other types of copies of electronic data). In some embodiments, storage operation cells may also provide one or more integrated management consoles for users or system processes to interface with in order to perform certain storage operations on electronic data as further described herein. Such integrated management consoles may be displayed at a central control facility or several similar consoles distributed throughout multiple network locations to provide global or geographically specific network data storage information.
  • Storage operations may be performed according to a storage policy. A storage policy is generally a data structure or other information source that includes 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. Thus, a storage policy may indicate that certain data is to be stored in a specific storage device, retained for a specified period of time before being aged to another tier of secondary storage, copied to secondary storage using a specified number of streams, etc. A storage policy may be stored to a storage manager database 111, to archive media as metadata for use in restore operations or other storage operations, or to other locations or components of the system.
  • A schedule policy may specify when to perform storage operations and how often and may also specify performing certain storage operations on sub-clients of data and how to treat those sub-clients. A sub-client may represent static or dynamic associations of portions of data of a volume that are mutually exclusive. Thus, a portion of data may be given a label, and the association may be stored as a static entity in an index, database or other storage location used by the system. Sub-clients may also be used as an effective administrative scheme of organizing data according to data type, department within the enterprise, storage preferences, etc. For example, an administrator may find it preferable to separate e-mail data from financial data using two different sub-clients having different storage preferences, retention criteria, etc.
  • Storage operation cells may contain not only physical devices, but also may represent logical concepts, organizations, and hierarchies. For example, a first storage operation cell 50 may be configured to perform HSM operations, such as data backup or other types of data migration, and may include a variety of physical components including a storage manager 100 (or management agent 130), a media agent 105, a client component 85, and other components as described herein. A second storage operation cell may contain the same or similar physical components, however, it may be configured to perform other storage operations, such as monitoring a primary data copy or performing other known storage operations.
  • Thus, as can be appreciated from the above, although the first and second storage operation cells are logically distinct entities and may be configured to perform different management functions (e.g., HSM and SRM respectively), each storage operation cell may contain the same or similar physical devices. Alternatively, in other embodiments, different storage operation cells may contain some or none of the same physical devices. For example, a storage operation cell 50 configured to perform SRM tasks may contain a media agent 105, client 85, or other network device connected to a primary storage volume, while a storage operation cell 50 configured to perform HSM tasks may instead include a media agent 105, client 85, or other network device connected to a secondary storage volume and not contain the elements or components associated with and including the primary storage volume. These two storage operation cells, however, may each include a different storage manager 100 that coordinates storage operations via the same media agents 105 and storage devices 115. This “overlapping” configuration allows storage resources to be accessed by more than one storage manager 100 such that multiple paths exist to each storage device 115 facilitating failover, load balancing, and promoting robust data access via alternative routes.
  • Alternatively, in some embodiments, the same storage manager 100 may control two or more storage operation cells 50 (whether or not each storage operation cell 50 has its own dedicated storage manager 100). Moreover, in certain embodiments, the extent or type of overlap may be user-defined (e.g., through a control console (not shown)) or may be automatically configured to optimize data storage and/or retrieval.
  • Data agent 95 may be a software module or part of a software module that is generally responsible for archiving, migrating, identifying, and recovering data from client computer 85 stored in an information store 90 or other memory location. Each client computer 85 may have at least one data agent 95 and the system can support multiple client computers 85. In some embodiments, data agents 95 may be distributed between client 85 and storage manager 100 (and any other intermediate components (not shown)) or may be deployed from a remote location or its functions approximated by a remote process that performs some or all of the functions of data agent 95.
  • Embodiments of the present invention may employ multiple data agents 95 each of which may perform a storage operation, e.g., backup, migrate, and recover data associated with a different application. 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. Other embodiments may employ one or more generic data agents 95 that can handle and process multiple data types rather than using the specialized data agents described above.
  • If a client computer 85 has two or more types of data, one data agent 95 may be required for each data type to archive, migrate, and restore the 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 may 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.
  • Alternatively, other embodiments may use one or more generic data agents 95, each of which may be capable of handling two or more data types. For example, one generic data agent 95 may be used to back up, migrate and restore MICROSOFT EXCHANGE® 2000 Mailbox data and MICROSOFT EXCHANGE® 2000 Database data while another generic data agent may handle MICROSOFT EXCHANGE® 2000 Public Folder data and MICROSOFT WINDOWS® 2000 File System data, etc.
  • Generally speaking, storage manager 100 may be a software module or other application that coordinates and controls storage operations performed by storage operation cell 50. Storage manager 100 may communicate with some or all elements of the storage operation cell 50 including client computers 85, data agents 95, media agents 105, and storage devices 115, to initiate and manage system backups, migrations, and data recovery.
  • Storage manager 100 may include a jobs agent 120 that monitors the status of some or all storage operations previously performed, currently being performed, or scheduled to be performed by storage operation cell 50. Jobs agent 120 may be communicatively coupled with an interface agent 125 (typically a software module or application). Interface agent 125 may include information processing and display software, such as a graphical user interface (“GUI”), an application program interface (“API”), or other interactive interface through which users and system processes can retrieve information about the status of storage operations. Through interface 125, users may optionally issue instructions to various storage operation cells 50 regarding performance of the storage operations as described and contemplated by the present invention. For example, a user may modify a schedule concerning the number of pending snapshot copies (or other types of copies) scheduled as needed to suit particular needs or requirements. As another example, a user may employ the GUI to view the status of pending storage operations in some or all of the storage operation cells in a given network; or to monitor the status of certain components in a particular storage operation cell (e.g., the amount of storage capacity left in a particular storage device). As a further example, interface 125 may display the cost metrics associated with a particular type of data storage and may allow a user to determine overall and target cost metrics associated with a particular data type, or certain storage operation cell 50 or other storage operation as predefined or user-defined (discussed in more detail below).
  • Storage manager 100 may also include a management agent 130 that is typically implemented as a software module or application program. In general, management agent 130 provides an interface that allows various management components 100 in other storage operation cells 50 to communicate with one another. For example, assume a certain network configuration includes multiple storage operation cells 50 adjacent to one another or otherwise logically related in a WAN or LAN configuration (not shown). With this arrangement, each storage operation cell 50 may be connected to the other through each respective interface module 125. This allows each storage operation cell 50 to send and receive certain pertinent information from other storage operation cells 50, including status information, routing information, information regarding capacity and utilization, etc. These communication paths may also be used to convey information and instructions regarding storage operations.
  • For example, a management agent 130 in first storage operation cell 50 may communicate with a management agent 130 in a second storage operation cell 50 regarding the status of storage operations in the second storage operation cell. Another illustrative example includes the case where a management agent 130 in first storage operation cell 50 communicates with a management agent 130 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 130 contained in the storage manager 100.
  • Another illustrative example is the case where management agent 130 in the first storage operation cell 50 communicates directly with and controls the components in the second storage operation cell 50 and bypasses the storage manager 100 in the second storage operation cell. If desired, storage operation cells 50 can also be organized hierarchically such that hierarchically superior storage operation cells control or pass information to hierarchically subordinate storage operation cells or vice versa. More information regarding hierarchical organization of operation storage cells 50 will be provided below.
  • Storage manager 100 may also maintain an index cache, a database, or other data structure 111. The data stored in database 111 may be used to indicate logical associations between components of the system, user preferences, management tasks, or other useful data. As further described herein, some of this information may be stored in a media agent database or other local data store according to some embodiments. For example, the storage manager 100 may use data from database 111 to track logical associations between media agents 105 and storage devices 115.
  • Generally speaking, a media agent 105 may be implemented as software module that conveys data, as directed by a storage manager 100, between a client computer 85 and one or more storage devices 115 such as a tape library, a magnetic media storage device, an optical media storage device, or any other suitable storage device. In one embodiment, media agents 105 may be communicatively coupled with and control a storage device 115 associated with that particular media agent. A media agent 105 may be considered to be associated with a particular storage device 115 if that media agent 105 is capable of routing and storing data to particular storage device 115.
  • In operation, a media agent 105 associated with a particular storage device 115 may instruct the storage device to use a robotic arm or other retrieval means to load or remove a certain storage media, and to subsequently archive, migrate, or restore data to or from that media. Media agents 105 may communicate with a storage device 115 via a suitable communications path such as a SCSI or fiber channel communications link. In some embodiments, the storage device 115 may be communicatively coupled to a media agent 105 via a Storage Area Network (“SAN”).
  • Each media agent 105 may maintain an index cache, a database, or other data structure 110 which stores index data generated during backup, migration, and restore and other storage operations as described herein. For example, performing storage operations on MICROSOFT EXCHANGE® data may generate index data. Such index data provides a media agent 105 or other external device with a fast and efficient mechanism for locating data stored or backed up. Thus, in some embodiments, a storage manager database 111 may store data associating a client 85 with a particular media agent 105 or storage device 115, for example, as specified in a storage policy, while media agent database 110 may indicate where specifically the client 85 data is stored in storage device 115, what specific files were stored, and other information associated with storage of client 85 data. In some embodiments, such index data may be stored along with the data backed up in a storage device 115, with an additional copy of the index data written to index cache 110. The data in index cache 110 is thus readily available for use in storage operations and other activities without having to be first retrieved from the storage device 115.
  • In some embodiments, certain components may reside and execute on the same computer. For example, in some embodiments, a client computer 85 such as a data agent 95, a media agent 105, or a storage manager 100 coordinates and directs local archiving, migration, and retrieval application functions as further described in U.S. Pat. No. 7,035,880. This client computer 85 can function independently or together with other similar client computers 85.
  • FIG. 2 presents a generalized 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 in accordance with an embodiment of the present invention. It will be understood that although the storage operation cells generally depicted in FIG. 2 have different reference numbers from the storage operation cell 50 shown in FIG. 1, these storage operation cells may be configured the same as or similar to the storage operation cell 50 depicted in FIG. 1.
  • As shown, the system illustrated in FIG. 2 may include a master storage manager component 135 and various other storage operation cells. As shown, the illustrative embodiment in FIG. 2 includes a first storage operation cell 140, a second storage operation cell 145, a third storage operation cell 150, a fourth storage operation cell 155, a fifth storage operation cell 160, and an nth storage operation cell 165. However, it will be understood this illustration is only exemplary and that fewer or more storage operation cells may be present or interconnected differently if desired.
  • Storage operation cells, such as the ones shown in FIG. 2 may be communicatively coupled and hierarchically organized. For example, a master storage manager component 135 may be associated with, communicate with, and direct storage operations for, a first storage operation cell 140, a second storage operation cell 145, a third storage operation cell 150, a fourth storage operation cell 155, a fifth storage operation cell 160, and an nth storage operation cell 165. In some embodiments, the master storage manager component 135 may not be part of any particular storage operation cell. In other embodiments (not shown), master storage manager component 135 may itself be part of a certain storage operation cell.
  • Thus, in operation, master storage manager component 135 may communicate with a management agent of the storage manager of the first storage operation cell 140 (or directly with the other components of first storage operation cell 140) with respect to storage operations performed in the first storage operation cell 140. For example, in some embodiments, master storage manager component 135 may instruct the first storage operation cell 140 with certain commands regarding a desired storage operation such as how and when to perform particular storage operations including the type of operation and the data on which to perform the operation.
  • In other embodiments, master storage manager component 135 may track the status of its associated storage operation cells, such as the status of jobs, system components, system resources utilization, and other items, by communicating with manager agents (or other components) in the respective storage operation cells. Moreover, master storage manager component 135 may track the status of its associated storage operation cells by receiving periodic status updates from the manager agents (or other components) in the respective storage operation cells regarding jobs, system components, system resources, and other items. For example, master storage manager component 135 may use methods to monitor network resources such as mapping network pathways and topologies to, among other things, physically monitor storage operations and suggest, for example, alternate routes for storing data as further described herein.
  • In some embodiments, master storage manager component 135 may store status information and other information regarding its associated storage operation cells and other system information in an index cache, database 137 or other data structure accessible to mater storage manager component 135. A presentation interface included in certain embodiments of master storage manager component 135 may access this information and present it to users and system processes with information regarding the status of storage operations, storage operation cells, system components, and other information of the system.
  • As mentioned above, storage operation cells may be organized hierarchically. With this configuration, storage operation cells may inherit properties from hierarchically superior storage operation cells or be controlled by other storage operation cells in the hierarchy (automatically or otherwise). Thus, in the embodiment shown in FIG. 2, storage operation cell 145 may control or is otherwise hierarchically superior to storage operation cells 150, 155, 160, and 165. Similarly, storage operation cell 155 may control storage operation cells 160 and 165. Alternatively, in some embodiments, storage operation cells may inherit (or otherwise be associated with) storage policies, storage preferences, storage metrics, or other properties or characteristics according to their relative position in a hierarchy of storage operation cells.
  • Storage operation cells may also be organized hierarchically according to function, geography, architectural considerations, or other factors useful or desirable in performing storage operations. For example, in one embodiment, storage operation cell 140 may be directed to create snapshot copies of primary copy data, while storage operation cell 145 may be directed to create backup copies of primary copy data or other data.
  • As another example, storage operation cell 140 may represent a geographic segment of an enterprise, such as a Chicago office, and storage operation cell 145 may represents a different geographic segment, such as a New York office. In this example, the second storage operation cells 145, 150, 155, 160, and 165 may represent departments within the New York office. Alternatively, these storage operation cells could be further divided by function performing various storage operations for the New York office or load balancing storage operations for the New York office.
  • As another example, and as previously described herein, different storage operation cells directed to different functions may also contain the same or a subset of the same set of physical devices. Thus, one storage operation cell in accordance with some embodiments of the present invention may be configured to perform SRM operations (such as a QSM cell in the COMMVAULT QINETIX system) and may contain the same, similar or a subset of the same physical devices as a cell configured to perform HSM or other types of storage operations. Each storage operation cell may, however, share the same parent or, alternatively, may be located on different branches of a storage operation cell hierarchy tree. For example, storage operation cell 140 may be directed to SRM operations whereas storage operation cell 155 may be directed to HSM operations. Similarly, storage operation cell 150 may be configured to perform SRM operations and storage operation cell 155 may be configured to perform HSM operations. Those skilled in the art will recognize that a wide variety of such combinations and arrangements of storage operation cells are possible to address a broad range of different aspects of performing storage operations in a hierarchy of storage operation cells.
  • In some embodiments, hierarchical organization of storage operation cells facilitates, among other things, system security and other considerations. For example, in some embodiments, only authorized users may be allowed to access or control certain storage operation cells. A network administrator for an enterprise may have access to many or all storage operation cells including master storage manager 135. But a network administrator for the New York office, according to a previous example, may only have access to storage operation cells 145-165, which form the New York office storage management system.
  • The hierarchical organization of storage operation cells may facilitate storage management planning and decision-making. For example, in some embodiments, data and other information related to HSM storage operation cells and SRM storage operation cells may be normalized (e.g., converted into a common format with normalized identifiers and other information) and combined by a master storage manager component or other hierarchically superior (or, if desired, hierarchically subordinate) component, and a user of master storage manager component 135 may view the status of some or all jobs in associated storage operation cells as well as the status of each component of the storage operation cells present in the system. Users may then plan and make decisions based on this global data. For example, a user may view high-level information regarding storage operations for the entire system, such as job status, component status, resource status (such as network pathways, etc.), and other information. This may be done from an SRM perspective to view primary copy information or from an HSM perspective to view secondary copy information. A user may 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.
  • In other embodiments master storage manager component 135 may alert a user such as a system administrator when a particular resource is unavailable or congested. For example, a particular storage device might be full or require additional media. As another example, a master storage manager component may use information from an HSM storage operation cell and an SRM storage operation cell to present indicia or otherwise alert a user or otherwise identify aspects of storage associated with the storage management system and hierarchy of storage operation cells.
  • NON 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, master storage manager component 135 (or another storage manager within the hierarchy of storage operation cells) may utilize the global data regarding its associated storage operation cells to suggest solutions to such problems when they occur (or act as a warning prior to occurrence). For example, master storage manager component 135 may alert the user that a storage device or other resource in a particular storage operation cell is full or otherwise congested, and then suggest, based on job and data storage information contained in its database, an alternate storage device or resource to migrate to the storage operation cell. Other types of corrective actions based on such information may include suggesting an alternate data path to a particular storage device, or dividing data to be stored among various available storage devices as a load balancing measure or to otherwise optimize storage or retrieval time. In some embodiments, such suggestions or corrective actions may be performed automatically, if desired.
  • Examples of the types of information that may be monitored for an application such as MICROSOFT EXCHANGE® include:
  • File Systems and File Analysis
      • Distribution by file types
      • Distribution by file sizes
      • Distribution by modification time/access time
      • Distribution by owner, etc.
      • Capacity and Asset Reporting
      • By host
      • By disk
      • By partitions
      • Availability Reporting
      • Disks
      • Hosts
      • Applications
  • Message Level
      • Distribution across mailboxes
      • By Message attachment type
      • By Message age
      • Data Migration report
      • Usage Reporting
      • By Storage Group
      • By Store
      • By Mailbox, etc.
  • In alternate embodiments, HSM and SRM components may be aware of each other due to a common database or metabase of information, which may include normalized data. Therefore, in those embodiments there is no need for such information to pass through a master storage manager as these components may be able to communicate directly with one another. For example, storage operation cell 150 may communicate directly with storage operation cell 165 and vice versa. This may be accomplished through a direct communications link between the two (not shown) or by passing data through intermediate storage operation cells, such as storage operation cells 145-160 in this case.
  • FIG. 3 illustrates a block diagram of a hierarchically organized group of storage operation cells in a system to perform SRM and HSM storage operations on electronic data in a computer network in accordance with various illustrative implementations for migrating resources between storage operation cells in accordance with the present invention. As will be further understood from the following description, however, implementing storage operation cell component migration according to the present invention is not limited to having a particular organization of storage operation cells, nor to having storage operation cells with HSM and/or SRM component functionality. For instance, the storage operation cells may be organized non-hierarchically or hierarchically, and may be implemented with or without a storage operation cell having a storage manager that functions as a master storage manager. As a further example, the network is not required to include a storage operation cell that performs SRM operations and not HSM storage operations.
  • As shown, the network in FIG. 3 includes a first storage operation cell 170, a second storage operation cell 173, a third storage operation cell 175, and a fourth storage operation cell 180. First storage operation cell 170 includes a client 185 in communication with a primary volume 190 storing data, and a storage manager component 195 in communication with a storage manager database 200 and with client 185. Second storage operation cell 173 includes a client 186 in communication with a primary volume 191, a media agent 206 in communication with a secondary storage media 211 and a secondary storage media 213, clients 236-244 in communication with respective primary volumes (not shown for clarity of illustration), media agents 208, 210, and 212 in communication with one or more of storage volumes 211, 213, 217, and 219, and storage manager 196 in communication with each of the media agents 206, 208, 210, and 212 in storage operation cell 173. Third storage operation cell 175 includes clients 246 and 250 in communication with respective primary volumes (not shown), media agents 214, 216, and 218 in respective communication with secondary storage media 221, 223, and 225, and storage manager 260 in communication with each of the media agents in storage operation cell 175. Fourth storage operation cell includes a master storage manager component 215 in communication with a master storage manager database 220.
  • With regard to FIG. 3, databases 220 and 200 respectively associated with storage managers 215 and 195 are expressly depicted, storage managers 196 and 260 are similarly each in communication with a respective database; however, these databases are not separately depicted and may be considered as being included in storage managers 196 and 260, in accordance with the illustrative storage manager 100 of FIG. 1. Additionally, in this embodiment, each depicted client device in storage operation cells 173 and 175 is in communication with the storage manager within its storage operation cell, but connecting lines are not shown for clarity of illustration. Depicted lines connecting media agents with clients and with storage volumes represent possible data flow paths according to the illustrative configuration. Thus, a given media agent may be operative in storage operations (e.g., backup, archiving, restoring) with respect to any storage volume and any client to which it is illustrated as being connected by a solid line. Depicted lines connecting a media agent to a storage manager represent control information and/or metadata paths.
  • The first storage operation cell 170 may be configured to perform a particular type of storage operation, such as SRM storage operations. For example, the first storage operation cell 170 may monitor and perform SRM-related calculations and operations associated with primary copy data. Thus, the first storage operation cell 170 includes a client component 185 in communication with a primary volume 190 for storing data. For example, client 185 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 190. Storage manager component 195 may contain 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 190. Storage manager 195 may track and store this and other information in storage manager database 200 which may include index information. For example, in some embodiments, storage manager component 195 may track or monitor the amount of available space and other similar characteristics of data associated with primary volume 190.
  • In some embodiments, as further described herein, storage manager component 195 may also issue alerts or take other actions when the information associated with primary volume 190 satisfies certain criteria, such as alert criteria, criteria defined in a storage policy, a threshold, such as a user defined threshold or default threshold, or other criteria. In some embodiments, action may be taken or alerts sent if a characteristic relating to a storage manager, media agent, database, storage device, storage library, client or other component matches the criteria. Such criteria may relate to resource characteristics, including, for example, network bandwidth utilization, resource capacity used or available, time period between storage operations, scheduling conflicts, processor loads, or other characteristics relating to performing a storage operation.
  • Second storage operation cell 173 may be directed to another type of storage operation, such as HSM storage operations. For example, the second storage operation cell 173 may perform backups, data 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 disk storage (i.e., primary storage) to less expensive storage such as tape storage (i.e., secondary storage).
  • Thus, the second storage operation cell 173 includes client component 186 in communication with the primary volume 191 storing data. In some embodiments, client component 186 and primary volume 191 are the same physical devices as the client component 185 and primary volume 190 in the first storage operation cell 170. Similarly, in some embodiments, the storage manager component 196 and its associated database (not shown, and which may include index information) in the second storage operation cell 173 are the same physical devices as the storage manager component and index in the first storage operation cell 170. Storage manager component 196, however, typically also contains HSM modules or other logic associated with the second storage operation cell 173 directed to performing HSM storage operations on primary volume 191 data.
  • Storage operation cell 173 therefore may also contain media agent 206 and a secondary storage media 211 configured for performing HSM-related operations on primary copy data stored on primary volume 191. For example, storage manager 196 may migrate primary copy data from primary volume 191 to secondary volume 211 using media agent 206. Storage manager 196 may also track and store information associated with primary copy migration and other similar HSM-related operations in its storage manager database (not shown). For example, in some embodiments, storage manager component 196 may direct HSM storage operations on primary copy data according to a storage policy associated with the primary copy 191 and stored in an index. In some embodiments, storage manager 196 may also track where primary copy information is stored, for example in secondary storage 211. Storage manager 196, media agents 206, 208, 210, and 212, and secondary storage media 213 and 217 may also be configured to perform such HSM storage operations with respect to primary copy data associated with clients 236, 238, 240, 242, and 244. Further, storage operation cell 175 may similarly be configured for performing such HSM storage operations with respect to primary copy data associated with clients 246, 248, and 250.
  • NOM Storage operation cell 180 may include a master storage manager 215 and a master storage manager 220. In some embodiments (not shown), additional storage operation cells may be located hierarchically in between storage operation cell 180 and storage operation cells 170, 173, and 175. In some embodiments, additional storage operation cells hierarchically superior to operation cell 180 may also be present in the hierarchy of storage operation cells.
  • In some embodiments, storage operation cells 170, 173, and 175 may be connected by communications link 197, which may be any suitable communications link such as a fiber channel or SCSI connection that allows storage operation cells 170, 173, and 175 to communicate directly with one another (i.e., without necessarily directly or indirectly involving storage operation cell 180). Such communication between cells 170 and 173 may be accomplished, for example, by storage manager 195 communicating with storage manager 196 via link 197. This allows storage operation cells 170 and 173 to share information such as status or operational characteristics with one another such as availability on primary or secondary storage, trigger events based on such information, etc. This allows for the direct transfer of stored data to and from the storage operation cells (via link 197) without the need to communicate with or pass data through master storage manager 215.
  • Storage operation cell 180 is also generally directed to performing certain types of storage operations, such as integration of SRM and HSM data from other storage operation cells, such as storage operation cells 170, 173, and 175. In some embodiments, fourth storage operation cell 180 also performs other types of storage operations and might also be directed to HSM, SRM, or other types of storage operations for other reasons such as convenience, hardware allocation, media managers, administrative or organization reasons, etc.
  • FIG. 4 is a schematic depiction of migration of various components or resources, such as clients, media agents, primary storage, secondary storage databases, storage managers or other components from one storage operation cell to another storage operation cell in accordance with certain aspects of the present invention. As shown, this may include, for example, movement of certain resources from storage operation cell 173 to storage operation cells 170 and 175 in the illustrative configuration of FIG. 3. As described herein, migration of storage operation cell resources may be used to optimize, consolidate, reorganize or otherwise reconfigure or transfer storage resources or components within the system. As mentioned above, migration of resources typically involves logical reassignment of certain resources, but may, in certain situations, also involve physical movement.
  • Logical migration may include associating or assigning a resource to another storage operation cell. This may involve logically reassigning the resource to another storage operation cell by transferring the management information associated with that resource, as well as reassigning that resource itself to another storage operation cell. For example, a media agent may be transferred from one storage operation cell to another by transferring management information regarding the media agent to the new storage operation cell and logically reassigning the media associated with that agent to the new storage operation cell (without any actual physical movement). Thus, for example, storage manager database entries may be copied and repopulated with new links, path, and address information, etc. as necessary to complete the transfer and bring the transferred resources to a fully operational state within the new storage operation cell.
  • Migration of resources may be initiated by a storage manager, such as a master storage manager, or other component, or by a user, according to user selections or preferences. For example, a user may identify certain resources within a storage operation cell that are operating beyond a specified capacity or that are underutilized, and mark those resources as possible migration candidates (e.g., placed in a migration pool).
  • Alternatively, a storage manager, or other system component, may monitor storage operation cells to determine whether storage operation cell resources are performing adequately or as desired, e.g., within a threshold or according to an operating criteria or characteristic, or otherwise detect that storage operation cell configurations are performing below an optimal, required or desired level. Based on acquired information, resources may be migrated to provide load balancing, promote efficient use of resources (e.g., storage media), improve data throughput, or provide other resource optimization. Resources may also be migrated and/or combined for convenience or administrative or organizational purposes (e.g., merge or close physical offices etc.).
  • In general, migrating a resource from a source storage operation cell to a target storage operation cell may involve logically associating the migrated resource with target storage operation cell (without necessarily requiring actual physical movement). Information relating to the logical association(s) of migrated components may be stored in an index, metabase, or database, for example database 220 (e.g., a storage manager database). Such logical associations may include pointers to a new storage operation cell, a network pathway, or other indication that a storage operation cell resource has migrated. For example, if a client is moved from one storage operation cell to another, information from the source storage operation cell including information from a storage manager and/or associated media agent(s) may also be migrated to the appropriate resources in the target storage operation cell; and a pointer or other referential element may be placed in the source storage operation cell to indicate the client's new location.
  • In some embodiments, substantially all of this information may be moved to the target storage operation cell from the source storage operation cell. For example, some or all information such as management information in an index or metabase may be migrated along with the resource so the resource may be reconstituted and resume normal operation in the target storage operation cell. This may include both data and media (e.g., media agents and their associated media libraries).
  • However, in certain circumstances, some or all of this management information may remain in the source storage operation cell. For example, a client may be moved from one storage operation cell to another, but one or more storage devices that store data from that client may remain in the source storage operation cell. In this case, this data from that client may remain in the source storage operation cell along with associated management information.
  • In the case where data needs to be retrieved from the source storage operation cell, the target storage operation cell may include a pointer or other reference to the appropriate location in the source storage operation cell. In other embodiments, however, associated storage devices and/or the data itself associated with the migrated client may be migrated to the target storage operation cell, in which case substantially all management information may be also be migrated to the target storage operation cell. In yet other embodiments, management information may remain in both storage operation cells with both sets of information updated as changes occur. In yet other embodiments, data may be present in one storage operation cell with the client in a different storage operation cell, with pointers and references at the storage managers of each cell for interoperation.
  • In one example, a storage policy may indicate that a storage operation, such as a secondary copy operation is to be performed on a daily basis for a particular client using a particular media agent and storage device. However, if the client is removed from the network and no longer producing data on which a storage operation is performed, the media agent and storage device associated with storage operations for that client may be migrated to another storage operation cell for other uses (even if the media agent is still associated with clients in the original cell). Alternatively, if a client is reassigned within a network from one department or domain to another, the associated media agent and storage device may be reassigned or referenced to a storage operation cell that is already associated with the other department or domain, or even reassigned or referred to some other storage operation cell.
  • In another example, clients may be added to an existing storage operation cell, and may generate data that exceeds media capacity of one or more storage devices in a storage operation cell. In this example, a storage device from another storage operation cell may be identified to migrate to the storage operation cell to provide additional media capacity, or alternatively, one or more of the clients may be migrated to another storage operation cell that includes sufficient storage capacity to handle the load. In other embodiments, a client may be split or partitioned between two or more storage operation cells. In this case, the data agent associated with the client may be registered for operation in those storage operation cells as well, with some data in a first storage operation cell and some data in other storage operation cells.
  • Other situations causing bottlenecks, underutilization, or over-utilization of storage management resources may also arise in which it may be useful or desirable to migrate or reassign one or more resources to improve storage operation performance.
  • In FIG. 4, the outline of the migrated devices or components and the changed data/information communication paths in the source storage operation cell 173 are depicted by dashed lines to indicate their migration, transfer, or removal from the source storage operation cell, and the migrated devices or components (identified by identical reference numerals) are depicted by solid lines in the target storage operation cell (i.e., cells 170 and 175) to indicate their migration to that target storage operation cell.
  • More specifically, as shown, client 240 and data from storage manager 196 may be migrated from source storage operation cell 173 to target storage operation cell 175 (including storage manager 260) such that media agent 216 (or other media agent(s) of storage operation cell 175) is operative in managing data movement (e.g., for a storage operation, such as a backup, recovery, or migration) between primary storage volume of client 240 and secondary storage media 223. Transferring client 240 may occur and be desirable, for example, in the event that client 240 is moved from one enterprise department to another department, or in the event that media agent 210 previously associated with client 240 becomes overburdened, or is otherwise unavailable to perform specified functions. It will be understood that client 240 may be reassigned without any physical movement of client 240, but rather by movement of management information and logical reassignment within the system. Such an operation may sometimes be referred to herein as “migration” of one or more resources from one storage operation cell to another.
  • Continuing with the embodiment illustrated in FIG. 4, client 244 together with its associated media agent 212 may be migrated from source storage operation cell 173 to storage operation cell 175, with media agent 212 subsequently being associated with secondary storage media 225 to manage data movement between client 244 (i.e., its primary storage volume) and secondary storage media 225. Client 244 its associated storage manager data and possibly its associated media agent 212, and media library and any other necessary or useful routing or management data may be migrated or transferred, for example, in the event that a storage volume 219 reaches a capacity that exceeds a threshold or criteria, or in another scenario in which it is desirable to migrate client 244 and media agent 212.
  • Continuing with the illustrative embodiment, client 186 (including its primary storage volume 191 ans storage manager data) may be migrated from source storage operation cell 173 to storage operation cell 175 such that media agent 214 (or other media agent in cell 175) is operative in managing data movement (e.g., for a storage operation, such as a backup, recovery, or migration) between primary storage volume 191 and secondary storage media 221. Client 186 and its associated storage manager data may be migrated or transferred, for example, because media agent 214 is underutilized in storage operations and has capacity which meets a threshold or criteria, or media agent 206 is overburdened and exceeds a bandwidth threshold or criteria, or satisfies other criteria in which it may be desirable to transfer client 186.
  • Moreover, media agent 206 may be migrated from source storage operation cell 173 to storage operation cell 170 and associated with secondary storage media 227 to conduct data between client 185 or other clients (not shown) and secondary storage media 227, providing for a storage operation, or a backup of data on primary storage volume 190. Alternatively or additionally, media agent 206 may remain associated with secondary storage media 211 to direct a storage operation of a primary storage volume 190 thereto, and, in such cases, secondary storage media 211 may also be migrated to storage operation cell 170, and its association with media agent 208 may be removed. Such migration may occur, for example, in the event that media agent 206 has a characteristic such as bandwidth, meeting a threshold or criteria to perform storage operations relating to client 185 and media agent 208 has a characteristic, such as bandwidth, to take over control of storage media 211. In other situations, it may be desirable to move client 185 to another storage operation cell, without media agent 206, and reassign client 185 to a new media agent in the new storage operation cell. This may involve migrating some or all of management from agent 206 and any associated storage manager information associated with the client as further described herein.
  • It will be understood, the migration of the resources as illustrated in FIG. 4 may be based on the following illustrative situation prior to migration. With regard to media agent 206, in addition to handling storage operation data movement between primary storage volume 191, media agent 206 may also be operative in performing storage operations for primary storage volume 190 of client 185 via link 197. The workload of handling data movement in a storage operation for both of these primary storage volumes may overload media agent 206 and cause congestion. Likewise, clients 238, 240, and 242 may over utilize media agent 210, thus causing congestion and delay, for example, in network pathways to media agent 210, and also rapidly consume the storage capacity of storage media 217 and 219. Further, performing a storage operation of client 244 via media agent 212 increases the storage capacity consumption rate of media 219.
  • In this example, load balancing techniques and reallocation within a the storage operation cell alone may not adequately mitigate these problems, or may not represent an optimal solution compared to possibly migrating one or more resources to another storage operation cell (with or without migrating resources within the storage operation cell).
  • Load redistribution may be addressed according to the resource migration described above in connection with FIG. 4. Thus, client 186 (with primary storage volume 191) and client 244 and their associated data may be migrated to storage operation cell 175, assigning each of these clients to a respective media agent and associated secondary storage that will not be overloaded or over-utilized by the addition of these clients. With the migration of client 186, media agent 206 may now be available to manage and control storage operations for client 185, and thus it may be migrated to storage operation cell 170. Because of the addition of media agent 206 and secondary storage media 227 (and/or, in alternative implementations, secondary storage media 211) into storage operation cell 170, HSM components may be added to storage manager 195 to allow for HSM operations, including collection and reporting of HSM data.
  • To further reduce the consumption rate of storage media 219, client 244 may be migrated to storage operation cell 175. Because media agent 212 is associated with client 244, it may be migrated to storage operation cell 175 with client 244 without requiring migration of other clients connected thereto, and without requiring any migration of databases (e.g., indexes) that media agent 212 would maintain for such other clients. In alternative implementations, a media agent already located in storage operation cell 175 may be assigned to client 244, or a new media agent for client 244 may be installed and configured in storage operation cell 175. In either case, storage preferences, storage policies or other preferences provided for a storage operation cell, media agent or other component of a storage operation cell may be retained by the resource or component after migration to a target storage operation cell, or alternatively the preference may be overwritten with new preferences associated with the target storage operation cell.
  • Accordingly, it will be understood that the ability to migrate or transfer resources across storage operation cells provides for greater flexibility in solving load balancing problems, providing robust failover solutions, and providing means by which systems efficiency may be monitored and improved providing, for improved performance, reliability, and resource utilization. Such load balancing or failover problems can be monitored and remedied on a system-wide or global basis, as well as on an individual storage component or resource level.
  • Referring now to FIG. 5, a flow chart illustrating some of the steps for migrating one or more resources from a source storage operation cell to a target storage operation cell is provided in accordance with an embodiment of the present invention. As noted above, resource migration may be implemented or initiated according to a process including any of the following: (1) one or more steps executed automatically in response to user input; (2) one or more steps executed automatically without user input in accordance with certain system operating policies or guidelines; or (3) one or more manually executed steps with certain steps occurring automatically. It will be understood that the process described with reference to FIG. 5 is merely illustrative, and that each operation or series of operations may be implemented automatically, manually, or a combination thereof.
  • For example, a user may initiate the resource migration process by interacting via a GUI (or other user interface) with a network resource management system that provides information and functions for storage operation cell resource allocation (step 505). Resource management may be implemented as one or more software modules or applications that may be integrated with, or be a component of, for example, the HSM and/or SRM software. At least some of the information monitored or generated by the HSM and/or SRM components, or other storage manager components may be used by the network resource management system for allocating or migrating resources. For instance, corrective actions recommended by the HSM component may be used by the resource management system in determining whether migration of a resource to another storage operation cell should be recommended.
  • In another example, a storage manager or other system component may receive information relating to, or may periodically query storage operation cell or system resources, or consult an index or database or storage policy regarding storage operation cell or system resources to determine current and future scheduled storage operation cell and resource utilization, and initiate the resource migration process, (step 505). Such periodic resource query may be the system checks or tests described in commonly owned U.S. patent application Ser. No. 11/269,513, titled SYSTEM AND METHOD FOR MONITORING A STORAGE NETWORK, filed Nov. 7, 2005. Thus, a storage manager or other system component may determine current and/or predicted resource needs or requirements for a storage operation cell, for example, based on a storage policy or other information and allocate storage operation cell resources accordingly.
  • The network resource management system, such as a storage manager component, or other component, may identify one or more resources to be moved or migrated from a given storage operation cell based, for example, on system operating conditions, user preference, and/or combination of the two, which may include additional forecasting or provisioning analysis (step 507). For instance, the network resource management system may provide information (e.g., component storage capacity, rate of storage media consumption, scheduled storage operations, network data pathway load metrics, processor loads, and other performance metrics) concerning resources (e.g., clients, media agents, primary or secondary storage media, data paths, or other components) within each of the storage operation cells. Alternatively, in the case where migration of resources is accomplished automatically, such information may be obtained by a storage manager, master storage manager or other system component to calculate performance metrics and determine and/or identify storage operation cell resources for migration. This may be performed on a substantially global basis, and a master storage manager component or other management component may analyze operations of the storage operation cells in a network and make recommendations and/or suggestions for resource migration based on this information (e.g., based on certain system optimization or data routing, management, and movement algorithms, etc.).
  • The resource management system or storage manager may also generate alerts identifying operating conditions that require attention in the storage operation cells, such as a pathway or processor bottleneck, one or more storage operations that exceed a threshold relating to system performance which may be remedied by resource reallocation (e.g., as further described in FIG. 6). The network resource management system or storage manager may also recommend the migration or reallocation of specific resources, and may also identify one or more potential target locations (within or without the source storage operation cell) for the migration or reallocation. This may occur, for example, in recognition of impending hardware, software, or other system failures, such the network may be may correct problems, prior to occurrence to maintain or preserve system operation and data protection criteria and/or prevent service degradation (e.g., a “self-healing” capability in view of identified and impending component failures).
  • The alerts and/or recommendations for migrating one or more resources generated by various storage managers (or other storage components) may be based on analysis of certain information (e.g., storage capacity, rate of storage media consumption, data path load metrics, and other performance metrics or other system diagnostics) concerning resources (e.g., clients, media agents, secondary storage media, data paths) within its storage operation cell including existing configurations of the storage operation cell, schedule policy or other preferences in advance of a storage operation.
  • Additionally or alternatively, the network resource management system may itself analyze information received or acquired directly or indirectly from the storage managers. For instance, such information from each storage operation cell may be stored on a globally accessible database. In a hierarchical configuration, such as shown in FIG. 3, this information from each storage operation cell may be communicated to, and stored in the database of, the master storage manager. The network resource management system may then access and analyze this information to identify situations for which resource migration, or other corrective or preventative actions, may be recommended. Thus, the network resource migration system may facilitate identifying resources to be migrated. It will be understood, however, that in some situations the decision to migrate a resource across storage operation cells may be identified via the resource management system based on specific performance scenarios, configurations, resource characteristics or other basis.
  • Based on the information, alerts, or recommendations generated by the system, or based on other considerations, the user may select via the GUI (or other interface means) a resource located in a source storage operation cell for assignment or re-assignment to a specified target storage operation cell (step 509). In some embodiments, the selection may be made automatically by the system based on system operating conditions and metrics as determined by performance algorithms or other analysis software. In such an embodiment, the resource automatically selected may be identified as having appropriate utilization for migration to a target storage operation cell. Possible resources that may be selected include a client, a media agent, storage media, transmission resources and a datapath (i.e., a combination of media agent and storage media and transmission path used by the storage policy to perform a data protection operation), or other system component.
  • In some embodiments, prior to assigning a resource to a target storage operation cell, a storage manager or other system component may direct that storage operations be quiesced or temporarily ceased and that certain confirmatory test(s) be performed to verify that the anticipated or intended storage operations can be performed in the new proposed storage operation cell configurations before allowing the new storage operation cell configurations to be brought online. In some embodiments, when the storage operations are buffered or quiesced, a storage manager or other system component may observe the source and target storage operation cells and any components which may be associated or affected by the migrated resource to determine whether the migration is operating as anticipated.
  • In other embodiments, a storage manager or other system component may simulate the new resource configurations of the source and target storage operation cell in advance of the migration, to determine whether the configuration is desirable and likely to achieve the desired goal. The simulation may take into account existing information relating to each storage operation cell resource and storage operation scheduling or other job related information which may be obtained from a storage policy. This may include simulation of one or more proposed configurations by analysis or optimization software, and choosing the best one based on specified criteria through the use of, for example, a selection algorithm (or user input).
  • The system may then provide for moving management information associated with each selected resource (and stored in the source storage operation cell storage manager) from the source storage manager to the target storage manager (step 511). This may include any management information associated with the migrated resource such as index information associated with a media management component, metadata associated with the resource or other information. The communication of this information may occur, for example, directly between storage managers of the source and target storage operation cells, or indirectly through one or more intermediary storage managers, which may include a master storage manager.
  • In some embodiments, a copy of all or part of the management information may be physically transferred to the target storage manager. By way of example, when migrating a client, the management information that is transferred to the target storage operation cell includes media records, archive records, application records, job history, source and target network pathway information and some or all storage policy criteria for that client.
  • The transfer of this information may be accomplished by first identifying or obtaining the information in the source storage operation cell, and copying the information, or merging the information in, to the target storage operation cell. This may include the techniques described in co-pending application entitled “Systems and Methods of Unified Reconstruction in Storage Systems” attorney docket 25693/012, which claims priority from U.S. Provisional Application, 60/752,202, filed Dec. 19, 2005, both of which are hereby incorporated by reference in their entirety.
  • In some embodiments, to identify or obtain this information, the system may create a folder or other destination into which the system stores the information. Then, the target storage operation cell may be confirmed and any other designations that may be required by the system depending on the resource being transferred and/or the target storage operation cell. For example, in migrating a client, it may be required to designate a library and a media agent in the target storage operation cell corresponding to a given storage policy. The system may merge the information stored in the folder into the storage manager of the target storage operation cell.
  • In some embodiments, the management information may be stored to a storage manager database or index. For example, metadata or index information relating to the resource being migrated may be copied to a corresponding media management component in the target storage operation cell. This allows the media management component such as a storage manager, media agent or other component in the target storage operation cell to properly to manage and interoperate with the transferred resource in the same or similar manner as in the source storage operation cell. This typically includes associating the management information with the new storage operation cell and associated components and resources, etc., to ensure interoperation. As mentioned above, the migrated resource (e.g., the client or other component) may be configured to use the storage manager of the target storage operation cell. This resource configuration may occur, for example, prior to transferring the management information in step 511.
  • In the event that the management information is incomplete, or there is an inconsistency or other failure between management information stored by the resource and that stored by the storage manager (step 513), then a restore operation may be performed, such as an incremental restore operation. The restore operation may be implemented in an incremental order, accessing the data and metadata stored on one or more storage media (e.g., from one or more jukeboxes) to restore the data and metadata in reverse time order, thus restoring the metadata in the target storage operation cell (e.g., the metadata stored in the storage manager as well as in clients and/or media agents). As such, information relating to the incremental order may be obtained and restored, (step 515). However, other restore methods may be used, if desired, such as by use of copying data blocks from other locations, checking pointers to resources or other components, according to the method described in co-pending commonly owned U.S. Provisional Patent Application Ser. No. 60/752,202, SYSTEMS AND METHODS FOR UNIFIED RECONSTRUCTION OF DATA IN A STORAGE NETWORK filed Dec. 19, 2005, and its corresponding utility application 25963/012.
  • Once the management information is received by the target storage operation cell and the transferred resource has been configured with respect to its new location (i.e., other resources configured to interoperate with the transferred resource as contemplated) the target storage manager, the transferred resource may be assigned to one or more storage devices (step 517) by specifying, for example, particular mount paths, network pathways, and/or storage media. The assignment may include logically associating one or more pathways and the migrated resource and may be based on past or predicted performance of resources. Such associations may be stored in an index and may be provided using pointers or other methods.
  • The system may perform certain diagnostics to verify the resource migration configuration is as intended and check for errors (step 519). In some embodiments, diagnostics or storage operation cell configuration simulation may be performed on the source and/or target storage operation cell in advance of performing a storage operations on the source or target storage operation cells. This may be done to confirm that the resource migration was successful or to identify problems that may be present in the new configurations (and if identified, take steps to address or repair such problems).
  • Simulations of new configurations may include calculating known characteristics of a migrated resource and other storage operation cell resources together with metrics relating to storage operations to provide a confidence factor that may indicate whether the new configuration will provide the intended benefit. Based on one or more configuration confidence factors, a highest scoring configuration may be selected to be implemented. In the event that a resource is migrated, and the storage manager or other system component determines that yet another configuration would provide enhanced storage performance, the storage manager may analyze this information and initiate the migration process in an iterative fashion.
  • In general, information, including optimization levels, confidence factors, performance improvement, and other information relating to storage operation cell migration is stored and tracked to provide ongoing metrics that may be used to optimize future storage operation cell configurations.
  • FIG. 6 is a flow chart illustrating some of the steps involved in providing dynamic resource allocation in accordance with certain embodiments of the present invention. As will be understood, this dynamic allocation procedure may be used for various dynamic reallocation of resources including, but not limited to, load balancing and/or failover configurations, predictive or corrective analysis reconfiguration, optimizations etc.
  • As shown, the operation of the resources in each storage operation cell may be monitored (step 705) by the system. For instance, the monitored information may include storage capacity, rate of storage media consumption, data path load metrics, and other performance metrics as further described herein. Such system monitoring may be automatic and established, for example, according to a user preference or default template defined by a system administrator setting forth performance or configuration requirements or preferences. The monitoring may be performed as described in commonly owned U.S. patent application Ser. No. 11/269,513, SYSTEM AND METHOD FOR MONITORING A STORAGE NETWORK, filed Nov. 7, 2005.
  • The system may compare or otherwise evaluate the operation of the resource with respect to one or more thresholds (step 710). The thresholds may be established in a storage policy, user preference or other preference as mentioned above. The comparison or evaluation may be based on individual comparisons of monitored metrics, indicia, and other parameters with respective individual thresholds. For example, a threshold for a secondary storage device may be a 70% utilization rate, above which additional media may be required to perform storage operations, or as another example, data path usage exceeding a particular capacity (e.g., 80%).
  • Alternatively, or additionally, comparisons or evaluations may be made based on a metric that is a function (e.g., a use specified weighted sum or average) of monitored quantities and/or other metrics, and which may characterize the overall operating level of an individual resource or the storage operation cell as a whole (e.g., risk of data loss). For example, media usage and predicated growth metrics may be used to determine whether a particular media library can be continued to be used. If, for example. A media library is within a certain time period of being fully utilized, based on media usage and growth metrics (e.g., 3 days), the system may generate a warning, request new media for the library, and determine alternate destinations, should the library become substantially fully utilized (e.g., 95% capacity).
  • In the event that the operation of any resource, or overall storage operation cell operation is within the preset thresholds, (step 715), storage operation cell monitoring may continue on a constant or periodic basis. At some point, the monitoring may indicate that a particular resource exceeds a certain threshold or criteria. The system may identify this resource as a potential resource to reallocate and/or identify other resources to allocate to the storage operation cell to remedy the condition causing the threshold to be exceeded. The potential resources for reallocation may be identified by determining whether resources in other storage operation cells for which the operating thresholds are not exceeded (e.g., underutilized resources) are available for migration (step 720). A list of such resources may be maintained by one or management components within the system and used to identify and consider which resources may be best be used to solve a particular problem. Moreover, a list of under utilized resources may be kept track of as a measure of the “reconfigurability” of system to adapt to changing conditions.
  • For example, if a client, secondary storage device, media agent or other resource in another storage operation cell is operating within a pre-set threshold or in accordance with a criteria, such resources may be available to migrate to the target storage operation cell which includes resources which exceed the preset thresholds. Resource information may be obtained by locating a pool of resources, querying a list of resources, comparing resources with job scheduling, storage policies or other information, pinging or otherwise communicating with resources to determine what resources may be underutilized or over utilized. Cell information may also be obtained by consulting a storage manager, storage manager index, media agent, or other system component.
  • Potential resource reallocations may also include resources physically located within or logically associated with the storage operation cell of the resource to be transferred. In the case that more than one potential reallocation is identified, the system prioritizes them based on considerations such as how well the resource needs can be satisfied, load balancing, data loss risk, as well as other conditions which may be defined in advance by the user.
  • The system may also determine whether other conditions or constraints exist that prevent allocation or transfer of the resource, (e.g., physical location, lack of communications paths, incompatible with one another, impending or actual hardware failure, etc.) (step 725). If the resource cannot be allocated to any of the identified potential target locations, then the system may remove the resource from consideration for migration (step 730). Alternatively, the system may alert a user of the condition and allow the user to review the status of the resources. Also, in advance of an automatic migration, the system may send an alert to an administrator for authorization to perform the resource transfer. The system may then return to step 720 to locate other available resources for allocation. and/or for permission to proceed. In other embodiments, the system may have been preauthorized and the migration may occur substantially automatically.
  • In some embodiments, the system may determine (at step 720) the potential optimization improvement obtained by transferring the resource. For example, a storage manager or other system component may simulate the operation of a target storage operation cell including a component or resource migrated from a located storage operation cell and the operation of the located storage operation cell without the migrated resource. Such simulation may include determining whether the migration will enhance or otherwise improve performance of storage operations and whether the new target and source storage operation cell configurations will continue to function appropriately. This may involve evaluation of certain system performance metrics such as growth rate of target, future scheduled jobs, routing, pathway and temporal constraints, etc. and simulate operation of proposed new configuration(s) for a certain period of time in the future to confirm the desired benefits, are in fact, likely to be achieved. Moreover, multiple such proposed configurations may be evaluated, with the m system (or user) selecting the most desirable option.
  • In the event that the resource can be transferred (step 730), the system may automatically initiate the transfer, (step 735), (e.g., identifying and copying data relating to the resource, merging the data and reconfiguring the resource, updating the index with new logical associations of the new configuration, etc.). Data relating to the resource transfer may be stored in a storage manager or media agent index or database. Following the resource transfer, the system may continue to periodically monitor the operation and resource utilization of the storage operation cells.
  • In accordance with a further embodiment of the present invention, resource reallocation may be based on predictive and other analyses, as will be further understood in view of the illustrative operational flow shown in FIG. 7. As shown, at step 805, the operation of the resources in each storage operation cell may be monitored by the system. The monitored information may include monitoring trends or patterns such as those relating to storage capacity, rate of storage media consumption, data path load metrics, system congestion, data load with respect to time, or any other performance metrics of interest to a system operator. This information may be communicated among storage operation cells, and/or to a master storage manager or other globally accessible location (step 810).
  • The monitored information may be used to perform predictive analysis type operations on a resource, storage operation cell, and/or network wide basis (step 815). Predictions may relate to individual monitored parameters or metrics, or functions thereof, and may involve load analysis, level of data protection, risk criteria of a storage characteristics, cost of storing data, data availability, or other indicia or metrics concerning the resources or the state of storage operations in one or more storage operation cells. In some embodiments, the predictive analysis may be performed according to user, department, project, or other identifier. Such predictions may be performed in order to identify and correct resource shortages and/or system inefficiencies prior to their occurrence.
  • In operation, a user may interact with the system via the GUI (or other interface) to specify and perform a desired analysis, and access and/or generate reports for trends concerning resource allocation. In some embodiments, the user may specify alternative configurations of the resources and perform a predictive analysis for such alternative configurations based on the monitored information for the resources in the current configuration. In some embodiments, the predictive analysis is performed automatically, for example according to user pre-defined analysis; a storage policy; or other preference. Simulations of storage operation cell operations and/or configurations may also be tracked and used to optimize future storage operation cell operations and/or configurations.
  • Trends and patterns obtained in the predictive analysis may be used together with other information such as storage policy information to determine future resource use required to perform storage operations according to the storage policy and to prevent resource exhaustion, overuse and system inefficiencies. For example, the system may predict, based on growth trends within a certain storage operation cell, the need for additional media agents, storage media, transmission paths or other resources (e.g., within a certain time frame). Such resources may be migrated from one storage operation cell to another prior to a lack or overuse of such resources becomes problematic in a given cell. For example, the system may predict an impending shortage of storage media within a certain storage operation cell. The system may consider various options for solving this problem and choose the optimal solution (including adding additional media to existing storage devices). This may involve migrating certain storage devices into the storage operation cell to help alleviate the predicted impending shortage of storage media.
  • Another example involves migrating additional media agents or data paths to a storage operation cell to help prevent bottlenecks or congestion conditions that may be predicted based on current growth or operational trends. For example, the system may predict media agent utilization will exceed a predefined utilization threshold based on client or data growth. In addition to considering other options, the system may locate and migrate (or prepare to migrate) additional media agents and reconfigure associated transmission paths to help alleviate this problem prior to its occurrence or before reaching certain level of severity.
  • Another scenario involves the case where device or component failure rates are trending above acceptable limits (e.g., for media agent hosts, storage manager hosts, storage devices, storage media, etc.). The system may recognize this emerging problem and reassign certain resources such as clients and/or media agents to other transmission paths to minimize this problem, or the potential for this problem. The system may also keep track of certain system configuration and operational information regarding system components such as hardware type, expected lifespan (in various configurations), current deployment time etc. This information may be evaluated to determine the likelihood of failure and system reconfiguration and/or device replacement recommendations or actions may be made based on this information. This may be accomplished using the systems and methods described in co-pending U.S. patent application Ser. No. 11/120,619, HIERARCHICAL SYSTEMS AND METHODS FOR PROVIDING STORAGE A UNIFIED VIEW OF STORAGE INFORMATION, filed May 2, 2005, attorney docket number 4982/54 and U.S. Patent Application Ser. No. 60/752,197 titled SYSTEMS AND METHODS FOR HIERARCHICAL CLIENT GROUP MANAGEMENT, filed Dec. 19, 2005, attorney docket number 4982/102, both of which are incorporated herein by reference.
  • Moreover, the system may monitor client growth in order to predict a point in time when it is desirable to split a storage operation cell into two or more storage operation cells or, alternatively when it may be desirable to combine multiple storage operation cells into one storage operation cell. For example, a storage operation cell may be split into multiple storage operation cells once the number of clients and/or media agent reach a certain threshold point. This point may be determined by certain utilization thresholds set as part of user preferences or system requirements, or may be based on bandwidth of computational abilities of such resources (e.g., predicted inability to or certain resources to handle operations with a certain time frame, etc.).
  • In operation, the system may recognize the need to split storage operation cells and create additional storage operation cells and migrate the appropriate resources into those storage operation cells as described above. Similarly, one or storage operation cells may be combined into a single storage operation cell once resource utilization falls below a certain threshold level. Such consolidation may also occur in the event of physical relocation or reallocation of certain resources to promote the efficient grouping or configuration of resources within the system.
  • Thus, the system may determine the future resources and future storage operation cell configurations required to perform storage operations and compare the resource requirement and storage operation cell configuration to a current resource allocation (step 820), such as existing components associated in one or more storage operation cells. Based on the comparison, resources may be reallocated, (e.g., migrated from a source storage operation cell to a target storage operation cell), either automatically by the system or in response to user specified reallocation, and/or a need for further modifications and/or enhancements to the storage network may be established (step 825). After the resources have been reallocated, the system may monitor trends in storage characteristics so that the trend or pattern predictive information may be dynamically updated accordingly and used to configure storage operation cell configurations on an ongoing basis a described herein (step 830). Accordingly, the system according to one embodiment is able to continuously maintain an optimized and/or fail-safe storage system even as over time the system changes in its usage, resources, capacity, setup etc.
  • Moreover, as mentioned above, resources or data may be migrated from one storage operation cell to another (existing or new) storage operation cell on a temporary or permanent basis. For example, in disaster recovery or other failure scenario, if one or more storage operation cells are experiencing failures, or have lost or are in jeopardy of losing power or will otherwise become unable to continue normal operation because of loss of resources or communications links (e.g., impending natural disaster), the system may create a storage operation cell and migrate resources to that storage operation cell on a temporary basis such that the resources may be returned or otherwise reallocated at some point in the future once the problem has been corrected.
  • As another example, assume a certain storage operation cell has lost power and its resources are currently operating with a backup power supply such as a UPS (uninterruptible power supply). The system may be able to operate for only a limited period of time based on the UPS power. The system may recognize the problem, and create a temporary storage operation cell and migrate clients and data from the storage operation cell that has lost power to the temporary storage operation cell. Such a migration may be scheduled to be substantially complete before the UPS runs out of power. This allows data and other system operations to continue to operate substantially uninterrupted until power can be restored to the original storage operation cell. At this point, data and storage operation cell resources may be returned to the original storage operation cell. In some embodiments, certain resources may be assigned to such temporary storage operation cells to act as a failover storage operation cell in such situations. This may be done to ensure data protection and system robustness even if certain storage operation cells are rendered inoperable by unforeseen or uncontrollable circumstances.
  • Systems and modules described herein may comprise software, firmware, hardware, or any combination(s) of software, firmware, or hardware 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 or methods, 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, and other interfaces suitable for the purposes described herein. Screenshots presented and described herein can be displayed differently as know in the art to input, access, change, manipulate, modify, alter, and work with information. Except to the extent necessary or inherent in the processes themselves, no particular order to steps or stages of methods or processes described in this disclosure, including the Figures, is implied. In many cases the order of process steps may be varied, and various illustrative steps may be combined, altered, or omitted, without changing the purpose, effect or import of the methods described.
  • Accordingly, 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 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.

Claims (28)

1. A method for automatically transferring a resource from a first storage operation cell to a second storage operation cell, the method comprising:
monitoring a first operational characteristic of a first resource in the first storage operation cell wherein the first operational characteristic has an associated first threshold;
identifying a second storage operation cell including a second resource having a second operational characteristic that does not exceed a second threshold,
determining whether the first resource may be transferred to the second storage operation cell such that the transfer is capable of causing the first operational characteristic to remain within the first threshold; and
automatically transferring the first resource to the second storage operation cell if the first operational characteristic is near or exceeds the first threshold.
2. The method of claim 1, wherein the first operational characteristic is representative of a distribution of storage operations within the first storage operation cell.
3. The method of claim 2, wherein the transfer of the first resource to the second storage operation cell promotes a substantially uniform distribution of storage operations within the first storage operation cell.
4. The method of claim 3, wherein load balancing is accomplished, at least in part, by the substantially uniform distribution of data transmission tasks.
5. The method of claim 1, wherein the first operational characteristic is representative of storage media consumption.
6. The method of claim 5, wherein the transfer of the first resource to the second storage operation cell reduces storage media consumption.
7. The method of claim 5, wherein the transfer of the first resource to the second storage operation cell reduces the likelihood of storage media exhaustion.
8. The method of claim 1, wherein the first operational characteristic is representative of overall system performance.
9. The method of claim 8, wherein the transfer of the first resource to the second storage operation cell improves system efficiency.
10. The method according to claim 1, further comprising automatically transferring management information associated with the first resource from the first storage operation cell to the second storage operation cell when the first resource is transferred.
11. The method of claim 1, further comprising monitoring at least one operational characteristic of the first storage operation cell after transferring the first resource.
12. The method of claim 11, further comprising transferring the first resource back to the first storage operation cell if the at least one operational characteristic of the first storage operation cell indicates an undesirable impact in the operation of the first storage operation cell after transferring the first resource.
13. The method of claim 1, further comprising monitoring at least one operational characteristic of the second storage operation cell after transferring the first resource.
14. The method of claim 13, further comprising transferring the first resource back to the first storage operation cell if the at least one operational characteristic of the second storage operation cell indicates an undesirable impact in the operation of the second storage operation cell after transferring the first resource.
15. The method according to claim 1, further comprising quiescing the resource before transferring the first resource to the second storage operation cell.
16. The method according to claim 1, further comprising verifying that the second storage operation cell can accept the first resource prior to transferring the first resource to the second storage operation cell.
17. The method according to claim 16, wherein the verifying further comprises simulating the performance of the first resource in the second storage operation cell.
18. The method according to claim 1, wherein the verifying further comprises simulating the performance of the first storage operation cell without the first resource in the second storage operation cell.
19. The method according to claim 1, further comprising:
performing a predictive analysis to determine an operational trend; and
determining whether to transfer the first resource to the second storage operation cell based on the operational trend.
20. The method according to claim 1, wherein the first and second operational characteristics are any one of the following: network bandwidth utilization, resource capacity used, resource capacity available, time periods between storage operations, scheduling conflicts, or transmission path loads.
21. The method according to claim 1, further comprising before transferring the first resource to the second storage operation cell, analyzing and predicting at least one effect on operational characteristics of the first or second storage operation cell if the first resource is transferred.
22. The method according to claim 1, wherein the identifying includes creating the second storage operation cell.
23. The method according to claim 1, further comprising sending an alert to a user that the resource has been transferred.
24. A computer-readable medium having stored thereon a plurality of sequences of instructions including sequences of instructions which, when executed by one or more processors cause an electronic device to:
monitor a first operational characteristic of a first resource in the first storage operation cell wherein the first operational characteristic has an associated first threshold;
identify a second storage operation cell including a second resource having a second operational characteristic that does not exceed a second threshold,
determine whether the first resource may be transferred to the second storage operation cell such that the transfer is capable of causing the first operational characteristic to remain within the first threshold; and
transfer the first resource to the second storage operation cell if the first operational characteristic is near or exceeds the first threshold.
25. A system for re-allocating a resource in a storage system, comprising:
a first storage operation cell in the storage system, the first storage operation cell including a first resource;
a second storage operation cell in the storage system,
a storage manager that monitors an operational characteristic of the first resource in the first storage operation cell;
wherein in the event that the operational characteristic is near or exceeds a first threshold, the storage manager automatically locates a second storage operation cell, the second storage operation cell, determines whether the first resource may be transferred to the second storage operation cell such that the transfer is capable of causing the first operational characteristic to remain within the first threshold; and
transfers the first resource to the second storage operation cell to maintain the first operational characteristic to remain within the first threshold.
26. A method for re-allocating resources in a storage system, the method comprising:
monitoring an operational characteristic of at least one storage operation cell in the storage system;
identifying a resource in a first storage operation cell;
identifying a second storage operation cell to which the resource may be transferred;
determining a potential effect that a transfer of the resource would have on the operational characteristic of at least one storage operation cell in the storage system; and
in the event that the determined potential effect of a transfer of the resource satisfies a criteria for the storage system, transferring the resource to the second storage operation cell.
27. A system for optimizing performance of storage operations in a storage system including a plurality of storage operation cells and resources, the system comprising:
a storage manager that monitors an operational characteristic of a plurality of storage operation cells in the storage system;
wherein the storage manager identifies a group first resources in a first storage operation cell and identifies a plurality of second storage operation cells to which the group of first resources may be transferred; and
wherein the storage manager determines a potential effect that a transfer of the group of first resources to the plurality of second storage operation cells would have on the performance storage operations, and if the determined potential effect of a transfer of the group of first resources improves the performance of storage operations, the storage manager transfers the group of first resources to the plurality of second storage operation cells.
28. A computer-readable medium having stored thereon a plurality of sequences of instructions including sequences of instructions which, when executed by one or more processors cause an electronic device to:
monitor an operational characteristic of at least one storage operation cell in a storage system;
identify a first resource in a first storage operation cell;
identify a second storage operation cell to which the resource may be transferred;
determine a potential effect that a transfer of the resource would have on the operational characteristic of at least one storage operation cell in the storage system; and
in the event that the determined potential effect of a transfer of the resource satisfies a an operational condition for the storage system, then transfer the resource to the second storage operation cell.
US12/856,995 2005-12-19 2010-08-16 Systems and Methods for Migrating Components in a Hierarchical Storage Network Abandoned US20100312979A1 (en)

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US75219705P 2005-12-19 2005-12-19
US75220105P 2005-12-19 2005-12-19
US75219605P 2005-12-19 2005-12-19
US75219805P 2005-12-19 2005-12-19
US11/639,808 US8661216B2 (en) 2005-12-19 2006-12-15 Systems and methods for migrating components in a hierarchical storage network

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US11/639,808 Continuation US8661216B2 (en) 2005-12-19 2006-12-15 Systems and methods for migrating components in a hierarchical storage network

Publications (1)

Publication Number Publication Date
US20100312979A1 true US20100312979A1 (en) 2010-12-09

Family

ID=42543192

Family Applications (6)

Application Number Title Priority Date Filing Date
US11/640,024 Active 2028-05-11 US8655850B2 (en) 2005-12-19 2006-12-15 Systems and methods for resynchronizing information
US11/639,808 Active 2028-09-11 US8661216B2 (en) 2005-12-19 2006-12-15 Systems and methods for migrating components in a hierarchical storage network
US11/825,279 Abandoned US20070260834A1 (en) 2005-12-19 2007-07-05 Systems and methods for migrating components in a hierarchical storage network
US12/712,245 Abandoned US20100153338A1 (en) 2005-12-19 2010-02-25 Systems and Methods for Resynchronizing Information
US12/856,995 Abandoned US20100312979A1 (en) 2005-12-19 2010-08-16 Systems and Methods for Migrating Components in a Hierarchical Storage Network
US14/181,359 Expired - Fee Related US9002799B2 (en) 2005-12-19 2014-02-14 Systems and methods for resynchronizing information

Family Applications Before (4)

Application Number Title Priority Date Filing Date
US11/640,024 Active 2028-05-11 US8655850B2 (en) 2005-12-19 2006-12-15 Systems and methods for resynchronizing information
US11/639,808 Active 2028-09-11 US8661216B2 (en) 2005-12-19 2006-12-15 Systems and methods for migrating components in a hierarchical storage network
US11/825,279 Abandoned US20070260834A1 (en) 2005-12-19 2007-07-05 Systems and methods for migrating components in a hierarchical storage network
US12/712,245 Abandoned US20100153338A1 (en) 2005-12-19 2010-02-25 Systems and Methods for Resynchronizing Information

Family Applications After (1)

Application Number Title Priority Date Filing Date
US14/181,359 Expired - Fee Related US9002799B2 (en) 2005-12-19 2014-02-14 Systems and methods for resynchronizing information

Country Status (1)

Country Link
US (6) US8655850B2 (en)

Cited By (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070198797A1 (en) * 2005-12-19 2007-08-23 Srinivas Kavuri Systems and methods for migrating components in a hierarchical storage network
US8706993B2 (en) 2004-04-30 2014-04-22 Commvault Systems, Inc. Systems and methods for storage modeling and costing
US8725980B2 (en) 2004-04-30 2014-05-13 Commvault Systems, Inc. System and method for allocation of organizational resources
US8738963B2 (en) * 2010-04-08 2014-05-27 Hitachi, Ltd. Methods and apparatus for managing error codes for storage systems coupled with external storage systems
US8769059B1 (en) 2012-05-23 2014-07-01 Amazon Technologies, Inc. Best practice analysis, third-party plug-ins
US8954574B1 (en) * 2012-05-23 2015-02-10 Amazon Technologies, Inc. Best practice analysis, migration advisor
US9116861B2 (en) 2012-12-14 2015-08-25 Lenovo Enterprise Solutions (Singapore) Pte. Ltd. Cascading failover of blade servers in a data center
US9122652B2 (en) 2012-12-17 2015-09-01 Lenovo Enterprise Solutions (Singapore) Pte. Ltd. Cascading failover of blade servers in a data center
US9152685B2 (en) 2005-12-19 2015-10-06 Commvault Systems, Inc. Systems and methods for migrating components in a hierarchical storage network
GB2533405A (en) * 2014-12-19 2016-06-22 Ibm Data storage resource assignment
US9626710B1 (en) 2012-05-23 2017-04-18 Amazon Technologies, Inc. Best practice analysis, optimized resource use
US20170160974A1 (en) * 2013-07-16 2017-06-08 International Business Machines Corporation Managing a storage system
EP2663891A4 (en) * 2011-01-10 2017-07-19 Storone Ltd. Large scale storage system
US10146450B1 (en) * 2015-12-28 2018-12-04 EMC IP Holding Company LLC Managing a pool of storage slices via consumption estimation based on historical data
US10176036B2 (en) 2015-10-29 2019-01-08 Commvault Systems, Inc. Monitoring, diagnosing, and repairing a management database in a data storage management system
US10275320B2 (en) 2015-06-26 2019-04-30 Commvault Systems, Inc. Incrementally accumulating in-process performance data and hierarchical reporting thereof for a data stream in a secondary copy operation
US10379988B2 (en) 2012-12-21 2019-08-13 Commvault Systems, Inc. Systems and methods for performance monitoring
US10740765B1 (en) 2012-05-23 2020-08-11 Amazon Technologies, Inc. Best practice analysis as a service
US10831591B2 (en) 2018-01-11 2020-11-10 Commvault Systems, Inc. Remedial action based on maintaining process awareness in data storage management
US11449253B2 (en) 2018-12-14 2022-09-20 Commvault Systems, Inc. Disk usage growth prediction system

Families Citing this family (273)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8346733B2 (en) 2006-12-22 2013-01-01 Commvault Systems, Inc. Systems and methods of media management, such as management of media to and from a media storage library
US7596586B2 (en) 2003-04-03 2009-09-29 Commvault Systems, Inc. System and method for extended media retention
AU2003214624A1 (en) * 2002-04-25 2003-11-10 Kashya Israel Ltd. An apparatus for continuous compression of large volumes of data
US7174433B2 (en) 2003-04-03 2007-02-06 Commvault Systems, Inc. System and method for dynamically sharing media in a computer network
WO2005048085A2 (en) 2003-11-13 2005-05-26 Commvault Systems, Inc. System and method for performing an image level snapshot and for restoring partial volume data
GB2435756B (en) 2004-11-05 2008-12-10 Commvault Systems Inc Method and system of pooling storage devices
US7651593B2 (en) 2005-12-19 2010-01-26 Commvault Systems, Inc. Systems and methods for performing data replication
CA2632935C (en) 2005-12-19 2014-02-04 Commvault Systems, Inc. Systems and methods for performing data replication
US7606844B2 (en) 2005-12-19 2009-10-20 Commvault Systems, Inc. System and method for performing replication copy storage operations
US7774565B2 (en) * 2005-12-21 2010-08-10 Emc Israel Development Center, Ltd. Methods and apparatus for point in time data access and recovery
US8060713B1 (en) 2005-12-21 2011-11-15 Emc (Benelux) B.V., S.A.R.L. Consolidating snapshots in a continuous data protection system using journaling
US7849361B2 (en) * 2005-12-22 2010-12-07 Emc Corporation Methods and apparatus for multiple point in time data access
US8392400B1 (en) * 2005-12-29 2013-03-05 Amazon Technologies, Inc. Method and apparatus for stress management in a searchable data service
US20080010513A1 (en) * 2006-06-27 2008-01-10 International Business Machines Corporation Controlling computer storage systems
US8726242B2 (en) 2006-07-27 2014-05-13 Commvault Systems, Inc. Systems and methods for continuous data replication
GB0616265D0 (en) * 2006-08-16 2006-09-27 Ibm Efficient synchronised updates to a data record in a data store
US8484167B2 (en) * 2006-08-31 2013-07-09 Sap Ag Data verification systems and methods based on messaging data
US8315988B2 (en) * 2006-08-31 2012-11-20 Sap Ag Systems and methods for verifying a data communication process
US7627612B2 (en) * 2006-09-28 2009-12-01 Emc Israel Development Center, Ltd. Methods and apparatus for optimal journaling for continuous data replication
US7627687B2 (en) * 2006-09-28 2009-12-01 Emc Israel Development Center, Ltd. Methods and apparatus for managing data flow in a continuous data replication system having journaling
US7831566B2 (en) * 2006-12-22 2010-11-09 Commvault Systems, Inc. Systems and methods of hierarchical storage management, such as global management of storage operations
US8458263B1 (en) 2007-03-27 2013-06-04 Emc Corporation Method and apparatus for electronic message archive verification
US8930464B1 (en) 2007-03-30 2015-01-06 Emc Corporation Email content pre-caching to a local archive store
US8856241B1 (en) * 2007-03-30 2014-10-07 Emc Corporation Management of email archive server requests
US7730148B1 (en) * 2007-03-30 2010-06-01 Emc Corporation Backfilling a local email archive store
US8032599B1 (en) * 2007-03-30 2011-10-04 Emc Corporation Display of archived email content in a preview pane
US8527593B1 (en) * 2007-03-30 2013-09-03 Emc Corporation Change of an archived email property in the email system local store
US7730147B1 (en) * 2007-03-30 2010-06-01 Emc Corporation Prioritizing archived email requests
US7730146B1 (en) * 2007-03-30 2010-06-01 Emc Corporation Local email archive store size management
US8156188B1 (en) * 2007-03-30 2012-04-10 Emc Corporation Email archive server priming for a content request
US9112873B2 (en) * 2007-04-10 2015-08-18 Apertio Limited Alias hiding in network data repositories
US8402147B2 (en) * 2007-04-10 2013-03-19 Apertio Limited Nomadic subscriber data system
US8782085B2 (en) 2007-04-10 2014-07-15 Apertio Limited Variant entries in network data repositories
JP5081498B2 (en) * 2007-05-24 2012-11-28 株式会社日立製作所 Computer system and control method thereof
US8706976B2 (en) 2007-08-30 2014-04-22 Commvault Systems, Inc. Parallel access virtual tape library and drives
WO2009029889A1 (en) * 2007-08-31 2009-03-05 Clear Channel Management Services, L.P. Radio receiver and method for receiving and playing signals from multiple broadcast channels
US7870360B2 (en) * 2007-09-14 2011-01-11 International Business Machines Corporation Storage area network (SAN) forecasting in a heterogeneous environment
US9207990B2 (en) * 2007-09-28 2015-12-08 Hewlett-Packard Development Company, L.P. Method and system for migrating critical resources within computer systems
US8495315B1 (en) * 2007-09-29 2013-07-23 Symantec Corporation Method and apparatus for supporting compound disposition for data images
US11226947B1 (en) * 2007-10-10 2022-01-18 United Services Automobile Association (Usaa) Systems and methods for storing time-series data
US9195700B1 (en) 2007-10-10 2015-11-24 United Services Automobile Association (Usaa) Systems and methods for storing time-series data
JP2009116826A (en) * 2007-11-09 2009-05-28 Hitachi Ltd Storage device and logical volume migration method
US7840536B1 (en) 2007-12-26 2010-11-23 Emc (Benelux) B.V., S.A.R.L. Methods and apparatus for dynamic journal expansion
US8041940B1 (en) 2007-12-26 2011-10-18 Emc Corporation Offloading encryption processing in a storage area network
US7860836B1 (en) 2007-12-26 2010-12-28 Emc (Benelux) B.V., S.A.R.L. Method and apparatus to recover data in a continuous data protection environment using a journal
US8423739B2 (en) * 2008-02-06 2013-04-16 International Business Machines Corporation Apparatus, system, and method for relocating logical array hot spots
US8914340B2 (en) * 2008-02-06 2014-12-16 International Business Machines Corporation Apparatus, system, and method for relocating storage pool hot spots
US9501542B1 (en) 2008-03-11 2016-11-22 Emc Corporation Methods and apparatus for volume synchronization
US8086651B2 (en) * 2008-05-12 2011-12-27 Research In Motion Limited Managing media files using metadata injection
US8122037B2 (en) * 2008-05-12 2012-02-21 Research In Motion Limited Auto-selection of media files
US8095566B2 (en) * 2008-05-12 2012-01-10 Research In Motion Limited Managing media files from multiple sources
US10552384B2 (en) * 2008-05-12 2020-02-04 Blackberry Limited Synchronizing media files available from multiple sources
US8706690B2 (en) 2008-05-12 2014-04-22 Blackberry Limited Systems and methods for space management in file systems
US20090282078A1 (en) * 2008-05-12 2009-11-12 Motion Limited Unified media file architecture
US8170990B2 (en) * 2008-05-30 2012-05-01 Hitachi, Ltd. Integrated remote replication in hierarchical storage systems
US8769048B2 (en) 2008-06-18 2014-07-01 Commvault Systems, Inc. Data protection scheduling, such as providing a flexible backup window in a data protection system
US8055835B2 (en) * 2008-06-23 2011-11-08 International Business Machines Corporation Apparatus, system, and method for migrating wear spots
US20090319532A1 (en) * 2008-06-23 2009-12-24 Jens-Peter Akelbein Method of and system for managing remote storage
US20100010979A1 (en) * 2008-07-11 2010-01-14 International Business Machines Corporation Reduced Volume Precision Data Quality Information Cleansing Feedback Process
US8140485B2 (en) * 2008-07-31 2012-03-20 International Business Machines Corporation Data recovery using a minimum number of recovery streams
US8725688B2 (en) 2008-09-05 2014-05-13 Commvault Systems, Inc. Image level copy or restore, such as image level restore without knowledge of data object metadata
US20100070466A1 (en) 2008-09-15 2010-03-18 Anand Prahlad Data transfer techniques within data storage devices, such as network attached storage performing data migration
US8380684B2 (en) * 2008-09-30 2013-02-19 Microsoft Corporation Data-tier application component fabric management
US9274714B2 (en) * 2008-10-27 2016-03-01 Netapp, Inc. Method and system for managing storage capacity in a storage network
US9495382B2 (en) * 2008-12-10 2016-11-15 Commvault Systems, Inc. Systems and methods for performing discrete data replication
US8204859B2 (en) 2008-12-10 2012-06-19 Commvault Systems, Inc. Systems and methods for managing replicated database data
US8055614B1 (en) * 2008-12-23 2011-11-08 Symantec Corporation Method and apparatus for providing single instance restoration of data files
US8984252B2 (en) * 2009-01-22 2015-03-17 International Business Machines Corporation Extent consolidation and storage group allocation
US8205014B2 (en) * 2009-02-02 2012-06-19 Hitachi, Ltd. Information apparatus and method of generating tuning plan for resource configuration of storage system
US8145598B2 (en) * 2009-02-23 2012-03-27 Iron Mountain Incorporated Methods and systems for single instance storage of asset parts
US8397051B2 (en) 2009-02-23 2013-03-12 Autonomy, Inc. Hybrid hash tables
US9037718B2 (en) * 2009-03-25 2015-05-19 Ntt Docomo, Inc. Method and apparatus for live replication
CA3081255C (en) 2009-04-01 2023-08-22 Nicira, Inc. Method and apparatus for implementing and managing virtual switches
US8255596B2 (en) * 2009-06-10 2012-08-28 International Business Machines Corporation Multipath-based migration of data across storage controllers
US8880835B2 (en) * 2009-07-07 2014-11-04 International Business Machines Corporation Adjusting location of tiered storage residence based on usage patterns
US10699223B1 (en) * 2009-08-13 2020-06-30 Amazon Technologies, Inc. System and method for resource allocation across distinct processes of a materials handling facility
US8417849B2 (en) * 2009-10-07 2013-04-09 International Business Machines Corporation Apparatus and method to adjust a multi-path device reservation
US8886597B2 (en) * 2009-10-28 2014-11-11 Sandisk Il Ltd. Synchronizing changes in a file system which are initiated by a storage device and a host device
US10496608B2 (en) * 2009-10-28 2019-12-03 Sandisk Il Ltd. Synchronizing changes in a file system which are initiated by a storage device and a host device
US8296329B1 (en) * 2009-12-09 2012-10-23 Emc Corporation Controller with heuristic bundle optimizer for data center migration or other type of transition
GB0921851D0 (en) * 2009-12-15 2010-01-27 Geniedb Record operation mode setting
US8504517B2 (en) 2010-03-29 2013-08-06 Commvault Systems, Inc. Systems and methods for selective data replication
US8504515B2 (en) 2010-03-30 2013-08-06 Commvault Systems, Inc. Stubbing systems and methods in a data replication environment
US8392680B1 (en) 2010-03-30 2013-03-05 Emc International Company Accessing a volume in a distributed environment
US8725698B2 (en) 2010-03-30 2014-05-13 Commvault Systems, Inc. Stub file prioritization in a data replication system
US20110282838A1 (en) * 2010-05-14 2011-11-17 International Business Machines Corporation Aging file system
WO2011150391A1 (en) 2010-05-28 2011-12-01 Commvault Systems, Inc. Systems and methods for performing data replication
US8332687B1 (en) 2010-06-23 2012-12-11 Emc Corporation Splitter used in a continuous data protection environment
US9525647B2 (en) 2010-07-06 2016-12-20 Nicira, Inc. Network control apparatus and method for creating and modifying logical switching elements
US8830823B2 (en) 2010-07-06 2014-09-09 Nicira, Inc. Distributed control platform for large-scale production networks
US9582319B2 (en) 2010-08-13 2017-02-28 International Business Machines Corporation Migrating virtual machines across network separated data centers
US8433869B1 (en) 2010-09-27 2013-04-30 Emc International Company Virtualized consistency group using an enhanced splitter
US8478955B1 (en) 2010-09-27 2013-07-02 Emc International Company Virtualized consistency group using more than one data protection appliance
US8335771B1 (en) 2010-09-29 2012-12-18 Emc Corporation Storage array snapshots for logged access replication in a continuous data protection system
US8694700B1 (en) 2010-09-29 2014-04-08 Emc Corporation Using I/O track information for continuous push with splitter for storage device
US9244779B2 (en) 2010-09-30 2016-01-26 Commvault Systems, Inc. Data recovery operations, such as recovery from modified network data management protocol data
US8549129B2 (en) * 2010-10-12 2013-10-01 Microsoft Corporation Live migration method for large-scale IT management systems
US9336139B2 (en) * 2010-11-29 2016-05-10 Cleversafe, Inc. Selecting a memory for storage of an encoded data slice in a dispersed storage network
US8335761B1 (en) 2010-12-02 2012-12-18 Emc International Company Replicating in a multi-copy environment
US8983907B2 (en) * 2010-12-08 2015-03-17 Microsoft Technology Licensing, Llc Change notifications from an updated data representation
US8666997B2 (en) 2010-12-08 2014-03-04 Microsoft Corporation Placeholders returned for data representation items
US9329886B2 (en) * 2010-12-10 2016-05-03 Amazon Technologies, Inc. Virtual machine morphing for heterogeneous migration environments
US8364641B2 (en) * 2010-12-15 2013-01-29 International Business Machines Corporation Method and system for deduplicating data
US9069829B2 (en) 2011-01-21 2015-06-30 Microsoft Technology Licensing, Llc Data items manager
US9584949B2 (en) 2011-01-27 2017-02-28 Microsoft Technology Licensing, Llc Cloud based master data management architecture
US20120198018A1 (en) * 2011-01-27 2012-08-02 Microsoft Corporation Securely publishing data to network service
US8849768B1 (en) * 2011-03-08 2014-09-30 Symantec Corporation Systems and methods for classifying files as candidates for deduplication
US8838533B2 (en) 2011-05-20 2014-09-16 Microsoft Corporation Optimistic application of data edits
US9256605B1 (en) 2011-08-03 2016-02-09 Emc Corporation Reading and writing to an unexposed device
US8898112B1 (en) 2011-09-07 2014-11-25 Emc Corporation Write signature command
US9043184B1 (en) * 2011-10-12 2015-05-26 Netapp, Inc. System and method for identifying underutilized storage capacity
US20130238867A1 (en) * 2012-03-06 2013-09-12 Hitachi, Ltd. Method and apparatus to deploy and backup volumes
US9298715B2 (en) 2012-03-07 2016-03-29 Commvault Systems, Inc. Data storage system utilizing proxy device for storage operations
US9471578B2 (en) 2012-03-07 2016-10-18 Commvault Systems, Inc. Data storage system utilizing proxy device for storage operations
US9678921B2 (en) * 2012-03-21 2017-06-13 Owl Computing Technologies, Llc Method and apparatus for data transfer reconciliation
US8935203B1 (en) 2012-03-29 2015-01-13 Amazon Technologies, Inc. Environment-sensitive distributed data management
US8930364B1 (en) * 2012-03-29 2015-01-06 Amazon Technologies, Inc. Intelligent data integration
US8832234B1 (en) 2012-03-29 2014-09-09 Amazon Technologies, Inc. Distributed data storage controller
US8918392B1 (en) 2012-03-29 2014-12-23 Amazon Technologies, Inc. Data storage mapping and management
EP2712450A4 (en) 2012-03-30 2015-09-16 Commvault Systems Inc Informaton management of mobile device data
US9342537B2 (en) 2012-04-23 2016-05-17 Commvault Systems, Inc. Integrated snapshot interface for a data storage system
US9703500B2 (en) 2012-04-25 2017-07-11 International Business Machines Corporation Reducing power consumption by migration of data within a tiered storage system
US9177000B2 (en) * 2012-04-30 2015-11-03 International Business Machines Corporation Data index using a linked data standard
US9223659B1 (en) 2012-06-28 2015-12-29 Emc International Company Generating and accessing a virtual volume snapshot in a continuous data protection system
US9858288B2 (en) 2012-08-03 2018-01-02 Egnyte, Inc. System and method for event-based synchronization of remote and local file systems
GB2504719A (en) 2012-08-07 2014-02-12 Ibm Grid based data mobility
US20140058717A1 (en) * 2012-08-24 2014-02-27 Hitachi, Ltd. Simulation system for simulating i/o performance of volume and simulation method
US10235145B1 (en) 2012-09-13 2019-03-19 Emc International Company Distributed scale-out replication
US9336094B1 (en) 2012-09-13 2016-05-10 Emc International Company Scaleout replication of an application
CN103716174A (en) * 2012-10-09 2014-04-09 鸿富锦精密工业(深圳)有限公司 Test log acquisition system and method for the same
JP6056453B2 (en) * 2012-12-20 2017-01-11 富士通株式会社 Program, data management method, and information processing apparatus
US8972334B2 (en) 2012-12-21 2015-03-03 International Business Machines Corporation Transparent data service suitable for modifying data storage capabilities in applications
US9069799B2 (en) 2012-12-27 2015-06-30 Commvault Systems, Inc. Restoration of centralized data storage manager, such as data storage manager in a hierarchical data storage system
US9633216B2 (en) 2012-12-27 2017-04-25 Commvault Systems, Inc. Application of information management policies based on operation with a geographic entity
US20140189532A1 (en) * 2012-12-28 2014-07-03 Verizon Patent And Licensing Inc. Editing text-based communications
US9886346B2 (en) 2013-01-11 2018-02-06 Commvault Systems, Inc. Single snapshot for multiple agents
US10509801B2 (en) * 2013-01-28 2019-12-17 Arris Enterprises Llc Selective data synchronization and transfer to remote distributed database servers
US20140229695A1 (en) * 2013-02-13 2014-08-14 Dell Products L.P. Systems and methods for backup in scale-out storage clusters
US9459968B2 (en) 2013-03-11 2016-10-04 Commvault Systems, Inc. Single index to query multiple backup formats
US9507887B1 (en) * 2013-03-13 2016-11-29 EMC IP Holding Company LLC Adaptive techniques for workload distribution across multiple storage tiers
US8996460B1 (en) 2013-03-14 2015-03-31 Emc Corporation Accessing an image in a continuous data protection using deduplication-based storage
US9696939B1 (en) 2013-03-14 2017-07-04 EMC IP Holding Company LLC Replicating data using deduplication-based arrays using network-based replication
US9383937B1 (en) 2013-03-14 2016-07-05 Emc Corporation Journal tiering in a continuous data protection system using deduplication-based storage
US9110914B1 (en) 2013-03-14 2015-08-18 Emc Corporation Continuous data protection using deduplication-based storage
US9152339B1 (en) 2013-03-15 2015-10-06 Emc Corporation Synchronization of asymmetric active-active, asynchronously-protected storage
US9383939B2 (en) * 2013-03-15 2016-07-05 International Business Machines Corporation Migrating and retrieving queued data in byte-addressable storage
US9081842B1 (en) 2013-03-15 2015-07-14 Emc Corporation Synchronous and asymmetric asynchronous active-active-active data access
US9244997B1 (en) 2013-03-15 2016-01-26 Emc Corporation Asymmetric active-active access of asynchronously-protected data storage
US9767210B2 (en) 2013-03-28 2017-09-19 International Business Machines Corporation Dynamically enhancing user interface
US9665593B2 (en) * 2013-03-28 2017-05-30 International Business Machines Corporation Dynamically synching elements in file
US9069709B1 (en) 2013-06-24 2015-06-30 Emc International Company Dynamic granularity in data replication
US9087112B1 (en) 2013-06-24 2015-07-21 Emc International Company Consistency across snapshot shipping and continuous replication
US9146878B1 (en) 2013-06-25 2015-09-29 Emc Corporation Storage recovery from total cache loss using journal-based replication
US20150113314A1 (en) * 2013-07-11 2015-04-23 Brian J. Bulkowski Method and system of implementing a distributed database with peripheral component interconnect express switch
US9590886B2 (en) 2013-11-01 2017-03-07 Commvault Systems, Inc. Systems and methods for differential health checking of an information management system
US10073904B2 (en) * 2013-11-05 2018-09-11 Verizon Patent And Licensing Inc. Event triggered service for the lightweight directory access protocol
US9367260B1 (en) 2013-12-13 2016-06-14 Emc Corporation Dynamic replication system
US9405765B1 (en) 2013-12-17 2016-08-02 Emc Corporation Replication of virtual machines
US9158630B1 (en) 2013-12-19 2015-10-13 Emc Corporation Testing integrity of replicated storage
US20150186488A1 (en) * 2013-12-27 2015-07-02 International Business Machines Corporation Asynchronous replication with secure data erasure
US9495251B2 (en) 2014-01-24 2016-11-15 Commvault Systems, Inc. Snapshot readiness checking and reporting
US9639426B2 (en) 2014-01-24 2017-05-02 Commvault Systems, Inc. Single snapshot for multiple applications
US9632874B2 (en) 2014-01-24 2017-04-25 Commvault Systems, Inc. Database application backup in single snapshot for multiple applications
US9753812B2 (en) 2014-01-24 2017-09-05 Commvault Systems, Inc. Generating mapping information for single snapshot for multiple applications
US10169121B2 (en) 2014-02-27 2019-01-01 Commvault Systems, Inc. Work flow management for an information management system
US9779153B2 (en) * 2014-03-03 2017-10-03 Netapp, Inc. Data transfer between storage systems using data fingerprints
US9648100B2 (en) * 2014-03-05 2017-05-09 Commvault Systems, Inc. Cross-system storage management for transferring data across autonomous information management systems
US9189339B1 (en) 2014-03-28 2015-11-17 Emc Corporation Replication of a virtual distributed volume with virtual machine granualarity
US10025710B2 (en) * 2014-04-30 2018-07-17 Walmart Apollo, Llc Pattern for integrating primary and secondary data stores in a sharded data domain
US9740574B2 (en) 2014-05-09 2017-08-22 Commvault Systems, Inc. Load balancing across multiple data paths
US9459970B2 (en) 2014-05-19 2016-10-04 Netapp, Inc. Performance during playback of logged data storage operations
US10082980B1 (en) 2014-06-20 2018-09-25 EMC IP Holding Company LLC Migration of snapshot in replication system using a log
US9274718B1 (en) 2014-06-20 2016-03-01 Emc Corporation Migration in replication system
US9619543B1 (en) 2014-06-23 2017-04-11 EMC IP Holding Company LLC Replicating in virtual desktop infrastructure
US10380076B2 (en) 2014-07-21 2019-08-13 Egnyte, Inc. System and method for policy based synchronization of remote and local file systems
US9852026B2 (en) 2014-08-06 2017-12-26 Commvault Systems, Inc. Efficient application recovery in an information management system based on a pseudo-storage-device driver
US11249858B2 (en) 2014-08-06 2022-02-15 Commvault Systems, Inc. Point-in-time backups of a production application made accessible over fibre channel and/or ISCSI as data sources to a remote application by representing the backups as pseudo-disks operating apart from the production application and its host
US9774672B2 (en) 2014-09-03 2017-09-26 Commvault Systems, Inc. Consolidated processing of storage-array commands by a snapshot-control media agent
US10042716B2 (en) 2014-09-03 2018-08-07 Commvault Systems, Inc. Consolidated processing of storage-array commands using a forwarder media agent in conjunction with a snapshot-control media agent
US10324798B1 (en) 2014-09-25 2019-06-18 EMC IP Holding Company LLC Restoring active areas of a logical unit
US10101943B1 (en) 2014-09-25 2018-10-16 EMC IP Holding Company LLC Realigning data in replication system
US10437783B1 (en) 2014-09-25 2019-10-08 EMC IP Holding Company LLC Recover storage array using remote deduplication device
US9529885B1 (en) 2014-09-29 2016-12-27 EMC IP Holding Company LLC Maintaining consistent point-in-time in asynchronous replication during virtual machine relocation
US9910621B1 (en) 2014-09-29 2018-03-06 EMC IP Holding Company LLC Backlogging I/O metadata utilizing counters to monitor write acknowledgements and no acknowledgements
US9648105B2 (en) 2014-11-14 2017-05-09 Commvault Systems, Inc. Unified snapshot storage management, using an enhanced storage manager and enhanced media agents
US9448731B2 (en) 2014-11-14 2016-09-20 Commvault Systems, Inc. Unified snapshot storage management
US9753936B1 (en) * 2014-12-01 2017-09-05 Amazon Technologies, Inc. Metering data in distributed storage environments
US9600377B1 (en) 2014-12-03 2017-03-21 EMC IP Holding Company LLC Providing data protection using point-in-time images from multiple types of storage devices
US10496487B1 (en) 2014-12-03 2019-12-03 EMC IP Holding Company LLC Storing snapshot changes with snapshots
US9405481B1 (en) 2014-12-17 2016-08-02 Emc Corporation Replicating using volume multiplexing with consistency group file
US10394773B2 (en) * 2015-01-02 2019-08-27 International Business Machines Corporation Determining when a change set was delivered to a workspace or stream and by whom
CA2972382A1 (en) * 2015-01-09 2016-07-14 Landmark Graphics Corporation Apparatus and methods of data synchronization
US10956299B2 (en) 2015-02-27 2021-03-23 Commvault Systems, Inc. Diagnosing errors in data storage and archiving in a cloud or networking environment
US9632881B1 (en) 2015-03-24 2017-04-25 EMC IP Holding Company LLC Replication of a virtual distributed volume
US9411535B1 (en) 2015-03-27 2016-08-09 Emc Corporation Accessing multiple virtual devices
US10296419B1 (en) 2015-03-27 2019-05-21 EMC IP Holding Company LLC Accessing a virtual device using a kernel
US10082985B2 (en) 2015-03-27 2018-09-25 Pure Storage, Inc. Data striping across storage nodes that are assigned to multiple logical arrays
US9678680B1 (en) 2015-03-30 2017-06-13 EMC IP Holding Company LLC Forming a protection domain in a storage architecture
US9928144B2 (en) 2015-03-30 2018-03-27 Commvault Systems, Inc. Storage management of data using an open-archive architecture, including streamlined access to primary data originally stored on network-attached storage and archived to secondary storage
US9953070B1 (en) 2015-04-05 2018-04-24 Simply Data Now Inc. Enterprise resource planning (ERP) system data extraction, loading, and directing
US10437789B2 (en) 2015-04-10 2019-10-08 Egnyte, Inc. System and method for delete fencing during synchronization of remote and local file systems
US11144510B2 (en) 2015-06-11 2021-10-12 Egnyte, Inc. System and method for synchronizing file systems with large namespaces
US10853181B1 (en) 2015-06-29 2020-12-01 EMC IP Holding Company LLC Backing up volumes using fragment files
US9766825B2 (en) 2015-07-22 2017-09-19 Commvault Systems, Inc. Browse and restore for block-level backups
US10101913B2 (en) 2015-09-02 2018-10-16 Commvault Systems, Inc. Migrating data to disk without interrupting running backup operations
US10394661B2 (en) * 2015-09-22 2019-08-27 International Business Machines Corporation Policy driven data updates
US10841374B2 (en) * 2015-10-26 2020-11-17 Mcafee, Llc Dynamic sharding for state-based processing
US10019502B2 (en) * 2015-11-27 2018-07-10 Netapp Inc. Non-disruptive baseline and resynchronization of a synchronous replication relationship
CN105897457A (en) * 2015-12-09 2016-08-24 乐视云计算有限公司 Service upgrade method and system of server group
US11347697B1 (en) * 2015-12-15 2022-05-31 Pure Storage, Inc. Proactively optimizing a storage system
US9684576B1 (en) 2015-12-21 2017-06-20 EMC IP Holding Company LLC Replication using a virtual distributed volume
US20170177613A1 (en) 2015-12-22 2017-06-22 Egnyte, Inc. Event-Based User State Synchronization in a Cloud Storage System
US10067837B1 (en) 2015-12-28 2018-09-04 EMC IP Holding Company LLC Continuous data protection with cloud resources
US10133874B1 (en) 2015-12-28 2018-11-20 EMC IP Holding Company LLC Performing snapshot replication on a storage system not configured to support snapshot replication
US10235196B1 (en) 2015-12-28 2019-03-19 EMC IP Holding Company LLC Virtual machine joining or separating
JPWO2017145899A1 (en) * 2016-02-24 2018-12-20 日本電気株式会社 Management system, test method and program
US10296368B2 (en) 2016-03-09 2019-05-21 Commvault Systems, Inc. Hypervisor-independent block-level live browse for access to backed up virtual machine (VM) data and hypervisor-free file-level recovery (block-level pseudo-mount)
US10503753B2 (en) 2016-03-10 2019-12-10 Commvault Systems, Inc. Snapshot replication operations based on incremental block change tracking
US10152267B1 (en) 2016-03-30 2018-12-11 Emc Corporation Replication data pull
US10579282B1 (en) 2016-03-30 2020-03-03 EMC IP Holding Company LLC Distributed copy in multi-copy replication where offset and size of I/O requests to replication site is half offset and size of I/O request to production volume
US10235087B1 (en) 2016-03-30 2019-03-19 EMC IP Holding Company LLC Distributing journal data over multiple journals
US10235060B1 (en) 2016-04-14 2019-03-19 EMC IP Holding Company, LLC Multilevel snapshot replication for hot and cold regions of a storage system
US10416982B1 (en) 2016-06-30 2019-09-17 EMC IP Holding Company LLC Automated analysis system and method
US10095504B1 (en) * 2016-06-30 2018-10-09 EMC IP Holding Company LLC Automated analysis system and method
US9971645B2 (en) 2016-08-23 2018-05-15 Seagate Technology Llc Auto-recovery of media cache master table data
US10019194B1 (en) 2016-09-23 2018-07-10 EMC IP Holding Company LLC Eventually consistent synchronous data replication in a storage system
US10146961B1 (en) 2016-09-23 2018-12-04 EMC IP Holding Company LLC Encrypting replication journals in a storage system
US10235091B1 (en) 2016-09-23 2019-03-19 EMC IP Holding Company LLC Full sweep disk synchronization in a storage system
US10210073B1 (en) 2016-09-23 2019-02-19 EMC IP Holding Company, LLC Real time debugging of production replicated data with data obfuscation in a storage system
US10235090B1 (en) 2016-09-23 2019-03-19 EMC IP Holding Company LLC Validating replication copy consistency using a hash function in a storage system
US10007582B2 (en) 2016-09-27 2018-06-26 International Business Machines Corporation Rebuild rollback support in distributed SDS systems
US10838821B2 (en) 2017-02-08 2020-11-17 Commvault Systems, Inc. Migrating content and metadata from a backup system
US10740193B2 (en) 2017-02-27 2020-08-11 Commvault Systems, Inc. Hypervisor-independent reference copies of virtual machine payload data based on block-level pseudo-mount
US11032350B2 (en) 2017-03-15 2021-06-08 Commvault Systems, Inc. Remote commands framework to control clients
US10891069B2 (en) 2017-03-27 2021-01-12 Commvault Systems, Inc. Creating local copies of data stored in online data repositories
GB201704973D0 (en) * 2017-03-28 2017-05-10 Gb Gas Holdings Ltd Data replication system
US10776329B2 (en) 2017-03-28 2020-09-15 Commvault Systems, Inc. Migration of a database management system to cloud storage
US11074140B2 (en) 2017-03-29 2021-07-27 Commvault Systems, Inc. Live browsing of granular mailbox data
US10572357B2 (en) 2017-03-29 2020-02-25 International Business Machines Corporation Switching over from using a first primary storage to using a second primary storage when the first primary storage is in a mirror relationship
US10223272B2 (en) 2017-04-25 2019-03-05 Seagate Technology Llc Latency sensitive metadata object persistence operation for storage device
US10664352B2 (en) 2017-06-14 2020-05-26 Commvault Systems, Inc. Live browsing of backed up data residing on cloned disks
CN107247641B (en) * 2017-06-19 2020-04-24 深圳市科力锐科技有限公司 Method and device for restoring operating system on line
US11341103B2 (en) * 2017-08-04 2022-05-24 International Business Machines Corporation Replicating and migrating files to secondary storage sites
US10496674B2 (en) * 2017-08-07 2019-12-03 International Business Machines Corporation Self-describing volume ancestry for data synchronization
US10635334B1 (en) 2017-09-28 2020-04-28 EMC IP Holding Company LLC Rule based data transfer model to cloud
US10942779B1 (en) * 2017-10-27 2021-03-09 EMC IP Holding Company LLC Method and system for compliance map engine
US10754368B1 (en) 2017-10-27 2020-08-25 EMC IP Holding Company LLC Method and system for load balancing backup resources
US10613923B2 (en) * 2017-11-03 2020-04-07 EMC IP Holding Company LLC Recovering log-structured filesystems from physical replicas
US10742735B2 (en) 2017-12-12 2020-08-11 Commvault Systems, Inc. Enhanced network attached storage (NAS) services interfacing to cloud storage
US10866963B2 (en) * 2017-12-28 2020-12-15 Dropbox, Inc. File system authentication
US10834189B1 (en) 2018-01-10 2020-11-10 EMC IP Holding Company LLC System and method for managing workload in a pooled environment
US10795927B2 (en) 2018-02-05 2020-10-06 Commvault Systems, Inc. On-demand metadata extraction of clinical image data
US10732885B2 (en) 2018-02-14 2020-08-04 Commvault Systems, Inc. Block-level live browsing and private writable snapshots using an ISCSI server
US10789387B2 (en) 2018-03-13 2020-09-29 Commvault Systems, Inc. Graphical representation of an information management system
US10509587B2 (en) 2018-04-24 2019-12-17 EMC IP Holding Company LLC System and method for high priority backup
US10769030B2 (en) 2018-04-25 2020-09-08 EMC IP Holding Company LLC System and method for improved cache performance
US10909094B1 (en) * 2018-04-30 2021-02-02 Amazon Technologies, Inc. Migration scheduling for fast-mutating metadata records
JP6878369B2 (en) * 2018-09-03 2021-05-26 株式会社日立製作所 Volume allocation management device, volume allocation management method, and volume allocation management program
EP3648430B1 (en) * 2018-11-05 2021-06-02 Wincor Nixdorf International GmbH Hardware security module
US10860443B2 (en) 2018-12-10 2020-12-08 Commvault Systems, Inc. Evaluation and reporting of recovery readiness in a data storage management system
US10817370B2 (en) 2018-12-17 2020-10-27 Gsi Technology Inc. Self correcting memory device
US11194676B2 (en) 2019-03-26 2021-12-07 International Business Machines Corporation Data synchronization in high availability storage environments
US11500664B2 (en) 2019-04-30 2022-11-15 Rubrik, Inc. Systems and method for continuous data protection and recovery by implementing a set of algorithms based on the length of I/O data streams
US11609775B2 (en) 2019-04-30 2023-03-21 Rubrik, Inc. Systems and methods for continuous data protection comprising storage of completed I/O requests intercepted from an I/O stream using touch points
US11086727B2 (en) * 2019-04-30 2021-08-10 Rubrik, Inc. Systems and methods for continuous data protection
US11663089B2 (en) 2019-04-30 2023-05-30 Rubrik, Inc. Systems and methods for continuous data protection
US11663092B2 (en) 2019-04-30 2023-05-30 Rubrik, Inc. Systems and methods for continuous data protection
US11308034B2 (en) 2019-06-27 2022-04-19 Commvault Systems, Inc. Continuously run log backup with minimal configuration and resource usage from the source machine
US11042318B2 (en) 2019-07-29 2021-06-22 Commvault Systems, Inc. Block-level data replication
US11500558B2 (en) * 2020-01-24 2022-11-15 EMC IP Holding Company LLC Dynamic storage device system configuration adjustment
WO2022182917A1 (en) * 2021-02-24 2022-09-01 Nebulon, Inc. Efficient data transmissions between storage nodes in replication relationships
US11593223B1 (en) 2021-09-02 2023-02-28 Commvault Systems, Inc. Using resource pool administrative entities in a data storage management system to provide shared infrastructure to tenants
US11809285B2 (en) 2022-02-09 2023-11-07 Commvault Systems, Inc. Protecting a management database of a data storage management system to meet a recovery point objective (RPO)

Citations (38)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020019909A1 (en) * 1998-06-30 2002-02-14 D'errico Matthew J. Method and apparatus for managing virtual storage devices in a storage system
US6466950B1 (en) * 1998-10-20 2002-10-15 Mitsubishi Denki Kabushiki Kaisha Update log management device and an update log management method decreasing the data amount of transmitting and the update log amount of holding based on the result of comparing the amount of the update log with the amount of the updated data plus the log applied information
US20030005119A1 (en) * 2001-06-28 2003-01-02 Intersan, Inc., A Delaware Corporation Automated creation of application data paths in storage area networks
US20030023893A1 (en) * 2001-05-07 2003-01-30 Lee Whay S. Fault-tolerant routing scheme for a multi-path interconnection fabric in a storage network
US6542972B2 (en) * 2000-01-31 2003-04-01 Commvault Systems, Inc. Logical view and access to physical storage in modular data and storage management system
US20030079018A1 (en) * 2001-09-28 2003-04-24 Lolayekar Santosh C. Load balancing in a storage network
US20030126200A1 (en) * 1996-08-02 2003-07-03 Wolff James J. Dynamic load balancing of a network of client and server computer
US6629189B1 (en) * 2000-03-09 2003-09-30 Emc Corporation Method and apparatus for managing target devices in a multi-path computer system
US20040006572A1 (en) * 2002-04-10 2004-01-08 Hitachi, Ltd. Method and system for employing and managing storage
US20040006578A1 (en) * 2002-07-08 2004-01-08 Trsunyeng Yu System and method for distributed concurrent version management
US6691209B1 (en) * 2000-05-26 2004-02-10 Emc Corporation Topological data categorization and formatting for a mass storage system
US20040078632A1 (en) * 2002-10-21 2004-04-22 Infante Jon L. System with multiple path fail over, fail back and load balancing
US20040117438A1 (en) * 2000-11-02 2004-06-17 John Considine Switching system
US20040133634A1 (en) * 2000-11-02 2004-07-08 Stanley Luke Switching system
US6792472B1 (en) * 2000-03-31 2004-09-14 International Business Machines Corporation System, method and computer readable medium for intelligent raid controllers operating as data routers
US20040193625A1 (en) * 2003-03-27 2004-09-30 Atsushi Sutoh Data control method for duplicating data between computer systems
US20050060613A1 (en) * 2001-01-23 2005-03-17 Adaptec, Inc. Methods and apparatus for a segregated interface for parameter configuration in a multi-path failover system
US20050172073A1 (en) * 2004-01-30 2005-08-04 Hewlett-Packard Development Company, L.P. Storage system including capability to move a virtual storage device group without moving data
US20050228875A1 (en) * 2004-04-13 2005-10-13 Arnold Monitzer System for estimating processing requirements
US20050254456A1 (en) * 2004-05-14 2005-11-17 Sharp Kabushiki Kaisha Transmitter, receiver, data transfer system, transmission method, reception method, computer program for transmission, computer program for reception, and recording medium
US20060047931A1 (en) * 2004-08-27 2006-03-02 Nobuyuki Saika Method and program for creating a snapshot, and storage system
US20060107089A1 (en) * 2004-10-27 2006-05-18 Peter Jansz Diagnosing a path in a storage network
US20060174075A1 (en) * 2005-01-31 2006-08-03 Atsushi Sutoh Method for creating and preserving snapshots in a storage system
US7093012B2 (en) * 2000-09-14 2006-08-15 Overture Services, Inc. System and method for enhancing crawling by extracting requests for webpages in an information flow
US20060206662A1 (en) * 2005-03-14 2006-09-14 Ludwig Thomas E Topology independent storage arrays and methods
US20060215564A1 (en) * 2005-03-23 2006-09-28 International Business Machines Corporation Root-cause analysis of network performance problems
US20070033437A1 (en) * 2004-01-30 2007-02-08 Hitachi, Ltd. Data processing system
US20070050547A1 (en) * 2005-08-25 2007-03-01 Hitachi, Ltd. Storage system and storage system management method
US20070088702A1 (en) * 2005-10-03 2007-04-19 Fridella Stephen A Intelligent network client for multi-protocol namespace redirection
US7231391B2 (en) * 2001-02-06 2007-06-12 Quest Software, Inc. Loosely coupled database clusters with client connection fail-over
US20080147878A1 (en) * 2006-12-15 2008-06-19 Rajiv Kottomtharayil System and methods for granular resource management in a storage network
US20080205301A1 (en) * 2000-06-09 2008-08-28 International Business Machines Corporation System and program for selecting one of multiple paths to communicate with a device
US20080228987A1 (en) * 2004-12-24 2008-09-18 Shuichi Yagi Storage system and method of storage system path control
US20080250178A1 (en) * 2005-09-08 2008-10-09 International Business Machines Corporation Load Distribution in Storage Area Networks
US20080313497A1 (en) * 2004-04-28 2008-12-18 Yusuke Hirakawa Data processing system
US20090013014A1 (en) * 2003-06-18 2009-01-08 International Business Machines Corporation Method, system, and article of manufacture for mirroring data at storage locations
US7502902B2 (en) * 2005-03-11 2009-03-10 Hitachi, Ltd. Storage system and data movement method
US7617321B2 (en) * 2004-05-07 2009-11-10 International Business Machines Corporation File system architecture requiring no direct access to user data from a metadata manager

Family Cites Families (515)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4296465A (en) 1977-11-03 1981-10-20 Honeywell Information Systems Inc. Data mover
US4686620A (en) * 1984-07-26 1987-08-11 American Telephone And Telegraph Company, At&T Bell Laboratories Database backup method
GB8622010D0 (en) 1986-09-12 1986-10-22 Hewlett Packard Ltd File backup facility
US5193154A (en) * 1987-07-10 1993-03-09 Hitachi, Ltd. Buffered peripheral system and method for backing up and retrieving data to and from backup memory device
US5005122A (en) * 1987-09-08 1991-04-02 Digital Equipment Corporation Arrangement with cooperating management server node and network service node
JPH0743676B2 (en) 1988-03-11 1995-05-15 株式会社日立製作所 Back-up data dump control method and device
US5455926A (en) 1988-04-05 1995-10-03 Data/Ware Development, Inc. Virtual addressing of optical storage media as magnetic tape equivalents
US4995035A (en) * 1988-10-31 1991-02-19 International Business Machines Corporation Centralized management in a computer network
JPH07122868B2 (en) 1988-11-29 1995-12-25 日本電気株式会社 Information processing equipment
US5093912A (en) * 1989-06-26 1992-03-03 International Business Machines Corporation Dynamic resource pool expansion and contraction in multiprocessing environments
DE69031443T2 (en) 1989-06-30 1998-04-23 Digital Equipment Corp Method and arrangement for controlling shadow memories
DE69029289T2 (en) 1989-06-30 1997-06-26 Digital Equipment Corp Method and arrangement for controlling shadow memories
US5133065A (en) 1989-07-27 1992-07-21 Personal Computer Peripherals Corporation Backup computer program for networks
US5321816A (en) 1989-10-10 1994-06-14 Unisys Corporation Local-remote apparatus with specialized image storage modules
US5504873A (en) * 1989-11-01 1996-04-02 E-Systems, Inc. Mass data storage and retrieval system
US5276867A (en) * 1989-12-19 1994-01-04 Epoch Systems, Inc. Digital data storage system with improved data migration
US5276860A (en) * 1989-12-19 1994-01-04 Epoch Systems, Inc. Digital data processor with improved backup storage
US5677900A (en) 1990-04-17 1997-10-14 Sharp Kabushiki Kaisha Method and apparatus for replacing a selected file with another longer or shorter file with no portion of the selected file remaining
GB2246218B (en) 1990-07-18 1994-02-09 Stc Plc Distributed data processing systems
US5239647A (en) 1990-09-07 1993-08-24 International Business Machines Corporation Data storage hierarchy with shared storage level
US5544347A (en) 1990-09-24 1996-08-06 Emc Corporation Data storage system controlled remote data mirroring with respectively maintained data indices
US5212772A (en) 1991-02-11 1993-05-18 Gigatrend Incorporated System for storing data in backup tape device
US5317731A (en) 1991-02-25 1994-05-31 International Business Machines Corporation Intelligent page store for concurrent and consistent access to a database by a transaction processor and a query processor
US5287500A (en) * 1991-06-03 1994-02-15 Digital Equipment Corporation System for allocating storage spaces based upon required and optional service attributes having assigned piorities
US5369757A (en) 1991-06-18 1994-11-29 Digital Equipment Corporation Recovery logging in the presence of snapshot files by ordering of buffer pool flushing
US5333315A (en) 1991-06-27 1994-07-26 Digital Equipment Corporation System of device independent file directories using a tag between the directories and file descriptors that migrate with the files
US5347653A (en) 1991-06-28 1994-09-13 Digital Equipment Corporation System for reconstructing prior versions of indexes using records indicating changes between successive versions of the indexes
US5231668A (en) 1991-07-26 1993-07-27 The United States Of America, As Represented By The Secretary Of Commerce Digital signature algorithm
WO1993003549A1 (en) 1991-07-31 1993-02-18 Euphonix, Inc. Automated audio mixer
US5410700A (en) * 1991-09-04 1995-04-25 International Business Machines Corporation Computer system which supports asynchronous commitment of data
EP0531599B1 (en) 1991-09-13 1998-07-22 International Business Machines Corporation Configurable gigabit/s switch adapter
US5606693A (en) 1991-10-02 1997-02-25 International Business Machines Corporation Distributed database management over a network
EP0541281B1 (en) 1991-11-04 1998-04-29 Commvault Systems, Inc. Incremental-computer-file backup using signatures
CA2285096C (en) 1991-11-12 2000-05-09 Ibm Canada Limited-Ibm Canada Limitee Logical mapping of data objects using data spaces
JPH05189281A (en) 1992-01-10 1993-07-30 Hitachi Ltd File assigning system for storage device
US5555404A (en) 1992-03-17 1996-09-10 Telenor As Continuously available database server having multiple groups of nodes with minimum intersecting sets of database fragment replicas
US5241668A (en) * 1992-04-20 1993-08-31 International Business Machines Corporation Method and system for automated termination and resumption in a time zero backup copy process
US5241670A (en) 1992-04-20 1993-08-31 International Business Machines Corporation Method and system for automated backup copy ordering in a time zero backup copy session
US5263154A (en) 1992-04-20 1993-11-16 International Business Machines Corporation Method and system for incremental time zero backup copying of data
US5265159A (en) 1992-06-23 1993-11-23 Hughes Aircraft Company Secure file erasure
US5603012A (en) 1992-06-30 1997-02-11 Discovision Associates Start code detector
US5403639A (en) 1992-09-02 1995-04-04 Storage Technology Corporation File server having snapshot application data groups
EP0680634B1 (en) 1993-01-21 1997-05-14 Apple Computer, Inc. Apparatus and method for backing up data from networked computer storage devices
DE69434311D1 (en) * 1993-02-01 2005-04-28 Sun Microsystems Inc ARCHIVING FILES SYSTEM FOR DATA PROVIDERS IN A DISTRIBUTED NETWORK ENVIRONMENT
US5719786A (en) * 1993-02-03 1998-02-17 Novell, Inc. Digital media data stream network management system
JP3265697B2 (en) 1993-03-17 2002-03-11 富士ゼロックス株式会社 Image processing device
CA2121852A1 (en) 1993-04-29 1994-10-30 Larry T. Jost Disk meshing and flexible storage mapping with enhanced flexible caching
US7174352B2 (en) 1993-06-03 2007-02-06 Network Appliance, Inc. File system image transfer
US6604118B2 (en) * 1998-07-31 2003-08-05 Network Appliance, Inc. File system image transfer
US5963962A (en) 1995-05-31 1999-10-05 Network Appliance, Inc. Write anywhere file-system layout
US5689706A (en) 1993-06-18 1997-11-18 Lucent Technologies Inc. Distributed systems with replicated files
JPH0721135A (en) 1993-07-02 1995-01-24 Fujitsu Ltd Data processing system with duplex monitor function
US5642496A (en) 1993-09-23 1997-06-24 Kanfi; Arnon Method of making a backup copy of a memory over a plurality of copying sessions
US5544345A (en) * 1993-11-08 1996-08-06 International Business Machines Corporation Coherence controls for store-multiple shared data coordinated by cache directory entries in a shared electronic storage
WO1995013580A1 (en) 1993-11-09 1995-05-18 Arcada Software Data backup and restore system for a computer network
US5495607A (en) * 1993-11-15 1996-02-27 Conner Peripherals, Inc. Network management system having virtual catalog overview of files distributively stored across network domain
US5491810A (en) * 1994-03-01 1996-02-13 International Business Machines Corporation Method and system for automated data storage system space allocation utilizing prioritized data set parameters
US5673381A (en) 1994-05-27 1997-09-30 Cheyenne Software International Sales Corp. System and parallel streaming and data stripping to back-up a network
US5638509A (en) 1994-06-10 1997-06-10 Exabyte Corporation Data storage and protection system
US5487072A (en) * 1994-06-30 1996-01-23 Bell Communications Research Inc. Error monitoring algorithm for broadband signaling
JPH0877073A (en) * 1994-08-31 1996-03-22 Toshiba Corp Collective optical disk device
US5598546A (en) * 1994-08-31 1997-01-28 Exponential Technology, Inc. Dual-architecture super-scalar pipeline
US5802281A (en) 1994-09-07 1998-09-01 Rsi Systems, Inc. Peripheral audio/video communication system that interfaces with a host computer and determines format of coded audio/video signals
US5574906A (en) * 1994-10-24 1996-11-12 International Business Machines Corporation System and method for reducing storage requirement in backup subsystems utilizing segmented compression and differencing
US6272465B1 (en) * 1994-11-02 2001-08-07 Legerity, Inc. Monolithic PC audio circuit
US5826046A (en) * 1994-12-30 1998-10-20 International Business Machines Corporation Method and apparatus for polling and selecting any paired device in any drawer
US5604862A (en) * 1995-03-14 1997-02-18 Network Integrity, Inc. Continuously-snapshotted protection of computer files
US5682513A (en) 1995-03-31 1997-10-28 International Business Machines Corporation Cache queue entry linking for DASD record updates
US5615392A (en) * 1995-05-05 1997-03-25 Apple Computer, Inc. Method and apparatus for consolidated buffer handling for computer device input/output
US5559957A (en) * 1995-05-31 1996-09-24 Lucent Technologies Inc. File system for a data storage device having a power fail recovery mechanism for write/replace operations
US6049889A (en) 1995-06-07 2000-04-11 Digital Equipment Corporation High performance recoverable communication method and apparatus for write-only networks
JPH0916463A (en) 1995-06-30 1997-01-17 Hitachi Ltd Dynamic allocation management system for memory area
US5699361A (en) 1995-07-18 1997-12-16 Industrial Technology Research Institute Multimedia channel formulation mechanism
US5813009A (en) 1995-07-28 1998-09-22 Univirtual Corp. Computer based records management system method
US5860104A (en) * 1995-08-31 1999-01-12 Advanced Micro Devices, Inc. Data cache which speculatively updates a predicted data cache storage location with store data and subsequently corrects mispredicted updates
US5619644A (en) 1995-09-18 1997-04-08 International Business Machines Corporation Software directed microcode state save for distributed storage controller
US5907672A (en) 1995-10-04 1999-05-25 Stac, Inc. System for backing up computer disk volumes with error remapping of flawed memory addresses
JP3856855B2 (en) * 1995-10-06 2006-12-13 三菱電機株式会社 Differential backup method
US5970255A (en) 1995-10-16 1999-10-19 Altera Corporation System for coupling programmable logic device to external circuitry which selects a logic standard and uses buffers to modify output and input signals accordingly
US5819020A (en) * 1995-10-16 1998-10-06 Network Specialists, Inc. Real time backup system
US5778395A (en) 1995-10-23 1998-07-07 Stac, Inc. System for backing up files from disk volumes on multiple nodes of a computer network
US5737747A (en) 1995-10-27 1998-04-07 Emc Corporation Prefetching to service multiple video streams from an integrated cached disk array
US5829046A (en) 1995-10-27 1998-10-27 Emc Corporation On-line tape backup using an integrated cached disk array
US6067525A (en) 1995-10-30 2000-05-23 Clear With Computers Integrated computerized sales force automation system
US5987478A (en) 1995-10-31 1999-11-16 Intel Corporation Virtual small block file manager for flash memory array
US6122668A (en) 1995-11-02 2000-09-19 Starlight Networks Synchronization of audio and video signals in a live multicast in a LAN
US5805920A (en) 1995-11-13 1998-09-08 Tandem Computers Incorporated Direct bulk data transfers
US5729743A (en) * 1995-11-17 1998-03-17 Deltatech Research, Inc. Computer apparatus and method for merging system deltas
US5933104A (en) 1995-11-22 1999-08-03 Microsoft Corporation Method and system for compression and decompression using variable-sized offset and length fields
US5675511A (en) 1995-12-21 1997-10-07 Intel Corporation Apparatus and method for event tagging for multiple audio, video, and data streams
US5761677A (en) 1996-01-03 1998-06-02 Sun Microsystems, Inc. Computer system method and apparatus providing for various versions of a file without requiring data copy or log operations
US5765173A (en) 1996-01-11 1998-06-09 Connected Corporation High performance backup via selective file saving which can perform incremental backups and exclude files and uses a changed block signature list
US5970233A (en) 1996-05-03 1999-10-19 Intel Corporation Multiple codecs for video encoding format compatibility
US5995091A (en) 1996-05-10 1999-11-30 Learn2.Com, Inc. System and method for streaming multimedia data
KR970076238A (en) 1996-05-23 1997-12-12 포만 제프리 엘 Servers, methods and program products thereof for creating and managing multiple copies of client data files
US6044444A (en) * 1996-05-28 2000-03-28 Emc Corporation Remote data mirroring having preselection of automatic recovery or intervention required when a disruption is detected
US5819299A (en) 1996-06-06 1998-10-06 Electric Communities Process for distributed garbage collection
US5812398A (en) 1996-06-10 1998-09-22 Sun Microsystems, Inc. Method and system for escrowed backup of hotelled world wide web sites
US6279078B1 (en) 1996-06-28 2001-08-21 Compaq Computer Corporation Apparatus and method for synchronizing a cache mode in a dual controller, dual cache memory system operating in a plurality of cache modes
US5761734A (en) 1996-08-13 1998-06-02 International Business Machines Corporation Token-based serialisation of instructions in a multiprocessor system
US5933601A (en) 1996-09-30 1999-08-03 Ncr Corporation Method for systems management of object-based computer networks
US5790114A (en) 1996-10-04 1998-08-04 Microtouch Systems, Inc. Electronic whiteboard with multi-functional user interface
US5758359A (en) 1996-10-24 1998-05-26 Digital Equipment Corporation Method and apparatus for performing retroactive backups in a computer system
US5907621A (en) 1996-11-15 1999-05-25 International Business Machines Corporation System and method for session management
US6487644B1 (en) 1996-11-22 2002-11-26 Veritas Operating Corporation System and method for multiplexed data back-up to a storage tape and restore operations using client identification tags
US6148377A (en) 1996-11-22 2000-11-14 Mangosoft Corporation Shared memory computer networks
US5875478A (en) * 1996-12-03 1999-02-23 Emc Corporation Computer backup using a file system, network, disk, tape and remote archiving repository media system
US5926836A (en) 1996-12-03 1999-07-20 Emc Corporation Computer and associated method for restoring data backed up on archive media
US5878408A (en) * 1996-12-06 1999-03-02 International Business Machines Corporation Data management system and process
US6131095A (en) 1996-12-11 2000-10-10 Hewlett-Packard Company Method of accessing a target entity over a communications network
US6009274A (en) 1996-12-13 1999-12-28 3Com Corporation Method and apparatus for automatically updating software components on end systems over a network
US6202135B1 (en) 1996-12-23 2001-03-13 Emc Corporation System and method for reconstructing data associated with protected storage volume stored in multiple modules of back-up mass data storage facility
AU5929398A (en) * 1997-01-23 1998-08-18 Overland Data, Inc. Virtual media library
US5875481A (en) * 1997-01-30 1999-02-23 International Business Machines Corporation Dynamic reconfiguration of data storage devices to balance recycle throughput
US6963923B1 (en) 1997-02-10 2005-11-08 International Business Machines Corporation Method for file transfer restarts using standard internet protocol
US6049892C1 (en) 1997-02-24 2002-06-04 Ethos Software Corp Process and apparatus for downloading data from a server computer to a client computer
US6658526B2 (en) * 1997-03-12 2003-12-02 Storage Technology Corporation Network attached virtual data storage subsystem
US6012090A (en) * 1997-03-14 2000-01-04 At&T Corp. Client-side parallel requests for network services using group name association
US6952705B2 (en) 1997-03-25 2005-10-04 Mci, Inc. Method, system and program product that utilize a hierarchical conceptual framework to model an environment containing a collection of items
US6003089A (en) 1997-03-31 1999-12-14 Siemens Information And Communication Networks, Inc. Method for constructing adaptive packet lengths in a congested network
US5924102A (en) 1997-05-07 1999-07-13 International Business Machines Corporation System and method for managing critical files
WO1998051096A1 (en) 1997-05-09 1998-11-12 Dsc Telecom L.P. Communication system with rapid database synchronization
US6094416A (en) 1997-05-09 2000-07-25 I/O Control Corporation Multi-tier architecture for control network
US6158044A (en) 1997-05-21 2000-12-05 Epropose, Inc. Proposal based architecture system
US6112239A (en) 1997-06-18 2000-08-29 Intervu, Inc System and method for server-side optimization of data delivery on a distributed computer network
US5887134A (en) * 1997-06-30 1999-03-23 Sun Microsystems System and method for preserving message order while employing both programmed I/O and DMA operations
US5958005A (en) 1997-07-17 1999-09-28 Bell Atlantic Network Services, Inc. Electronic mail security
US6366988B1 (en) 1997-07-18 2002-04-02 Storactive, Inc. Systems and methods for electronic data storage management
US6137864A (en) 1997-07-25 2000-10-24 Lucent Technologies Inc. Specifiable delete times for voice messaging
US5877766A (en) 1997-08-15 1999-03-02 International Business Machines Corporation Multi-node user interface component and method thereof for use in accessing a plurality of linked records
DE69802294T2 (en) 1997-08-29 2002-05-16 Hewlett Packard Co SYSTEMS FOR DATA BACKUP AND RECOVERY
EP0899662A1 (en) 1997-08-29 1999-03-03 Hewlett-Packard Company Backup and restore system for a computer network
US6467035B2 (en) 1997-09-08 2002-10-15 Agere Systems Guardian Corp. System and method for performing table look-ups using a multiple data fetch architecture
US6067541A (en) 1997-09-17 2000-05-23 Microsoft Corporation Monitoring document changes in a file system of documents with the document change information stored in a persistent log
JP3901806B2 (en) 1997-09-25 2007-04-04 富士通株式会社 Information management system and secondary server
US5950205A (en) 1997-09-25 1999-09-07 Cisco Technology, Inc. Data transmission over the internet using a cache memory file system
US6275953B1 (en) 1997-09-26 2001-08-14 Emc Corporation Recovery from failure of a data processor in a network server
JP4128641B2 (en) 1997-10-13 2008-07-30 株式会社東芝 Data backup method
US6052735A (en) 1997-10-24 2000-04-18 Microsoft Corporation Electronic mail object synchronization between a desktop computer and mobile device
US6021415A (en) * 1997-10-29 2000-02-01 International Business Machines Corporation Storage management system with file aggregation and space reclamation within aggregated files
US7581077B2 (en) 1997-10-30 2009-08-25 Commvault Systems, Inc. Method and system for transferring data in a storage operation
US6418478B1 (en) 1997-10-30 2002-07-09 Commvault Systems, Inc. Pipelined high speed data transfer mechanism
US7209972B1 (en) 1997-10-30 2007-04-24 Commvault Systems, Inc. High speed data transfer mechanism
JP4363676B2 (en) * 1997-10-31 2009-11-11 株式会社東芝 Computer system
US6061692A (en) 1997-11-04 2000-05-09 Microsoft Corporation System and method for administering a meta database as an integral component of an information server
US6260068B1 (en) * 1998-06-10 2001-07-10 Compaq Computer Corporation Method and apparatus for migrating resources in a multi-processor computer system
JPH11143754A (en) 1997-11-05 1999-05-28 Hitachi Ltd Version information and constitution information display method and device therefor, and computer readable recording medium for recording version information and constitution information display program
JP3665460B2 (en) 1997-12-05 2005-06-29 富士通株式会社 Route selection system, method, and recording medium by response time tuning of distributed autonomous cooperation type
US6304880B1 (en) 1997-12-12 2001-10-16 International Business Machines Corporation Automated reclamation scheduling override in a virtual tape server
US6131190A (en) * 1997-12-18 2000-10-10 Sidwell; Leland P. System for modifying JCL parameters to optimize data storage allocations
US6088697A (en) * 1997-12-18 2000-07-11 International Business Machines Corporation Dynamic change management in an extended remote copy operation
US6023710A (en) * 1997-12-23 2000-02-08 Microsoft Corporation System and method for long-term administration of archival storage
US6374336B1 (en) 1997-12-24 2002-04-16 Avid Technology, Inc. Computer system and process for transferring multiple high bandwidth streams of data between multiple storage units and multiple applications in a scalable and reliable manner
US6076148A (en) 1997-12-26 2000-06-13 Emc Corporation Mass 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
US6262749B1 (en) 1997-12-31 2001-07-17 Acuson Corporation Ultrasonic system and method for data transfer, storage and/or processing
US6154787A (en) 1998-01-21 2000-11-28 Unisys Corporation Grouping 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
US6131148A (en) 1998-01-26 2000-10-10 International Business Machines Corporation Snapshot copy of a secondary volume of a PPRC pair
US6260069B1 (en) 1998-02-10 2001-07-10 International Business Machines Corporation Direct data retrieval in a distributed computing system
US6105129A (en) 1998-02-18 2000-08-15 Advanced Micro Devices, Inc. Converting register data from a first format type to a second format type if a second type instruction consumes data produced by a first type instruction
US6374363B1 (en) 1998-02-24 2002-04-16 Adaptec, Inc. Method for generating a footprint image file for an intelligent backup and restoring system
DE69816415T2 (en) * 1998-03-02 2004-04-15 Hewlett-Packard Co. (N.D.Ges.D.Staates Delaware), Palo Alto Data Backup System
US6026414A (en) * 1998-03-05 2000-02-15 International Business Machines Corporation System including a proxy client to backup files in a distributed computing environment
US6292783B1 (en) 1998-03-06 2001-09-18 Plexar & Associates Phone-assisted clinical document information computer system for use in home healthcare, post-acute clinical care, hospice and home infusion applications
US6631477B1 (en) 1998-03-13 2003-10-07 Emc Corporation Host system for mass storage business continuance volumes
US6161111A (en) * 1998-03-31 2000-12-12 Emc Corporation System and method for performing file-handling operations in a digital data processing system using an operating system-independent file map
US6175829B1 (en) * 1998-04-22 2001-01-16 Nec Usa, Inc. Method and apparatus for facilitating query reformulation
US6167402A (en) * 1998-04-27 2000-12-26 Sun Microsystems, Inc. High performance message store
US6163856A (en) 1998-05-29 2000-12-19 Sun Microsystems, Inc. Method and apparatus for file system disaster recovery
US6154852A (en) 1998-06-10 2000-11-28 International Business Machines Corporation Method and apparatus for data backup and recovery
US6438595B1 (en) * 1998-06-24 2002-08-20 Emc Corporation Load balancing using directory services in a data processing system
US6665687B1 (en) 1998-06-26 2003-12-16 Alexander James Burke Composite user interface and search system for internet and multimedia applications
US6421711B1 (en) 1998-06-29 2002-07-16 Emc Corporation Virtual ports for data transferring of a data storage system
US6366986B1 (en) 1998-06-30 2002-04-02 Emc Corporation Method and apparatus for differential backup in a computer storage system
US6542909B1 (en) 1998-06-30 2003-04-01 Emc Corporation System for determining mapping of logical objects in a computer system
US6094605A (en) 1998-07-06 2000-07-25 Storage Technology Corporation Virtual automated cartridge system
US6269431B1 (en) 1998-08-13 2001-07-31 Emc Corporation Virtual storage and block level direct access of secondary storage for recovery of backup data
US6353878B1 (en) * 1998-08-13 2002-03-05 Emc Corporation Remote control of backup media in a secondary storage subsystem through access to a primary storage subsystem
GB2341249A (en) 1998-08-17 2000-03-08 Connected Place Limited A method of generating a difference file defining differences between an updated file and a base file
US6446077B2 (en) * 1998-09-21 2002-09-03 Microsoft Corporation Inherited information propagator for objects
US6304914B1 (en) 1998-09-22 2001-10-16 Microsoft Corporation Method and apparatus for pre-compression packaging
US6195695B1 (en) * 1998-10-27 2001-02-27 International Business Machines Corporation Data processing system and method for recovering from system crashes
US6516314B1 (en) * 1998-11-17 2003-02-04 Telefonaktiebolaget L M Ericsson (Publ) Optimization of change log handling
US6516327B1 (en) * 1998-12-24 2003-02-04 International Business Machines Corporation System and method for synchronizing data in multiple databases
US6397308B1 (en) 1998-12-31 2002-05-28 Emc Corporation Apparatus and method for differential backup and restoration of data in a computer storage system
US7107395B1 (en) 1998-12-31 2006-09-12 Emc Corporation Apparatus and methods for operating a computer storage system
US6487561B1 (en) * 1998-12-31 2002-11-26 Emc Corporation Apparatus and methods for copying, backing up, and restoring data using a backup segment size larger than the storage block size
US6212512B1 (en) 1999-01-06 2001-04-03 Hewlett-Packard Company Integration of a database into file management software for protecting, tracking and retrieving data
US6324581B1 (en) 1999-03-03 2001-11-27 Emc Corporation File 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
US6350199B1 (en) * 1999-03-16 2002-02-26 International Game Technology Interactive gaming machine and method with customized game screen presentation
US6681230B1 (en) * 1999-03-25 2004-01-20 Lucent Technologies Inc. Real-time event processing system with service authoring environment
JP3763992B2 (en) 1999-03-30 2006-04-05 富士通株式会社 Data processing apparatus and recording medium
US6389432B1 (en) 1999-04-05 2002-05-14 Auspex Systems, Inc. Intelligent virtual volume access
US6804714B1 (en) * 1999-04-16 2004-10-12 Oracle International Corporation Multidimensional repositories for problem discovery and capacity planning of database applications
US6516348B1 (en) 1999-05-21 2003-02-04 Macfarlane Druce Ian Craig Rattray Collecting and predicting capacity information for composite network resource formed by combining ports of an access server and/or links of wide arear network
US6564271B2 (en) 1999-06-09 2003-05-13 Qlogic Corporation Method and apparatus for automatically transferring I/O blocks between a host system and a host adapter
US6519679B2 (en) * 1999-06-11 2003-02-11 Dell Usa, L.P. Policy based storage configuration
US6539462B1 (en) * 1999-07-12 2003-03-25 Hitachi Data Systems Corporation Remote data copy using a prospective suspend command
US7035880B1 (en) * 1999-07-14 2006-04-25 Commvault Systems, Inc. Modular backup and retrieval system used in conjunction with a storage area network
US7389311B1 (en) 1999-07-15 2008-06-17 Commvault Systems, Inc. Modular backup and retrieval system
US7395282B1 (en) * 1999-07-15 2008-07-01 Commvault Systems, Inc. Hierarchical backup and retrieval system
US6538669B1 (en) * 1999-07-15 2003-03-25 Dell Products L.P. Graphical user interface for configuration of a storage system
US6490666B1 (en) 1999-08-20 2002-12-03 Microsoft Corporation Buffering data in a hierarchical data storage environment
US6771595B1 (en) * 1999-08-31 2004-08-03 Intel Corporation Apparatus and method for dynamic resource allocation in a network environment
CA2385683A1 (en) 1999-09-13 2001-04-05 Healinx A message and program system supporting communication
US6343324B1 (en) * 1999-09-13 2002-01-29 International Business Machines Corporation Method 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
FR2799023B1 (en) * 1999-09-24 2003-04-18 France Telecom METHOD FOR THEMATIC CLASSIFICATION OF DOCUMENTS, MODULE FOR THEMATIC CLASSIFICATION AND SEARCH ENGINE INCORPORATING SUCH A MODULE
US6363464B1 (en) * 1999-10-08 2002-03-26 Lucent Technologies Inc. Redundant processor controlled system
US6643801B1 (en) * 1999-10-28 2003-11-04 General Electric Company Method and system for estimating time of occurrence of machine-disabling failures
TW454120B (en) * 1999-11-11 2001-09-11 Miralink Corp Flexible remote data mirroring
US6684191B1 (en) 1999-11-22 2004-01-27 International Business Machines Corporation System and method for assessing a procurement and accounts payable system
US6434681B1 (en) 1999-12-02 2002-08-13 Emc Corporation Snapshot copy facility for a data storage system permitting continued host read/write access
KR20020090206A (en) 1999-12-07 2002-11-30 데이타 파운데이션 인코퍼레이션 Scalable storage architecture
US6460055B1 (en) 1999-12-16 2002-10-01 Livevault Corporation Systems and methods for backing up data files
US6401178B1 (en) 1999-12-23 2002-06-04 Emc Corporatiion Data processing method and apparatus for enabling independent access to replicated data
ATE435464T1 (en) 2000-01-14 2009-07-15 Thinkstream Inc DISTRIBUTED INFORMATION NETWORK WITH GLOBAL ACCESS
US6564228B1 (en) * 2000-01-14 2003-05-13 Sun Microsystems, Inc. Method of enabling heterogeneous platforms to utilize a universal file system in a storage area network
US6721767B2 (en) 2000-01-31 2004-04-13 Commvault Systems, Inc. Application specific rollback in a computer system
US7003641B2 (en) * 2000-01-31 2006-02-21 Commvault Systems, Inc. Logical view with granular access to exchange data managed by a modular data and storage management system
US6658436B2 (en) * 2000-01-31 2003-12-02 Commvault Systems, Inc. Logical view and access to data managed by a modular data and storage management system
US6760723B2 (en) 2000-01-31 2004-07-06 Commvault Systems Inc. Storage management across multiple time zones
US7065538B2 (en) 2000-02-11 2006-06-20 Quest Software, Inc. System and method for reconciling transactions between a replication system and a recovered database
US6647473B1 (en) 2000-02-16 2003-11-11 Microsoft Corporation Kernel-based crash-consistency coordinator
US6651075B1 (en) 2000-02-16 2003-11-18 Microsoft Corporation Support for multiple temporal snapshots of same volume
US6473775B1 (en) 2000-02-16 2002-10-29 Microsoft Corporation System and method for growing differential file on a base volume of a snapshot
US6615223B1 (en) 2000-02-29 2003-09-02 Oracle International Corporation Method and system for data replication
US20020120741A1 (en) * 2000-03-03 2002-08-29 Webb Theodore S. Systems and methods for using distributed interconnects in information management enviroments
US6487645B1 (en) 2000-03-06 2002-11-26 International Business Machines Corporation Data storage subsystem with fairness-driven update blocking
US20010032172A1 (en) 2000-03-17 2001-10-18 Surveyplanet, Inc. System and method for requesting proposals and awarding contracts for provision of services
US6587970B1 (en) 2000-03-22 2003-07-01 Emc Corporation Method and apparatus for performing site failover
US6728733B2 (en) 2000-03-29 2004-04-27 Komatsu Wall System Development Co., Ltd. System, method, and program product for administrating document file in computerized network system
US7111189B1 (en) 2000-03-30 2006-09-19 Hewlett-Packard Development Company, L.P. Method for transaction log failover merging during asynchronous operations in a data storage network
US20020023051A1 (en) * 2000-03-31 2002-02-21 Kunzle Adrian E. System and method for recommending financial products to a customer based on customer needs and preferences
US20020049778A1 (en) 2000-03-31 2002-04-25 Bell Peter W. System and method of information outsourcing
WO2001075679A1 (en) * 2000-04-04 2001-10-11 Metamatrix, Inc. A system and method for accessing data in disparate information sources
AU2001293359A1 (en) 2000-04-14 2001-10-30 Mathias Client Management Software Company Method and system for interfacing clients with relationship management (rm) accounts and for permissioning marketing
US6571310B1 (en) 2000-04-20 2003-05-27 International Business Machines Corporation Method and apparatus for managing a heterogeneous data storage system
US6356801B1 (en) * 2000-05-19 2002-03-12 International Business Machines Corporation High availability work queuing in an automated data storage library
EP1158409B1 (en) 2000-05-25 2008-05-28 Hitachi, Ltd. Storage system making possible data synchronisation confirmation at time of asynchronous remote copy
US6564229B1 (en) 2000-06-08 2003-05-13 International Business Machines Corporation System and method for pausing and resuming move/copy operations
US6665815B1 (en) 2000-06-22 2003-12-16 Hewlett-Packard Development Company, L.P. Physical incremental backup using snapshots
US6330642B1 (en) * 2000-06-29 2001-12-11 Bull Hn Informatin Systems Inc. Three interconnected raid disk controller data processing system architecture
EP1174795A1 (en) 2000-07-19 2002-01-23 Hewlett-Packard Company, A Delaware Corporation Multiplexing computing apparatus
US20020049738A1 (en) 2000-08-03 2002-04-25 Epstein Bruce A. Information collaboration and reliability assessment
US6925476B1 (en) * 2000-08-17 2005-08-02 Fusionone, Inc. Updating application data including adding first change log to aggreagate change log comprising summary of changes
US7082441B1 (en) 2000-08-17 2006-07-25 Emc Corporation Method and storage and manipulation of storage system metrics
US6886020B1 (en) 2000-08-17 2005-04-26 Emc Corporation Method and apparatus for storage system metrics management and archive
US6751635B1 (en) 2000-08-18 2004-06-15 Network Appliance, Inc. File deletion and truncation using a zombie file space
GB2366014B (en) 2000-08-19 2004-10-13 Ibm Free space collection in information storage systems
US7278142B2 (en) 2000-08-24 2007-10-02 Veritas Operating Corporation Dynamic computing environment using remotely allocable resources
US7269641B2 (en) 2000-08-30 2007-09-11 Sun Microsystems, Inc. Remote reconfiguration system
US6732125B1 (en) 2000-09-08 2004-05-04 Storage Technology Corporation Self archiving log structured volume with intrinsic data protection
WO2003107219A1 (en) * 2000-09-11 2003-12-24 Zambeel, Inc. Storage system having partitioned migratable metadata
EP1193616A1 (en) 2000-09-29 2002-04-03 Sony France S.A. Fixed-length sequence generation of items out of a database using descriptors
US6611849B1 (en) * 2000-09-29 2003-08-26 Palm Source, Inc. System for synchronizing databases on multiple devices utilizing a home base
JP2002108662A (en) 2000-10-02 2002-04-12 Fujitsu Ltd Method for managing information
US6973553B1 (en) 2000-10-20 2005-12-06 International Business Machines Corporation Method and apparatus for using extended disk sector formatting to assist in backup and hierarchical storage management
US20020091712A1 (en) 2000-10-28 2002-07-11 Martin Andrew Richard Data-base caching system and method of operation
US7106691B1 (en) * 2000-11-01 2006-09-12 At&T Corp. Method for tracking source and destination internet protocol data
US7068597B1 (en) 2000-11-27 2006-06-27 3Com Corporation System and method for automatic load balancing in a data-over-cable network
US7225219B2 (en) 2000-11-29 2007-05-29 Broadspider Networks, Inc. Distributed caching architecture for computer networks
US6871271B2 (en) * 2000-12-21 2005-03-22 Emc Corporation Incrementally restoring a mass storage device to a prior state
US6647396B2 (en) 2000-12-28 2003-11-11 Trilogy Development Group, Inc. Classification based content management system
US6799258B1 (en) 2001-01-10 2004-09-28 Datacore Software Corporation Methods and apparatus for point-in-time volumes
US6978265B2 (en) 2001-01-16 2005-12-20 Lakeside Software, Inc. System and method for managing information for a plurality of computer systems in a distributed network
US20020124137A1 (en) * 2001-01-29 2002-09-05 Ulrich Thomas R. Enhancing disk array performance via variable parity based load balancing
US6862692B2 (en) * 2001-01-29 2005-03-01 Adaptec, Inc. Dynamic redistribution of parity groups
US7734715B2 (en) 2001-03-01 2010-06-08 Ricoh Company, Ltd. System, computer program product and method for managing documents
US7194454B2 (en) 2001-03-12 2007-03-20 Lucent Technologies Method for organizing records of database search activity by topical relevance
US6836779B2 (en) 2001-03-13 2004-12-28 Christian D. Poulin Network transaction method
US6728736B2 (en) 2001-03-14 2004-04-27 Storage Technology Corporation System and method for synchronizing a data copy using an accumulation remote copy trio
US7177866B2 (en) * 2001-03-16 2007-02-13 Gravic, Inc. Asynchronous coordinated commit replication and dual write with replication transmission and locking of target database on updates only
US7096269B2 (en) * 2001-03-30 2006-08-22 Hitachi, Ltd. Path selection methods for storage based remote copy
JP3693958B2 (en) 2001-04-05 2005-09-14 松下電器産業株式会社 Distributed document search method and apparatus, distributed document search program, and recording medium recording the program
US20020159437A1 (en) * 2001-04-27 2002-10-31 Foster Michael S. Method and system for network configuration discovery in a network manager
CA2347647A1 (en) 2001-05-15 2002-11-15 Ibm Canada Limited-Ibm Canada Limitee Storing and restoring snapshots of a computer process
US7111023B2 (en) 2001-05-24 2006-09-19 Oracle International Corporation Synchronous change data capture in a relational database
US6763351B1 (en) 2001-06-18 2004-07-13 Siebel Systems, Inc. Method, apparatus, and system for attaching search results
GB0116686D0 (en) 2001-07-07 2001-08-29 Hewlett Packard Co Data backup
US7062761B2 (en) 2001-07-10 2006-06-13 Micron Technology, Inc. Dynamic arrays and overlays with bounds policies
US7564970B2 (en) * 2004-08-12 2009-07-21 Cmla, Llc Exponential data transform to enhance security
US20030018657A1 (en) * 2001-07-18 2003-01-23 Imation Corp. Backup of data on a network
US6948038B2 (en) * 2001-07-24 2005-09-20 Microsoft Corporation System and method for backing up and restoring data
US7774492B2 (en) * 2001-07-26 2010-08-10 Citrix Systems, Inc. System, method and computer program product to maximize server throughput while avoiding server overload by controlling the rate of establishing server-side net work connections
US7685126B2 (en) * 2001-08-03 2010-03-23 Isilon Systems, Inc. System and methods for providing a distributed file system utilizing metadata to track information about data stored throughout the system
JP4923353B2 (en) 2001-08-08 2012-04-25 東洋紡績株式会社 Electret filter medium and method for producing the same
US6662198B2 (en) 2001-08-30 2003-12-09 Zoteca Inc. Method and system for asynchronous transmission, backup, distribution of data and file sharing
JP4161557B2 (en) 2001-09-03 2008-10-08 株式会社日立製作所 Packet transfer method and apparatus
US20030061491A1 (en) * 2001-09-21 2003-03-27 Sun Microsystems, Inc. System and method for the allocation of network storage
US7024517B1 (en) * 2001-09-27 2006-04-04 Emc Corporation System and method for configuring data storage in accordance with workload requirements
EP1442387A4 (en) 2001-09-28 2008-01-23 Commvault Systems Inc System and method for archiving objects in an information store
DE60232165D1 (en) 2001-09-28 2009-06-10 Commvault Systems Inc SYSTEM AND METHOD FOR PRODUCING AND MANAGING FAST RECOVERY VOLUME
US20030065759A1 (en) * 2001-10-01 2003-04-03 Britt Julie Anne Event driven storage resource metering
US6925512B2 (en) 2001-10-15 2005-08-02 Intel Corporation Communication between two embedded processors
AU2002352853A1 (en) 2001-11-20 2003-06-10 Service Tune, Inc. Service transaction management system and process
US7596586B2 (en) 2003-04-03 2009-09-29 Commvault Systems, Inc. System and method for extended media retention
AU2002365580A1 (en) 2001-11-23 2003-06-10 Commvault Systems, Inc. Selective data replication system and method
US7296125B2 (en) 2001-11-29 2007-11-13 Emc Corporation Preserving a snapshot of selected data of a mass storage system
US6898688B2 (en) 2001-12-28 2005-05-24 Storage Technology Corporation Data management appliance
EP1324216A1 (en) 2001-12-28 2003-07-02 Deutsche Thomson-Brandt Gmbh Machine for classification of metadata
US6938180B1 (en) 2001-12-31 2005-08-30 Emc Corporation Logical restores of physically backed up data
US7139932B2 (en) 2002-01-03 2006-11-21 Hitachi, Ltd. Data synchronization of multiple remote storage after remote copy suspension
US6948089B2 (en) 2002-01-10 2005-09-20 Hitachi, Ltd. Apparatus and method for multiple generation remote backup and fast restore
US7237075B2 (en) 2002-01-22 2007-06-26 Columbia Data Products, Inc. Persistent snapshot methods
US20030220949A1 (en) 2002-01-22 2003-11-27 Columbia Data Products, Inc. Automatic deletion in data storage management
US6748504B2 (en) 2002-02-15 2004-06-08 International Business Machines Corporation Deferred copy-on-write of a snapshot
US7343365B2 (en) 2002-02-20 2008-03-11 Microsoft Corporation Computer system architecture for automatic context associations
JP2003248611A (en) * 2002-02-26 2003-09-05 Hitachi Ltd Storage management integration system and its storage management control method
US7072304B2 (en) * 2002-02-27 2006-07-04 Nortel Networks Limited Network path selection based on bandwidth
US7373364B1 (en) 2002-03-05 2008-05-13 Network Appliance, Inc. System and method for creating a point-in-time restoration of a database file
US6941393B2 (en) 2002-03-05 2005-09-06 Agilent Technologies, Inc. Pushback FIFO
US6880051B2 (en) 2002-03-14 2005-04-12 International Business Machines Corporation Method, system, and program for maintaining backup copies of files in a backup storage device
US20030177149A1 (en) 2002-03-18 2003-09-18 Coombs David Lawrence System and method for data backup
US7051050B2 (en) 2002-03-19 2006-05-23 Netwrok Appliance, Inc. System and method for restoring a single file from a snapshot
EP1349088B1 (en) 2002-03-19 2010-11-03 Network Appliance, Inc. System and method for determining and transmitting changes in snapshots
US7467167B2 (en) 2002-03-19 2008-12-16 Network Appliance, Inc. System and method for coalescing a plurality of snapshots
US6993539B2 (en) * 2002-03-19 2006-01-31 Network Appliance, Inc. System and method for determining changes in two snapshots and for transmitting changes to destination snapshot
US7007046B2 (en) * 2002-03-19 2006-02-28 Network Appliance, Inc. Format for transmission file system information between a source and a destination
US7475098B2 (en) 2002-03-19 2009-01-06 Network Appliance, Inc. System and method for managing a plurality of snapshots
US7225204B2 (en) 2002-03-19 2007-05-29 Network Appliance, Inc. System and method for asynchronous mirroring of snapshots at a destination using a purgatory directory and inode mapping
US7032131B2 (en) 2002-03-26 2006-04-18 Hewlett-Packard Development Company, L.P. System and method for ensuring merge completion in a storage area network
US6772841B2 (en) * 2002-04-11 2004-08-10 Halliburton Energy Services, Inc. Expandable float shoe and associated methods
US6983351B2 (en) * 2002-04-11 2006-01-03 International Business Machines Corporation System and method to guarantee overwrite of expired data in a virtual tape server
US7532340B2 (en) 2002-04-19 2009-05-12 Toshiba Tec Kabushiki Kaisha Document management system rule-based automation
US6981177B2 (en) 2002-04-19 2005-12-27 Computer Associates Think, Inc. Method and system for disaster recovery
US7546364B2 (en) 2002-05-16 2009-06-09 Emc Corporation Replication of remote copy data for internet protocol (IP) transmission
US6871163B2 (en) * 2002-05-31 2005-03-22 Sap Aktiengesellschaft Behavior-based adaptation of computer systems
US7269612B2 (en) 2002-05-31 2007-09-11 International Business Machines Corporation Method, system, and program for a policy based storage manager
US6944796B2 (en) 2002-06-27 2005-09-13 Intel Corporation Method and system to implement a system event log for system manageability
US7085959B2 (en) 2002-07-03 2006-08-01 Hewlett-Packard Development Company, L.P. Method and apparatus for recovery from loss of lock step
US7844577B2 (en) 2002-07-15 2010-11-30 Symantec Corporation System and method for maintaining a backup storage system for a computer system
US7085787B2 (en) * 2002-07-19 2006-08-01 International Business Machines Corporation Capturing data changes utilizing data-space tracking
US6952758B2 (en) 2002-07-31 2005-10-04 International Business Machines Corporation Method and system for providing consistent data modification information to clients in a storage system
US6792518B2 (en) 2002-08-06 2004-09-14 Emc Corporation Data storage system having mata bit maps for indicating whether data blocks are invalid in snapshot copies
US20040039679A1 (en) * 2002-08-14 2004-02-26 Norton David W. Generation and acceptance of tailored offers
US20040107199A1 (en) 2002-08-22 2004-06-03 Mdt Inc. Computer application backup method and system
US7103731B2 (en) 2002-08-29 2006-09-05 International Business Machines Corporation Method, system, and program for moving data among storage units
US7810067B2 (en) 2002-08-30 2010-10-05 Sap Aktiengesellschaft Development processes representation and management
US7130970B2 (en) * 2002-09-09 2006-10-31 Commvault Systems, Inc. Dynamic storage device pooling in a computer system
US7246140B2 (en) 2002-09-10 2007-07-17 Exagrid Systems, Inc. Method and apparatus for storage system to provide distributed data storage and protection
US7234115B1 (en) 2002-09-26 2007-06-19 Home Director, Inc. Home entertainment system and method
US7640342B1 (en) 2002-09-27 2009-12-29 Emc Corporation System and method for determining configuration of one or more data storage systems
US6938135B1 (en) 2002-10-04 2005-08-30 Veritas Operating Corporation Incremental backup of a data volume
WO2004034197A2 (en) 2002-10-07 2004-04-22 Commvault Systems, Inc. System and method for managing stored data
US7707184B1 (en) 2002-10-09 2010-04-27 Netapp, Inc. System and method for snapshot full backup and hard recovery of a database
US7401064B1 (en) 2002-11-07 2008-07-15 Data Advantage Group, Inc. Method and apparatus for obtaining metadata from multiple information sources within an organization in real time
US8121978B2 (en) 2002-11-15 2012-02-21 Sybase, Inc. Database system providing improved methods for data replication
WO2004047078A2 (en) 2002-11-20 2004-06-03 Filesx Ltd. Fast backup storage and fast recovery of data (fbsrd)
KR101168423B1 (en) * 2003-02-05 2012-07-25 가부시키가이샤 자나비 인포메틱스 Path search method of navigation apparatus and display method of traffic information
US7177886B2 (en) 2003-02-07 2007-02-13 International Business Machines Corporation Apparatus and method for coordinating logical data replication with highly available data replication
US7197490B1 (en) * 2003-02-10 2007-03-27 Network Appliance, Inc. System and method for lazy-copy sub-volume load balancing in a network attached storage pool
US7827283B2 (en) 2003-02-19 2010-11-02 International Business Machines Corporation System for managing and controlling storage access requirements
US20040193953A1 (en) 2003-02-21 2004-09-30 Sun Microsystems, Inc. Method, system, and program for maintaining application program configuration settings
US7231544B2 (en) 2003-02-27 2007-06-12 Hewlett-Packard Development Company, L.P. Restoring data from point-in-time representations of the data
US7111021B1 (en) 2003-03-21 2006-09-19 Network Appliance, Inc. System and method for efficient space accounting in a file system with snapshots
US7174433B2 (en) 2003-04-03 2007-02-06 Commvault Systems, Inc. System and method for dynamically sharing media in a computer network
US7158985B1 (en) * 2003-04-09 2007-01-02 Cisco Technology, Inc. Method and apparatus for efficient propagation of large datasets under failure conditions
US6839724B2 (en) * 2003-04-17 2005-01-04 Oracle International Corporation Metamodel-based metadata change management
US7155465B2 (en) 2003-04-18 2006-12-26 Lee Howard F Method and apparatus for automatically archiving a file system
US20040215724A1 (en) 2003-04-28 2004-10-28 Microsoft Corporation Email service error recovery
US7673000B2 (en) 2003-04-28 2010-03-02 Microsoft Corporation Email service
JP2004334574A (en) 2003-05-08 2004-11-25 Hitachi Ltd Operation managing program and method of storage, and managing computer
US7853462B2 (en) 2003-05-12 2010-12-14 I2 Technologies Us, Inc. Optimizing an inventory of a supply chain
US7240219B2 (en) 2003-05-25 2007-07-03 Sandisk Il Ltd. Method and system for maintaining backup of portable storage devices
JP2004354752A (en) 2003-05-29 2004-12-16 Sumitomo Electric Ind Ltd Joint folder for single-core bidirectional optical module
US20050015409A1 (en) 2003-05-30 2005-01-20 Arkivio, Inc. Techniques for performing operations on migrated files without recalling data
US20040249883A1 (en) 2003-06-09 2004-12-09 Venkataraman Srinivasan System and method of website data transfer handshake
US20040254919A1 (en) 2003-06-13 2004-12-16 Microsoft Corporation Log parser
US20040260678A1 (en) 2003-06-18 2004-12-23 Microsoft Corporation State based configuration failure detection using checkpoint comparison
JP2005011429A (en) 2003-06-19 2005-01-13 Hitachi Ltd File management method and recorder, reproducing device, and recording medium
US7275177B2 (en) 2003-06-25 2007-09-25 Emc Corporation Data recovery with internet protocol replication with or without full resync
US7454569B2 (en) * 2003-06-25 2008-11-18 Commvault Systems, Inc. Hierarchical system and method for performing storage operations in a computer network
US7567991B2 (en) 2003-06-25 2009-07-28 Emc Corporation Replication of snapshot using a file system copy differential
WO2005001646A2 (en) 2003-06-25 2005-01-06 Arkivio, Inc. Techniques for performing policy automated operations
US8095511B2 (en) 2003-06-30 2012-01-10 Microsoft Corporation Database data recovery system and method
US7694086B1 (en) 2003-06-30 2010-04-06 Symantec Operating Corporation Method and system for incremental backup of data volumes
US7617369B1 (en) * 2003-06-30 2009-11-10 Symantec Operating Corporation Fast failover with multiple secondary nodes
US7203944B1 (en) * 2003-07-09 2007-04-10 Veritas Operating Corporation Migrating virtual machines among computer systems to balance load caused by virtual machines
JP4421230B2 (en) * 2003-08-12 2010-02-24 株式会社日立製作所 Performance information analysis method
JP2007502470A (en) * 2003-08-14 2007-02-08 コンペレント・テクノロジーズ Virtual disk drive system and method
US7093089B2 (en) * 2003-08-18 2006-08-15 Hewlett-Packard Development Company, Lp. Systems and methods for storing data on computer systems
US7702670B1 (en) 2003-08-29 2010-04-20 Emc Corporation System and method for tracking changes associated with incremental copying
US7330859B2 (en) 2003-09-10 2008-02-12 International Business Machines Corporation Database backup system using data and user-defined routines replicators for maintaining a copy of database on a secondary server
US6912482B2 (en) 2003-09-11 2005-06-28 Veritas Operating Corporation Data storage analysis mechanism
US7188292B2 (en) 2003-09-26 2007-03-06 Nortel Networks Limited Data mirroring system
US20050071391A1 (en) 2003-09-29 2005-03-31 International Business Machines Corporation High availability data replication set up using external backup and restore
US7200620B2 (en) 2003-09-29 2007-04-03 International Business Machines Corporation High availability data replication of smart large objects
US7225208B2 (en) 2003-09-30 2007-05-29 Iron Mountain Incorporated Systems and methods for backing up data files
JP4492084B2 (en) * 2003-10-07 2010-06-30 株式会社日立製作所 Storage path control method
US7496690B2 (en) * 2003-10-09 2009-02-24 Intel Corporation Method, system, and program for managing memory for data transmission through a network
US7194487B1 (en) 2003-10-16 2007-03-20 Veritas Operating Corporation System and method for recording the order of a change caused by restoring a primary volume during ongoing replication of the primary volume
JP4267420B2 (en) * 2003-10-20 2009-05-27 株式会社日立製作所 Storage apparatus and backup acquisition method
JP4066932B2 (en) 2003-11-10 2008-03-26 株式会社日立製作所 Computer resource allocation method based on prediction
US7315923B2 (en) * 2003-11-13 2008-01-01 Commvault Systems, Inc. System and method for combining data streams in pipelined storage operations in a storage network
US7613748B2 (en) 2003-11-13 2009-11-03 Commvault Systems, Inc. Stored data reverification management system and method
WO2005048085A2 (en) 2003-11-13 2005-05-26 Commvault Systems, Inc. System and method for performing an image level snapshot and for restoring partial volume data
US7440982B2 (en) * 2003-11-13 2008-10-21 Commvault Systems, Inc. System and method for stored data archive verification
WO2005050381A2 (en) * 2003-11-13 2005-06-02 Commvault Systems, Inc. Systems and methods for performing storage operations using network attached storage
US7412583B2 (en) 2003-11-14 2008-08-12 International Business Machines Corporation Virtual incremental storage method
US7284153B2 (en) * 2003-11-17 2007-10-16 International Business Machines Corporation Apparatus, method, and system for logging diagnostic information
US7225210B2 (en) 2003-11-20 2007-05-29 Overland Storage, Inc. Block level data snapshot system and method
EP1687745A2 (en) 2003-11-26 2006-08-09 Veritas Operating Corporation System and method for generating extensible file system metadata and file system content processing
US7272606B2 (en) 2003-11-26 2007-09-18 Veritas Operating Corporation System and method for detecting and storing file content access information within a file system
US7228456B2 (en) 2003-12-01 2007-06-05 Emc Corporation Data recovery for virtual ordered writes for multiple storage devices
US7155633B2 (en) 2003-12-08 2006-12-26 Solid Data Systems, Inc. Exchange server method and system
US7519726B2 (en) 2003-12-12 2009-04-14 International Business Machines Corporation Methods, apparatus and computer programs for enhanced access to resources within a network
US7720801B2 (en) 2003-12-19 2010-05-18 Netapp, Inc. System and method for supporting asynchronous data replication with very short update intervals
US20050138306A1 (en) 2003-12-19 2005-06-23 Panchbudhe Ankur P. Performance of operations on selected data in a storage area
US7469262B2 (en) * 2003-12-29 2008-12-23 Oracle International Corporation Customizable metadata merging framework
US7039661B1 (en) 2003-12-29 2006-05-02 Veritas Operating Corporation Coordinated dirty block tracking
US7293133B1 (en) 2003-12-31 2007-11-06 Veritas Operating Corporation Performing operations without requiring split mirrors in a multi-class file system
US7103740B1 (en) 2003-12-31 2006-09-05 Veritas Operating Corporation Backup mechanism for a multi-class file system
JP2005196673A (en) * 2004-01-09 2005-07-21 Hitachi Ltd Memory control system for storing operation information
JP2005217815A (en) 2004-01-30 2005-08-11 Hitachi Ltd Path control method
US7627617B2 (en) 2004-02-11 2009-12-01 Storage Technology Corporation Clustered hierarchical file services
JP2005235058A (en) 2004-02-23 2005-09-02 Hitachi Ltd Snapshot acquisition method, snapshot acquisition device, and computer program provided with snapshot acquisition function
US7216244B2 (en) * 2004-02-25 2007-05-08 Hitachi, Ltd. Data storage system with redundant storage media and method therefor
US7533181B2 (en) 2004-02-26 2009-05-12 International Business Machines Corporation Apparatus, system, and method for data access management
JP4454342B2 (en) * 2004-03-02 2010-04-21 株式会社日立製作所 Storage system and storage system control method
US7318134B1 (en) * 2004-03-16 2008-01-08 Emc Corporation Continuous data backup using distributed journaling
US8266406B2 (en) * 2004-04-30 2012-09-11 Commvault Systems, Inc. System and method for allocation of organizational resources
US7343356B2 (en) * 2004-04-30 2008-03-11 Commvault Systems, Inc. Systems and methods for storage modeling and costing
US7340652B2 (en) * 2004-04-30 2008-03-04 International Business Machines Corporation Invalidation of storage control unit cache metadata
US8055745B2 (en) * 2004-06-01 2011-11-08 Inmage Systems, Inc. Methods and apparatus for accessing data from a primary data storage system for secondary storage
US7383462B2 (en) * 2004-07-02 2008-06-03 Hitachi, Ltd. Method and apparatus for encrypted remote copy for secure data backup and restoration
WO2006014504A2 (en) 2004-07-07 2006-02-09 Sciencelogic, Llc Self configuring network management system
US7529898B2 (en) 2004-07-09 2009-05-05 International Business Machines Corporation Method for backing up and restoring data
US7131027B2 (en) * 2004-07-09 2006-10-31 Hitachi, Ltd. Method and apparatus for disk array based I/O routing and multi-layered external storage linkage
US7461101B2 (en) * 2004-07-13 2008-12-02 International Business Machines Corporation Method for reducing data loss and unavailability by integrating multiple levels of a storage hierarchy
US20060020616A1 (en) * 2004-07-22 2006-01-26 Geoffrey Hardy Indexing operational logs in a distributed processing system
US7467267B1 (en) 2004-07-23 2008-12-16 Sprint Communications Company L.P. Method and system for backing up or restoring data in remote devices over a communications network
JP4576923B2 (en) * 2004-08-09 2010-11-10 株式会社日立製作所 Storage system storage capacity management method
US7661135B2 (en) * 2004-08-10 2010-02-09 International Business Machines Corporation Apparatus, system, and method for gathering trace data indicative of resource activity
US7457980B2 (en) 2004-08-13 2008-11-25 Ken Qing Yang Data replication method over a limited bandwidth network by mirroring parities
US7257689B1 (en) 2004-10-15 2007-08-14 Veritas Operating Corporation System and method for loosely coupled temporal storage management
JP4507249B2 (en) * 2004-10-19 2010-07-21 株式会社日立製作所 System and method for controlling storage device updates
GB2435756B (en) 2004-11-05 2008-12-10 Commvault Systems Inc Method and system of pooling storage devices
WO2006053050A2 (en) 2004-11-08 2006-05-18 Commvault Systems, Inc. System and method for performing auxiliary storage operations
JP4349301B2 (en) 2004-11-12 2009-10-21 日本電気株式会社 Storage management system, method and program
US8959299B2 (en) * 2004-11-15 2015-02-17 Commvault Systems, Inc. Using a snapshot as a data source
US7529745B2 (en) 2004-11-19 2009-05-05 International Business Machines Corporation Method of verifying metadata of a migrated file
KR100611578B1 (en) 2004-11-23 2006-08-10 한국전자통신연구원 A resource allocation device for providing the differentiated service, and a method thereof
JP2006163843A (en) 2004-12-07 2006-06-22 Ricoh Co Ltd Parts management method and parts management program
US20060136685A1 (en) 2004-12-17 2006-06-22 Sanrad Ltd. Method and system to maintain data consistency over an internet small computer system interface (iSCSI) network
US7415488B1 (en) 2004-12-31 2008-08-19 Symantec Operating Corporation System and method for redundant storage consistency recovery
US7363444B2 (en) 2005-01-10 2008-04-22 Hewlett-Packard Development Company, L.P. Method for taking snapshots of data
US7512601B2 (en) 2005-01-18 2009-03-31 Microsoft Corporation Systems and methods that enable search engines to present relevant snippets
US7809691B1 (en) 2005-02-22 2010-10-05 Symantec Operating Corporation System and method of applying incremental changes prior to initialization of a point-in-time copy
US8005795B2 (en) 2005-03-04 2011-08-23 Emc Corporation Techniques for recording file operations and consistency points for producing a consistent copy
JP2006285448A (en) * 2005-03-31 2006-10-19 Oki Electric Ind Co Ltd Redundant system
US7461230B1 (en) * 2005-03-31 2008-12-02 Symantec Operating Corporation Maintaining spatial locality of write operations
US7765186B1 (en) 2005-04-13 2010-07-27 Progress Software Corporation Update-anywhere replication of distributed systems
JP2006302015A (en) 2005-04-21 2006-11-02 Hitachi Ltd Storage system and data management method
US8112605B2 (en) * 2005-05-02 2012-02-07 Commvault Systems, Inc. System and method for allocation of organizational resources
US7689467B1 (en) 2005-06-09 2010-03-30 At&T Intellectual Property Ii, Lp Arrangement for guiding user design of comprehensive product solution using on-the-fly data validation
US7496589B1 (en) * 2005-07-09 2009-02-24 Google Inc. Highly compressed randomly accessed storage of large tables with arbitrary columns
JP4733461B2 (en) * 2005-08-05 2011-07-27 株式会社日立製作所 Computer system, management computer, and logical storage area management method
US7716171B2 (en) 2005-08-18 2010-05-11 Emc Corporation Snapshot indexing
US20070043956A1 (en) * 2005-08-19 2007-02-22 Microsoft Corporation System and methods that facilitate third party code test development
US7617541B2 (en) 2005-09-09 2009-11-10 Netapp, Inc. Method and/or system to authorize access to stored data
JP4688617B2 (en) 2005-09-16 2011-05-25 株式会社日立製作所 Storage control system and method
JP4668763B2 (en) * 2005-10-20 2011-04-13 株式会社日立製作所 Storage device restore method and storage device
WO2007053314A2 (en) 2005-10-28 2007-05-10 Goldengate Software, Inc. Apparatus and method for creating a real time database replica
US7840285B2 (en) 2005-10-28 2010-11-23 Invensys Systems, Inc. Sequence of events recorder facility for an industrial process control environment
US8595633B2 (en) 2005-10-31 2013-11-26 Yahoo! Inc. Method and system for displaying contextual rotating advertisements
US7689736B2 (en) * 2005-11-07 2010-03-30 Dot Hill Systems Corporation Method and apparatus for a storage controller to dynamically determine the usage of onboard I/O ports
US7529748B2 (en) 2005-11-15 2009-05-05 Ji-Rong Wen Information classification paradigm
US20070113006A1 (en) 2005-11-16 2007-05-17 Elliott John C Apparatus and method to configure one or more storage arrays
WO2007062258A2 (en) * 2005-11-28 2007-05-31 Storagedna, Inc. Distributed file system with file fragmentation
WO2007062254A2 (en) 2005-11-28 2007-05-31 Commvault Systems, Inc. Systems and methods for data management
US7668879B2 (en) 2005-11-30 2010-02-23 Oracle International Corporation Database system configured for automatic failover with no data loss
US7627584B2 (en) 2005-11-30 2009-12-01 Oracle International Corporation Database system configured for automatic failover with no data loss
US7636743B2 (en) 2005-12-19 2009-12-22 Commvault Systems, Inc. Pathname translation in a data replication system
US7617262B2 (en) * 2005-12-19 2009-11-10 Commvault Systems, Inc. Systems and methods for monitoring application data in a data replication system
US7651593B2 (en) * 2005-12-19 2010-01-26 Commvault Systems, Inc. Systems and methods for performing data replication
US7543125B2 (en) 2005-12-19 2009-06-02 Commvault Systems, Inc. System and method for performing time-flexible calendric storage operations
US7617253B2 (en) 2005-12-19 2009-11-10 Commvault Systems, Inc. Destination systems and methods for performing data replication
US7606844B2 (en) * 2005-12-19 2009-10-20 Commvault Systems, Inc. System and method for performing replication copy storage operations
US8655850B2 (en) * 2005-12-19 2014-02-18 Commvault Systems, Inc. Systems and methods for resynchronizing information
CA2632935C (en) 2005-12-19 2014-02-04 Commvault Systems, Inc. Systems and methods for performing data replication
US7962709B2 (en) 2005-12-19 2011-06-14 Commvault Systems, Inc. Network redirector systems and methods for performing data replication
US20110010518A1 (en) * 2005-12-19 2011-01-13 Srinivas Kavuri Systems and Methods for Migrating Components in a Hierarchical Storage Network
US7500150B2 (en) 2005-12-30 2009-03-03 Microsoft Corporation Determining the level of availability of a computing resource
US8170985B2 (en) 2006-01-31 2012-05-01 Emc Corporation Primary stub file retention and secondary retention coordination in a hierarchical storage system
US7528745B2 (en) * 2006-02-15 2009-05-05 Qualcomm Incorporated Digital domain sampling rate converter
US7441092B2 (en) 2006-04-20 2008-10-21 Microsoft Corporation Multi-client cluster-based backup and restore
KR100877063B1 (en) 2006-05-29 2009-01-07 삼성전자주식회사 Apparatus and method for managing data
US7613750B2 (en) 2006-05-29 2009-11-03 Microsoft Corporation Creating frequent application-consistent backups efficiently
US8190571B2 (en) 2006-06-07 2012-05-29 Microsoft Corporation Managing data with backup server indexing
US7904681B1 (en) * 2006-06-30 2011-03-08 Emc Corporation Methods and systems for migrating data with minimal disruption
US8726242B2 (en) * 2006-07-27 2014-05-13 Commvault Systems, Inc. Systems and methods for continuous data replication
US8495102B2 (en) 2006-09-01 2013-07-23 International Business Machines Corporation Method, system, and program product for organizing a database
US7606842B2 (en) 2006-09-27 2009-10-20 Hewlett-Packard Development Company, L.P. Method of merging a clone file system with an original file system
KR100791325B1 (en) 2006-10-27 2008-01-03 삼성전자주식회사 Apparatus and method for managing nonvolatile memory
US20080103916A1 (en) 2006-10-31 2008-05-01 Jon Carlo Camarador Apparatuses, methods, and systems for capital management product enrollment
US7669029B1 (en) * 2006-11-15 2010-02-23 Network Appliance, Inc. Load balancing a data storage system
EP2102750B1 (en) 2006-12-04 2014-11-05 Commvault Systems, Inc. System and method for creating copies of data, such as archive copies
US7840537B2 (en) 2006-12-22 2010-11-23 Commvault Systems, Inc. System and method for storing redundant information
US7831566B2 (en) * 2006-12-22 2010-11-09 Commvault Systems, Inc. Systems and methods of hierarchical storage management, such as global management of storage operations
JP4900811B2 (en) 2007-03-30 2012-03-21 株式会社日立製作所 Storage system and storage control method
US8239351B2 (en) 2007-06-07 2012-08-07 Apple Inc. Methods and systems for managing permissions data
US20090150462A1 (en) 2007-12-07 2009-06-11 Brocade Communications Systems, Inc. Data migration operations in a distributed file system
US7930476B1 (en) 2007-12-28 2011-04-19 Emc Corporation Application aware storage resource provisioning
US8752093B2 (en) 2008-01-21 2014-06-10 At&T Intellectual Property I, L.P. System and method of providing recommendations related to a service system
US8170990B2 (en) 2008-05-30 2012-05-01 Hitachi, Ltd. Integrated remote replication in hierarchical storage systems
US8219524B2 (en) 2008-06-24 2012-07-10 Commvault Systems, Inc. Application-aware and remote single instance data management
US9098495B2 (en) 2008-06-24 2015-08-04 Commvault Systems, Inc. Application-aware and remote single instance data management
US8335776B2 (en) * 2008-07-02 2012-12-18 Commvault Systems, Inc. Distributed indexing system for data storage
US8166263B2 (en) * 2008-07-03 2012-04-24 Commvault Systems, Inc. Continuous data protection over intermittent connections, such as continuous data backup for laptops or wireless devices
US9495382B2 (en) 2008-12-10 2016-11-15 Commvault Systems, Inc. Systems and methods for performing discrete data replication
US8204859B2 (en) 2008-12-10 2012-06-19 Commvault Systems, Inc. Systems and methods for managing replicated database data
US8504517B2 (en) 2010-03-29 2013-08-06 Commvault Systems, Inc. Systems and methods for selective data replication
US8504515B2 (en) 2010-03-30 2013-08-06 Commvault Systems, Inc. Stubbing systems and methods in a data replication environment
US8725698B2 (en) 2010-03-30 2014-05-13 Commvault Systems, Inc. Stub file prioritization in a data replication system
US8352422B2 (en) * 2010-03-30 2013-01-08 Commvault Systems, Inc. Data restore systems and methods in a replication environment
WO2011150391A1 (en) 2010-05-28 2011-12-01 Commvault Systems, Inc. Systems and methods for performing data replication

Patent Citations (39)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030126200A1 (en) * 1996-08-02 2003-07-03 Wolff James J. Dynamic load balancing of a network of client and server computer
US20020019909A1 (en) * 1998-06-30 2002-02-14 D'errico Matthew J. Method and apparatus for managing virtual storage devices in a storage system
US6466950B1 (en) * 1998-10-20 2002-10-15 Mitsubishi Denki Kabushiki Kaisha Update log management device and an update log management method decreasing the data amount of transmitting and the update log amount of holding based on the result of comparing the amount of the update log with the amount of the updated data plus the log applied information
US6542972B2 (en) * 2000-01-31 2003-04-01 Commvault Systems, Inc. Logical view and access to physical storage in modular data and storage management system
US6629189B1 (en) * 2000-03-09 2003-09-30 Emc Corporation Method and apparatus for managing target devices in a multi-path computer system
US6792472B1 (en) * 2000-03-31 2004-09-14 International Business Machines Corporation System, method and computer readable medium for intelligent raid controllers operating as data routers
US6691209B1 (en) * 2000-05-26 2004-02-10 Emc Corporation Topological data categorization and formatting for a mass storage system
US20080205301A1 (en) * 2000-06-09 2008-08-28 International Business Machines Corporation System and program for selecting one of multiple paths to communicate with a device
US7093012B2 (en) * 2000-09-14 2006-08-15 Overture Services, Inc. System and method for enhancing crawling by extracting requests for webpages in an information flow
US20040133634A1 (en) * 2000-11-02 2004-07-08 Stanley Luke Switching system
US20040117438A1 (en) * 2000-11-02 2004-06-17 John Considine Switching system
US20050060613A1 (en) * 2001-01-23 2005-03-17 Adaptec, Inc. Methods and apparatus for a segregated interface for parameter configuration in a multi-path failover system
US7231391B2 (en) * 2001-02-06 2007-06-12 Quest Software, Inc. Loosely coupled database clusters with client connection fail-over
US20030023893A1 (en) * 2001-05-07 2003-01-30 Lee Whay S. Fault-tolerant routing scheme for a multi-path interconnection fabric in a storage network
US20030005119A1 (en) * 2001-06-28 2003-01-02 Intersan, Inc., A Delaware Corporation Automated creation of application data paths in storage area networks
US20030079018A1 (en) * 2001-09-28 2003-04-24 Lolayekar Santosh C. Load balancing in a storage network
US20040006572A1 (en) * 2002-04-10 2004-01-08 Hitachi, Ltd. Method and system for employing and managing storage
US20040006578A1 (en) * 2002-07-08 2004-01-08 Trsunyeng Yu System and method for distributed concurrent version management
US20040078632A1 (en) * 2002-10-21 2004-04-22 Infante Jon L. System with multiple path fail over, fail back and load balancing
US20040193625A1 (en) * 2003-03-27 2004-09-30 Atsushi Sutoh Data control method for duplicating data between computer systems
US20080114815A1 (en) * 2003-03-27 2008-05-15 Atsushi Sutoh Data control method for duplicating data between computer systems
US20090013014A1 (en) * 2003-06-18 2009-01-08 International Business Machines Corporation Method, system, and article of manufacture for mirroring data at storage locations
US20070033437A1 (en) * 2004-01-30 2007-02-08 Hitachi, Ltd. Data processing system
US20050172073A1 (en) * 2004-01-30 2005-08-04 Hewlett-Packard Development Company, L.P. Storage system including capability to move a virtual storage device group without moving data
US20050228875A1 (en) * 2004-04-13 2005-10-13 Arnold Monitzer System for estimating processing requirements
US20080313497A1 (en) * 2004-04-28 2008-12-18 Yusuke Hirakawa Data processing system
US7617321B2 (en) * 2004-05-07 2009-11-10 International Business Machines Corporation File system architecture requiring no direct access to user data from a metadata manager
US20050254456A1 (en) * 2004-05-14 2005-11-17 Sharp Kabushiki Kaisha Transmitter, receiver, data transfer system, transmission method, reception method, computer program for transmission, computer program for reception, and recording medium
US20060047931A1 (en) * 2004-08-27 2006-03-02 Nobuyuki Saika Method and program for creating a snapshot, and storage system
US20060107089A1 (en) * 2004-10-27 2006-05-18 Peter Jansz Diagnosing a path in a storage network
US20080228987A1 (en) * 2004-12-24 2008-09-18 Shuichi Yagi Storage system and method of storage system path control
US20060174075A1 (en) * 2005-01-31 2006-08-03 Atsushi Sutoh Method for creating and preserving snapshots in a storage system
US7502902B2 (en) * 2005-03-11 2009-03-10 Hitachi, Ltd. Storage system and data movement method
US20060206662A1 (en) * 2005-03-14 2006-09-14 Ludwig Thomas E Topology independent storage arrays and methods
US20060215564A1 (en) * 2005-03-23 2006-09-28 International Business Machines Corporation Root-cause analysis of network performance problems
US20070050547A1 (en) * 2005-08-25 2007-03-01 Hitachi, Ltd. Storage system and storage system management method
US20080250178A1 (en) * 2005-09-08 2008-10-09 International Business Machines Corporation Load Distribution in Storage Area Networks
US20070088702A1 (en) * 2005-10-03 2007-04-19 Fridella Stephen A Intelligent network client for multi-protocol namespace redirection
US20080147878A1 (en) * 2006-12-15 2008-06-19 Rajiv Kottomtharayil System and methods for granular resource management in a storage network

Cited By (47)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9164692B2 (en) 2004-04-30 2015-10-20 Commvault Systems, Inc. System and method for allocation of organizational resources
US11287974B2 (en) 2004-04-30 2022-03-29 Commvault Systems, Inc. Systems and methods for storage modeling and costing
US8706993B2 (en) 2004-04-30 2014-04-22 Commvault Systems, Inc. Systems and methods for storage modeling and costing
US8725980B2 (en) 2004-04-30 2014-05-13 Commvault Systems, Inc. System and method for allocation of organizational resources
US10901615B2 (en) 2004-04-30 2021-01-26 Commvault Systems, Inc. Systems and methods for storage modeling and costing
US10282113B2 (en) 2004-04-30 2019-05-07 Commvault Systems, Inc. Systems and methods for providing a unified view of primary and secondary storage resources
US9405471B2 (en) 2004-04-30 2016-08-02 Commvault Systems, Inc. Systems and methods for storage modeling and costing
US9111220B2 (en) 2004-04-30 2015-08-18 Commvault Systems, Inc. Systems and methods for storage modeling and costing
US9152685B2 (en) 2005-12-19 2015-10-06 Commvault Systems, Inc. Systems and methods for migrating components in a hierarchical storage network
US10133507B2 (en) 2005-12-19 2018-11-20 Commvault Systems, Inc Systems and methods for migrating components in a hierarchical storage network
US8661216B2 (en) 2005-12-19 2014-02-25 Commvault Systems, Inc. Systems and methods for migrating components in a hierarchical storage network
US20070198797A1 (en) * 2005-12-19 2007-08-23 Srinivas Kavuri Systems and methods for migrating components in a hierarchical storage network
US11132139B2 (en) 2005-12-19 2021-09-28 Commvault Systems, Inc. Systems and methods for migrating components in a hierarchical storage network
US9916111B2 (en) 2005-12-19 2018-03-13 Commvault Systems, Inc. Systems and methods for migrating components in a hierarchical storage network
US9448892B2 (en) 2005-12-19 2016-09-20 Commvault Systems, Inc. Systems and methods for migrating components in a hierarchical storage network
US9361177B2 (en) 2010-04-08 2016-06-07 Hitachi, Ltd. Methods and apparatus for managing error codes for storage systems coupled with external storage systems
US8738963B2 (en) * 2010-04-08 2014-05-27 Hitachi, Ltd. Methods and apparatus for managing error codes for storage systems coupled with external storage systems
EP2663891A4 (en) * 2011-01-10 2017-07-19 Storone Ltd. Large scale storage system
US9729666B2 (en) 2011-01-10 2017-08-08 Storone Ltd. Large scale storage system and method of operating thereof
US11030669B1 (en) 2012-05-23 2021-06-08 Amazon Technologies, Inc. Best practice analysis, optimized resource use
US8769059B1 (en) 2012-05-23 2014-07-01 Amazon Technologies, Inc. Best practice analysis, third-party plug-ins
US9455871B1 (en) 2012-05-23 2016-09-27 Amazon Technologies, Inc. Best practice analysis, migration advisor
US9219648B1 (en) 2012-05-23 2015-12-22 Amazon Technologies, Inc. Best practice analysis, automatic remediation
US9197502B1 (en) 2012-05-23 2015-11-24 Amazon Technologies, Inc. Best practice analysis, migration advisor
US9626710B1 (en) 2012-05-23 2017-04-18 Amazon Technologies, Inc. Best practice analysis, optimized resource use
US8954574B1 (en) * 2012-05-23 2015-02-10 Amazon Technologies, Inc. Best practice analysis, migration advisor
US10740765B1 (en) 2012-05-23 2020-08-11 Amazon Technologies, Inc. Best practice analysis as a service
US9116861B2 (en) 2012-12-14 2015-08-25 Lenovo Enterprise Solutions (Singapore) Pte. Ltd. Cascading failover of blade servers in a data center
US9116860B2 (en) 2012-12-14 2015-08-25 Lenovo Enterprise Solutions (Singapore) Pte. Ltd. Cascading failover of blade servers in a data center
US9122652B2 (en) 2012-12-17 2015-09-01 Lenovo Enterprise Solutions (Singapore) Pte. Ltd. Cascading failover of blade servers in a data center
US10379988B2 (en) 2012-12-21 2019-08-13 Commvault Systems, Inc. Systems and methods for performance monitoring
US10042574B2 (en) * 2013-07-16 2018-08-07 International Business Machines Corporation Managing a storage system
US20170160974A1 (en) * 2013-07-16 2017-06-08 International Business Machines Corporation Managing a storage system
US10216458B2 (en) 2014-12-19 2019-02-26 International Business Machines Corporation Modeling the effects of switching data storage resources through data storage pool tier performance capacity and demand gap analysis
GB2533405A (en) * 2014-12-19 2016-06-22 Ibm Data storage resource assignment
US9880788B2 (en) 2014-12-19 2018-01-30 International Business Machines Corporation Modeling the effects of switching data storage resources through data storage pool tier performance capacity and demand gap analysis
US10275320B2 (en) 2015-06-26 2019-04-30 Commvault Systems, Inc. Incrementally accumulating in-process performance data and hierarchical reporting thereof for a data stream in a secondary copy operation
US11301333B2 (en) 2015-06-26 2022-04-12 Commvault Systems, Inc. Incrementally accumulating in-process performance data and hierarchical reporting thereof for a data stream in a secondary copy operation
US10248494B2 (en) 2015-10-29 2019-04-02 Commvault Systems, Inc. Monitoring, diagnosing, and repairing a management database in a data storage management system
US10176036B2 (en) 2015-10-29 2019-01-08 Commvault Systems, Inc. Monitoring, diagnosing, and repairing a management database in a data storage management system
US11474896B2 (en) 2015-10-29 2022-10-18 Commvault Systems, Inc. Monitoring, diagnosing, and repairing a management database in a data storage management system
US10853162B2 (en) 2015-10-29 2020-12-01 Commvault Systems, Inc. Monitoring, diagnosing, and repairing a management database in a data storage management system
US10146450B1 (en) * 2015-12-28 2018-12-04 EMC IP Holding Company LLC Managing a pool of storage slices via consumption estimation based on historical data
US11200110B2 (en) 2018-01-11 2021-12-14 Commvault Systems, Inc. Remedial action based on maintaining process awareness in data storage management
US10831591B2 (en) 2018-01-11 2020-11-10 Commvault Systems, Inc. Remedial action based on maintaining process awareness in data storage management
US11815993B2 (en) 2018-01-11 2023-11-14 Commvault Systems, Inc. Remedial action based on maintaining process awareness in data storage management
US11449253B2 (en) 2018-12-14 2022-09-20 Commvault Systems, Inc. Disk usage growth prediction system

Also Published As

Publication number Publication date
US20140164327A1 (en) 2014-06-12
US9002799B2 (en) 2015-04-07
US20100153338A1 (en) 2010-06-17
US8661216B2 (en) 2014-02-25
US20070198602A1 (en) 2007-08-23
US20070260834A1 (en) 2007-11-08
US8655850B2 (en) 2014-02-18
US20070198797A1 (en) 2007-08-23

Similar Documents

Publication Publication Date Title
US11132139B2 (en) Systems and methods for migrating components in a hierarchical storage network
US8661216B2 (en) Systems and methods for migrating components in a hierarchical storage network
US20200267219A1 (en) Systems and methods for granular resource management in a storage network
US11287974B2 (en) Systems and methods for storage modeling and costing
US8296475B2 (en) Systems and methods for performing multi-path storage operations
US20080147878A1 (en) System and methods for granular resource management in a storage network

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION

AS Assignment

Owner name: COMMVAULT SYSTEMS, INC., NEW JERSEY

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KAVURI, SRINIVAS;MULLER, MARCUS;REEL/FRAME:032483/0934

Effective date: 20070416