System and method for allocation of organizational resources

System and methods for storing electronic data is provided, where the system comprises a storage manager component and a management module associated with the storage manager component. The management module is configured to receive information related to storage activities associated with one or more storage operation components within the storage operation system under the direction of the storage manager component. The management module is adapted to predict storage operation resource allocations based on the received information related to the storage activities.

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. 60/752,196, titled System and Method for Migrating Components in a Hierarchical Storage Network, filed Dec. 19, 2005.

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 managing the allocation of resources in a storage operation system.

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 generally 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 if necessary. Such primary copy data is typically intended for short term retention (e.g., several 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 occurred with the data stored in primary storage.

Secondary copies include point-in-time data and are typically 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 backed up, 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.

Based on the many storage operations that may be performed on primary, secondary, or other types of storage data, information associated with these storage operations may exists. For example, administrative users or managers of a storage operation system may wish to leverage such storage operation information to a better understanding of system operation.

SUMMARY OF THE INVENTION

System and methods for storing electronic data are provided, wherein, in one embodiment, the system comprises a storage manager component and a management module associated with the storage manager component. The management module is configured to receive information related to storage activities associated with one or more storage operation components within the storage operation system under the direction of the storage manager component. The management module is adapted to predict storage operation resource allocations based on the received information related to the storage activities.

DETAILED DESCRIPTION

FIG. 1presents a block diagram of a storage operation cell in a system to perform storage operations on electronic data in a computer network according to an embodiment of the invention. As shown, the storage operation cell includes a storage management component, such as storage manager100and one or more of the following: a client85, a data store90, a data agent95, a media management component, such as a media agent125, a media management component index cache130, a storage device135, a storage management component index cache105, a jobs agent110, an interface module115, and a management agent120. The system and elements thereof are exemplary of a modular storage management system such as that further described in application Ser. No. 09/610,738, which is incorporated herein by reference in its entirety. A storage operation cell may generally include combinations of hardware and software components directed to performing storage operations on electronic data. Exemplary storage operation cells according to embodiments of the invention include CommCells as embodied in the QNet storage management system and the QiNetix storage management system by CommVault Systems of Oceanport, N.J., and as further described in application Ser. No. 60/482,305 and application Ser. No. 09/354,058 which are hereby incorporated by reference in their entirety.

Storage operations cells may be related to backup cells and may provide all of the functionality of backup cells as further described in application Ser. No. 09/354,058. Storage operation cells may also perform additional types of storage operations and provided by other types of storage management functionality. Storage operation cells performing storage operations may also include, but are not limited to, creation, storage, retrieval, migration, deletion, and tracking of primary or production volume data, secondary volume data, primary copies, secondary copies, auxiliary copies, snapshot copies, backup copies, incremental copies, differential copies, Hierarchical Storage Management (“HSM”) copies, archive copies, Information Lifecycle Management (“ILM”) copies, and other types of copies and versions of electronic data. Storage operation cells may also include an integrated management console for providing users or system processes to interface with, in order to perform storage operations on electronic data.

A storage operation cell may be organized and associated with other storage operation cells by forming a logical hierarchy among various components of a storage management system. Storage operation cells generally include a storage manager100, and, one or more other components including, but not limited to, a client computer85, a data agent95, a media management component125, a storage device135, such as a single instance storage device, and other components.

For example, a storage operation cell may contain a data agent95which may generally be a software module that is responsible for performing storage operations related to client computer85data that may be stored in data store90or another memory location. For example, data agent95may provide archiving, migrating, and recovery of client computer data. A data agent may perform storage operations in accordance with one or more storage policies or other preferences. A storage policy is generally a data structure or other information which 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. Storage policies may be stored to a storage manager index105, to archive media as metadata for use in restore operations or other storage operations, or to other locations or components of the system.

Each client computer85generally has at least one data agent95and the system may support many client computers85. The system may also generally provide a plurality of data agents95each of which may intend to perform storage operations related to data associated with a different application, for example, in order to backup, migrate, and recover application specific data. For example, different individual data agents95may 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.

If a client computer85includes two or more types of data, one data agent95may generally be required for each data type in order to perform storage operations related to client computer85data. For example, to backup, migrate, and restore all of the data on a MICROSOFT EXCHANGE 2000 server, the client computer85would use one MICROSOFT EXCHANGE 2000 mailbox data agent95to backup the EXCHANGE 2000 mailboxes, one MICROSOFT EXCHANGE 2000 database data agent95to backup the Exchange 2000 databases, one MICROSOFT EXCHANGE 2000 public folder data agent95to backup the EXCHANGE 2000 public folders, and one MICROSOFT WINDOWS 2000 file system data agent95to backup the client computer's85file system. These data agents95may be treated as four separate data agents95by the system even though they reside on the same client computer85. Separate data agents may be combined to form a virtual data agent (not shown) for performing storage operations related to a specific application. Thus, the four separate data agents of the previous example may be combined as a virtual data agent suitable for performing storage operations related to all types of MICROSOFT EXCHANGE 2000 and/or WINDOWS 2000 data.

The storage manager100may generally be a software module or application that coordinates and controls storage operations performed by the storage operation cell. The storage manager100may communicate with all elements of the storage operation cell including client computers85, data agents95, media management components125, and storage devices135regarding storage operations, for example, to initiate and manage system backups, migrations, and recoveries. The storage manager100may also communicate with other storage operation cells.

The storage manager100may include a jobs agent110software module which monitors the status of all storage operations that have been performed, that are being performed, or that are scheduled to be performed by the storage operation cell. The jobs agent110may be communicatively coupled with an interface agent115software module. The interface agent115may provide presentation logic, such as a graphical user interface (“GUI”), an application program interface (“API), or other interface by which users and system processes may be able to retrieve information about the status of storage operations and issue instructions regarding the performance of storage operations. For example, a user may modify the schedule of a number of pending snapshot copies or other types of copies. As another example, a user may use the GUI to view the status of all storage operations currently pending in all storage operation cells or the status of particular components in a storage operation cell.

Storage system management information may include, but is not limited to, the status of various storage operations (past and present), storage operation policies, storage operation scheduling, the configuration (e.g., associations) of components (e.g., media agents125, storage devices135, clients85, data agent95, etc.) within the storage operation system, the number of storage operation jobs carried out by each of the storage operation system components, failure and load balancing information, network capacity information across various communication links (e.g., links117,119), and other data management related information. Such information may be stored in index105, and associated metabase, and/or any other storage devices associated with storage manager100.

A management interface module122within jobs agent component110may facilitate the accessing and processing of system information. In addition to allowing users of the storage operation system (e.g., system administrators) to monitor, control, and retrieve such information, management interface module122may generate reports indicative of system operation which may include past, present or predictive information relating to system performance. One or more users of a storage operation system may access a unified view of system management information from management module122via interface module115. Based on this accessed information, various trending procedures and process may be carried in order predict the growth requirements of the one or more storage operation cells in a storage operation system. As previously described, interface115may include a GUI, API, or other graphical interface device capable of displaying, entering, and/or editing system management information to users such as storage system administrators.

As illustrated inFIG. 1, management interface module122may be a module residing within jobs agent110. Alternatively, management interface module122may be a separate module within storage manager100. Also, management interface module122may include a separate module in communication with storage manager100via management agent120. For example, management interface module122may receive storage management related information from different modules with the storage operation cell, such as, data agents95, media agents125, storage devices135, network traffic evaluation devices, and/or any other hardware devices, software modules, or combinations thereof, that may have or generate performance related data or metrics based on storage operation activities (e.g., copy operations, data migration, backups, etc.) with the storage operation cells of a storage operation system.

The storage manager100may also include a management agent120software module. The management agent120may generally provide an interface with other management components100in other storage operations cells through which information and instructions regarding storage operations may be conveyed. For example, a management agent120in a first storage operation cell can communicate with a management agent120in a second storage operation cell regarding the status of storage operations in the second storage operation cell. A management agent120in a first storage operation cell can communicate with a management agent120in a second storage operation cell to control the storage manager100(and other components) of the second storage operation cell via management agent120contained in the storage manager100of the second storage operation cell. The management agent120in the first storage operation cell may communicate directly with and control the components in the second storage management cell and bypasses the storage manager100in the second storage management cell. Storage operation cells can thus be organized hierarchically among cells.

A media management component125may be a software module that conducts data, as directed by a storage manager100, between client computers85and one or more storage devices135. The media management component125may communicatively be coupled with and generally configured to control one or more storage devices135. For example, the media management component125may instruct a storage device135to use a robotic arm or other means to load or eject a media cartridge, and to archive, migrate, or restore application specific data. The media management component125may generally communicate with storage devices135via a local bus such as a SCSI adaptor. In some embodiments, the storage device135may be communicatively coupled to the media management component125via a Storage Area Network (“SAN”).

Each media management component125may maintain an index cache130which stores index data the system generates during storage operations as further described herein. For example, storage operations for MICROSOFT EXCHANGE data generate index data. Index data may include, for example, information regarding the location of the stored data on a particular media, information regarding the content of the data stored such as file names, sizes, creation dates, formats, application types, and other file-related criteria, information regarding one or more clients associated with the data stored, information regarding one or more storage policies, storage criteria, or storage preferences associated with the data stored, compression information, retention-related information, encryption-related information, stream-related information, and other types of information. Index data may thus provides the system with an efficient mechanism for performing storage operations including locating user files for recovery operations and for managing and tracking stored data. The system generally maintains two copies of the index data regarding particular stored data. A first copy may generally be stored with the data copied to a storage device135. Thus, a tape may contain the stored data as well as index information related to the stored data. In the event of a system restore, the index data stored with the stored data may be used to rebuild a media management component index130or other index useful in performing storage operations. In addition, the media management component125that controls the storage operation may also write an additional copy of the index data to its index cache130. The data in the media management component index cache130may be generally stored on faster media, such as magnetic media, and is thus readily available to the system for use in storage operations and other activities without having to be first retrieved from the storage device135.

Storage manager100may also maintains an index cache105. Storage manager index data may be used to indicate, track, and associate logical relationships and associations between components of the system, user preferences, management tasks, and other useful data. For example, the storage manager100may use its index cache105to track logical associations between media management components125and storage devices135. The storage manager100may also use its index cache105to track the status of storage operations to be performed, storage patterns associated with the system components such as media use, storage growth, network bandwidth, Service Level Agreement (“SLA”) compliance levels, data protection levels, storage policy information, storage criteria associated with user preferences, retention criteria, storage operation preferences, and other storage-related information. Index caches105and130may typically reside on their corresponding storage component's hard disk or other fixed storage device.

For example, the jobs agent110of a storage manager component100may retrieve storage manager index105data regarding a storage policy and storage operation to be performed or scheduled for a particular client85. Jobs agent110, either directly or via the interface module115, may communicate with the data agent95at the client85regarding the storage operation. In some embodiments, the jobs agent110may also retrieve from the index cache105a storage policy associated with the client85and uses information from the storage policy to communicate to the data agent95one or more media management components125associated with performing storage operations for that particular client85as well as other information regarding the storage operation to be performed, such as retention criteria, encryption criteria, streaming criteria, etc. The data agent95may then package or otherwise manipulate the client data stored in the client data store90in accordance with the storage policy information and/or according to a user preference, and communicates this client data to the appropriate media management component(s)125for processing. Media management component(s)125may store the data according to storage preferences associated with the storage policy including storing the generated index data with the stored data, as well as storing a copy of the generated index data in the media management component index cache130.

In some embodiments, components of the system may reside and execute on the same computer. In some embodiments, a client computer85component such as a data agent95, a media management component125, or a storage manager100may coordinate and direct storage operations as further described in application Ser. No. 09/610,738. This client computer85component can function independently or together with other similar client computer85components.

FIG. 2presents a block diagram of a hierarchically organized group of storage operation cells in a system to perform storage operations on electronic data in a computer network according to an embodiment of the invention. As shown, the system may include a master storage manager component140, a first storage operation cell145, a second storage operation cell150, a third storage operation cell155, a fourth storage operation cell160, a fifth storage operation cell165, and an nth storage operation cell170.

As previously described, storage operation cells may often be communicatively coupled and hierarchically organized. For example, as shown inFIG. 2, master storage manager140may be associated with, communicates with, and directs storage operations for a first storage operation cell145, a second storage operation cell150, a third storage operation cell155, a fourth storage operation cell160, a fifth storage operation cell165, and an nth storage operation cell170. In some embodiments, master storage manager140may not be part of any particular storage operation cell. In other embodiments (not shown), master storage manager140may itself be part of a storage operation cell.

Thus, master storage manager140may communicate with the management agent of the storage manager of the first storage operation cell145(or directly with the other components of the first cell145) regarding storage operations performed in the first storage operation cell145. For example, in some embodiments, the master storage manager140may instruct the first storage operation cell145how and when to perform storage operations, including the type of operation to perform, and the data on which to perform the operation.

In other embodiments, master storage manager140may track the status of its associated storage operation cells, such as the status of jobs, system components, system resources, and other items, by communicating with manager agents (or other components) in the respective storage operation cells. In other embodiments, master storage manager140may track the status of its associated storage operation cells by receiving periodic status updates from the manager agents (or other components) in the respective cells regarding jobs, system components, system resources, and other items. For example, in some embodiments, master storage manager140may use methods to monitor network resources such as mapping network pathways and topologies to, among other things, physically monitor storage operations and suggest alternate routes for storing data as further described herein. The master storage manager140may also use methods to monitor primary and secondary storage trends, storage status, media usage, data protection levels, and other storage-related information as further described herein.

In some embodiments, master storage manager140may store status information and other information regarding its associated storage operation cells and the system in an index cache or other data structure accessible to the master storage manager140. In some embodiments, as further described herein, the presentation interface of the master storage manager140accesses this information to present users and system processes with information regarding the status of storage operations, storage operation cells, system components, and other information of the system.

Storage operation cells may thus be organized hierarchically. Thus, storage operation cells may inherit properties from their parents or be controlled by other storage operation cells in the hierarchy. Thus, in some embodiments as shown inFIG. 2, the second storage operation cell150controls or is otherwise superior to the third storage operation cell155, the fourth storage operation cell160, the fifth storage operation cell165, and the nth storage operation cell170. Similarly, the fourth storage operation cell160controls the fifth storage operation cell165, and the nth storage operation cell170.

Storage operation cells may also be organized hierarchically according to criteria such as function, geography, architectural considerations, or other factors useful in performing storage operations. For example, in one embodiment storage operation cells may be organized according to types of storage operations: the first storage operation cell145may be directed to performing snapshot copies of primary copy data, and the second storage operation cell150is directed to performing backup copies of primary copy data or other data. For example, in another embodiment, the first storage operation cell145may represent a geographic segment of an enterprise, such as a Chicago office, and a second storage operation cell150represents a different geographic segment, such as a New York office. In this example, the second storage operation cell150, the third storage operation cell155, the fourth storage operation cell160, the fifth storage operation cell165, and the nth storage operation cell170may represent departments within the New York office. Alternatively, these storage operation cells may be further divided by function performing various types of copies for the New York office or load balancing storage operations for the New York office.

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. For example, a network administrator for an enterprise might have access to all storage operation cells including the master storage manager140. However, a network administrator for only the New York office, according to a previous example, may only satisfy access criteria for gaining access to the second storage operation cell150, the third storage operation cell155, the fourth storage operation cell160, the fifth storage operation cell165, and the nth storage operation cell170which may comprise the New York office storage management system.

In some embodiments, hierarchical organization of storage operation cells facilitates storage management planning and decision-making. For example, in some embodiments, a user of the master storage manager140may view the status of all jobs in the associated storage operation cells of the system as well as the status of each component in every storage operation cell of the system. The user can may then plan and make decisions based on this global data. For example, the user may view high-level reports of summary information regarding storage operations for the entire system, such as job completion status, component availability status, resource usage status (such as network pathways, etc.), and other information. The user 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 manager140may alert the user when a particular resource is unavailable or congested. A storage device may be at or near capacity or require additional storage media. Alternatively, a storage manager in a particular storage operation cell may be unavailable due to hardware failure, software problems, or other reasons. In some embodiments, master storage manager140(or another storage manager within the hierarchy of storage operation cells) may utilize the global data regarding its associated storage operation cells at its disposal to suggest solutions to such problems prior to occurrence. For example, the master storage manager140may alert the user that a storage device in a particular storage operation cell was full or otherwise congested, and then suggest, based on job and data storage information contained in its index cache, an alternate storage device.

Master storage manager140(or other network storage manager) may contain programming directed to analyzing the storage patterns and resources of its associated storage operation cells and which suggests optimal or alternate methods of performing storage operations. Thus, for example, master storage manager140may analyze traffic patterns in order to determine that snapshot data should be sent via a different network segment or to a different storage operation cell or storage device. In some embodiments, users may direct specific queries to master storage manager140regarding predicting storage operations or regarding storage operation information.

FIG. 3is a block diagram of a hierarchically organized group of storage operation cells in a system to perform storage operations on electronic data in a computer network according to an embodiment of the invention. As shown,FIG. 3may include a first storage operation cell175, a second storage operation cell180, a third storage operation cell185, a client190in communication with a primary volume195storing production or other “live” data, a storage manager component200in communication with a storage manager index data store205, a media management component210in communication with a media management component index215, a secondary storage device or volume220, and a master storage manager component225in communication with a master storage manager index data store230.

According to an embodiment of the invention, the first storage operation cell175may be directed to a particular type storage operation, such as SRM storage operations. For example, the first storage operation cell175may monitor and perform SRM-related calculations and operations associated with primary volume195data. Thus, the first storage operation cell175may include a client component190in communication with a primary volume195storing data. For example, client190may 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 volume195. Storage manager component200in cell175may contain SRM modules or other logic directed to monitoring or otherwise interacting with attributes, characteristics, metrics, and other information associated with the data stored in primary volume195. Storage manager200may track and store this information and other information in storage manager index205. For example, in some embodiments, storage manager component200may track the amount of available space and other similar characteristics of data associated with primary volume195. In some embodiments, as further described herein, storage manager component200may also issue alerts or take other actions when the information associated with primary volume195satisfies certain criteria, such as alert criteria (e.g., breach of storage capacity threshold levels).

In addition to storing alert criteria and storage data characteristics, storage manager200in cell175may also track and save (e.g., within index205) other system management information. For example, information associated with various aspects of storage operation activities within cell175may be accessed by storage manager200and stored in index205.

For example, the information associated with storage activities may include, but is not limited to, a logged time stamp for each performed storage operation; storage capacity used during each storage operation; status of storage operation (e.g., partial or full failure); pathways taken over one or more communication links (e.g., link240) between client190and primary storage195during each storage operation; aggregate storage capacity available within storage device195, number of clients190within storage cell175; number of storage devices (e.g., storage195and index205) within storage operation cell175; and network congestion information associated with each pathway over which a storage operation is performed. Storage manager200may periodically send such stored system management information to a master storage manager such as storage manager225in storage operation cell175. Alternatively, master storage manager225may poll storage manager200of cell175and/or other storage manager components (e.g., storage manager200of storage operation cell180) in order to access system management information.

The storage manager200in storage operation cell175may include a management interface module such as management interface122shown inFIG. 1. If so, the management interface may access the system management information from index205for processing. Once processed, various forecasting information associated with the storage resources in storage cell175may be determined and sent to master storage manager225. For example, based on previous storage capacity trends and available storage capacity associated with storage device195, the management interface (not shown) may predict a need for added storage capacity within three weeks.

Thus, in the provided example, the predicted storage needs may provide a measure of growth rate associated with a storage resource such as primary storage195, which may provide system administrators and managers with an opportunity to allocate new and/or alternative resources prior to a point in time when the resource may no longer be available. In another example, information related to traffic on a data pathway may be monitored in order to develop a trend in failure conditions versus data traffic on a specific pathway at different times. Thus, based on this information, the management interface module may, for example, users with the opportunity to select additional or alternative data pathways at times when data transmissions over a particular pathway previously lead to a failure in storage operations. In some embodiments, the storage manager may automatically assign the appropriate resources according to the processing of the system management information by its respective management interface module (e.g., in the case were data loss or system failure is imminent or to part of an ongoing optimization process, etc).

The second storage operation cell180may be directed to another type storage operation, such as HSM storage operations. For example, second storage operation cell180may perform backups, migrations, snapshots, or other types of HSM-related operations known in the art. For example, in some embodiments, data may be migrated from faster and more expensive storage such as magnetic storage to less expensive storage such as tape storage.

In some embodiments, storage operation cells may also contain logical groupings of the same physical devices. Thus, the second storage operation cell180may include client component190in communication with primary volume195for storing data, and client component190and primary volume195in the second storage operation cell180may be the same physical devices as the client component190and primary volume195in the first storage operation cell175. Similarly, in some embodiments, storage manager component200and index205in the second storage operation cell180may be the same physical devices as the storage manager component and index in the first storage operation cell175. Storage manager component200may, however, also contain HSM modules or other logic associated with second storage operation cell180that may be directed to performing HSM storage operations on primary volume195data.

The second storage operation cell180, therefore, may also contain a media management component210, a media management component index215, and a secondary storage volume220directed to performing HSM-related operations on primary copy data. For example, storage manager200may migrate primary copy data from primary volume195to secondary volume220using media management component210. Storage manager200may also track and store information associated with primary copy migration and other similar HSM-related operations in storage manager index205. For example, in some embodiments, storage manager component200may direct HSM storage operations on primary copy data according to a storage policy associated with primary copy195and stored in index205. In some embodiments, storage manager200may also track where primary copy information is stored, for example, in secondary storage220.

Storage manager200in cell180may also track and save (e.g., within index205) system management information associated with various aspects of storage operation activities. For example, the information associated with storage activities may include, but is not limited to, a logged time stamp for each performed storage operations; storage capacity used during each storage operation; status of storage operations (e.g., partial or full failure); pathways taken over one or more communication links (e.g., link240) between client190, media agent210, and secondary storage220during each storage operation; pathways taken over one or more communication links (e.g., links245and250) between client190and primary storage195during each storage operation; aggregate storage capacity available within storage device195; number of clients190within storage cell180; number of storage devices (e.g., storage devices195,220, and205) within storage operation cell180; number of media agents210within storage cell180; and network congestion information associated with each pathway over which a storage operation is performed. Storage manager200may periodically send such stored system management information to a master storage manager such as storage manager225in storage operation cell180. Alternatively, master storage manager225may poll storage manager200of cell180and/or other storage manager components (e.g., storage manager200of storage operation cell175) in order to access such system management information.

The storage manager200in storage operation cell180may also include a management interface module such as management interface122shown inFIG. 1. The management interface that may include reporting and analysis software component that may search for and retrieve certain system management information from portions of the system including, for example, index205or an associated metabase (not shown) indicative of system performance. The reporting software may analyze this information to generate certain reports that may reveal trends in system operation such as the use of certain system resources over time, observed and projected system growth, resource utilization rate, failure and congestion rates, performance information for specific groups of resources, etc. This allows system users to identify, track and predict performance and operational trends within the system providing operational visibility, allowing users to manage system configuration and resources effectively.

For example, based on information regarding previous storage capacity usage and available storage capacity of one or more secondary storage devices220, the reporting and analysis software component may analyze and forecast a need for added storage capacity within a certain period of time (e.g., two months). Thus, the predicted storage needs may be indicative of growth rate associated with a particular storage resource such as storage device220, which may provide system administrators with an opportunity to allocate additional and/or alternative resources such as additional storage media prior to a point in time when the resource is no longer viable.

In another example, information associated with the number of storage operations performed and the number of active media agents210coordinating those storage operations in certain cells180may be retrieved and analyzed by the reporting software. The results of such an analysis may provide a system administrator with information regarding resource usage including emerging patterns and trends providing an opportunity to identify bottlenecks or stress points and configure, assign or allocate additional media agents to cope with changing conditions. For example, if certain media agents are operating at or near full capacity, additional ones may be added. In this example, if certain other media agents are operating significantly below full capacity, storage operations from over burdened media agents may moved to these media agents to load balance. In some embodiments, the system may automatically perform these tasks without user input (e.g., in an emergency situation when failure or data loss are imminent, or as part of an ongoing process to optimize system performance or enhance efficiency, etc.).

The third storage operation cell185may contain a master storage manager225and a master storage manager index230. In some embodiments (not shown), additional storage operation cells may be hierarchically located between the third storage operation cell185and the first storage operation cell175or the second storage operation cell180. In some embodiments, additional storage operation cells hierarchically superior to the third storage operation cell185may also be present in the hierarchy of storage operation cells.

In some embodiments, the third storage operation cell185may also be directed to performing a type of storage operation, such as integration of SRM and HSM data from other storage operation cells, such as first storage operation cell175and second storage operation cell180. In other embodiments, the third storage operation cell185may also perform other types of storage operations and may also be directed to HSM, SRM, or other types of storage operations. In some embodiments, the master storage manager225of the third storage operation cell185may aggregate and process network and storage-related data provided by other manager components200in other storage operation cells175and180in order to provide, among other information, reporting information regarding particular cells, groups of cell, or the system as a whole.

For example, master storage manager225in storage operation cell185may also include a management interface module such as management interface122shown inFIG. 1which may include a reporting and analysis component. This management interface (not shown) may access management information received from both storage manager200in cell175and storage manager200in storage cell180. Master storage manager225may, therefore, provide system administrators with a unified view of all storage operation cells within a configured storage operation system.

Although each storage operation cell may process system management information via a respective management interface module (e.g., generating performance metrics, trending, forecasting, and resource allocation), processing of system management information may be provided centrally at master storage manager225. In such embodiments, system management information may be sent by the storage manager of each storage operation cell (e.g., storage manager200of cell175) to master storage manager225following each storage operation. Alternatively, master storage manager225may periodically poll storage certain operation cells for system management information based on the report or analysis to be performed.

FIG. 3Bis a flow diagram400generally illustrating some steps involved in using storage operation information (e.g., system management information) to generate certain reports or metrics according to an embodiment of the invention. At step402, information associated with various storage operations within a storage operation cell may be tracked and stored by the storage manager, media agent or other media management component associated with one or more storage operation cells. For example, certain system management information such as information regarding the data or information copied (e.g., data size, type, packaging or other format details, security, location, destination, size, etc.), the time and date associated with past, present or future the storage operation, the policy responsible for initiating the storage operation, the pathway used/to be used complete the storage operation, the components involved/to be involved in the storage operation, and the status of the storage operation etc.

In some embodiments, this information may present in an index, database, metabase or other information storage device associated with one or more master storage managers or other media management components associated with one or more storage operation cells. Thus, in operation, a computing device (not shown) performing the calculations associated with a report may request and collect information from various master storage managers regarding certain information relating to metrics to be calculated (described further herein) (step404). Once collected, this information may be processed to generate a specified report or obtain the desired performance metric(s). This may include providing forecasting and trending analyses as further described herein that may be used for identifying stress points within the system which may be used to assist in resource allocation (dynamic, automatic or manual) in one or more other storage operation cells (e.g., cells175and180) associated with the master storage operation cell (step408).

In other embodiments, information regarding system performance may be collected from various media management components within storage operation cells and reported to an associated master storage manager which may fulfill request as described above or be reported directly to the computing device requesting such information. In such embodiments, the computing device may consult with a master storage manager to locate media management components that have information of interest. The computing device may thus consult multiple storage operation cells in search of relevant information, collate and/or arrange the relevant information for subsequent processing to generate requested reports or metrics.

At step404, it may be determined whether certain information is stored in or available in one or more master storage managers (e.g., master storage manager225shown inFIG. 3A). If so, the information may be retrieved and processed accordingly. This may involve initially polling or otherwise communicating with master storage managers within the system (or specified subset with in the system) to identify storage operation cells with information relevant to calculating desired metrics. A list of such cells may be created and used as a starting point in collecting relevant metric information. If however, it is determined that the information is not present in one or more master storage manager(s), the information may be retrieved from one or more media management components in a similar manner (step406). A computing device including metric calculation-software and an optional user interface may generate reports and provide forecasting and resource allocation operation based on the accessed information received from these storage manager components (step408). Such reports may be presented to a user for consideration or may be analyzed by system management software monitoring system performance.

FIG. 4Ashows an illustrative interface screen412that may be generated by reporting and analysis software for performing certain calculations based on system performance information according to an embodiment of the invention. For example, screen412may be generated by management interface module122(FIG. 1), and presented to users via interface module115(FIG. 1). As shown, the left side of screen412may include a directory tree414or other menu structure that allows users to access and manage different parts of a storage operation system from a unified display. For example, directory tree414may include a “reports” field416, which may, among other things, provide users with the ability to request and monitor report results associated with various aspects of the storage operation system.

Selecting a report from field416may cause the system to generate provide a user display420allowing a user to specify parameters and generate certain reports regarding a particular category or occurrence of interest. Such reports may be preprogrammed by a vendor and/or created by an end user through reports generation tool (not shown) using techniques and procedures known in the art.

As shown, such reports may include, but are not limited to Billing, Data Protection, Data Recovery, Primary Storage or Commcell Growth and may include multiple subcategories as shown in connection with Data Protection reports on the left hand side of screen412. However, it will be understood that these reports are only illustrative and that any other reports relating to system operation or performance may be added if desired. By selecting, for example, “CommCell Growth” element418from reports field416, display420may be presented to the user. In some embodiments, users may enter certain specifics as filter parameters that provide or generate criteria that specifying data or occurrences of interest. For example, display420may include menu option422for selecting components or modules of the storage operation system that may be used in generating certain reports associated with the selected components or modules. For example, as illustrated in the embodiment ofFIG. 4A, subclient(s)424has been selected.

Display420may include various time range selection options426. For example, a user may select a report that provides information based on a certain frequency (e.g., a weekly basis) and/or over a specified time range (e.g., over last 8 weeks). Thus, frequency option428and range option430may specify a report generated based on subclient related information collected on a weekly basis (i.e., based on option428) over a specified eight-week period (i.e., based on option430). In other embodiments, a range of dates may be specified if desired.

Using an output or result field431, a user may specify that a certain format for displaying results that may include various graphical displays for displaying report results. In the provided example, a bar graph display is selected, however any suitable layout may selected of desired (e.g., pie chart, a line plot across and x-y axis, etc.). A report may be generated for subclients of a particular storage operation cell or other selected storage operation cells using selection field432. Thus, as shown in exemplary screen412, specific storage operation cells436and438may be selected and included in a subsequently generated report. After specifying the information certain information, By clicking on “Generate” button440in screen412, a Commcell growth report may be generated, as by clicking on “Generate” button440in screen412(shown inFIG. 4B).

FIG. 4Bshows an illustrative report screen445for provides results based on the information specified inFIG. 4Aaccording to an embodiment of the invention. The display option for the report may be changed using chart option menu447. For example, the current report display for subclient components associated with the storage operation cell “Hummer” (i.e., as indicated by information bar452within screen445) is displayed by bar graph450. Bar graph450may display the number of subclients in use during storage operations, as indicated at455, as a function of a selected time range, indicated at457. Bar460may indicate that during the week of Monday, September 12 (i.e., #09/12#), twenty-eight subclients were involved in storage operations. Similarly, bar462may indicate that during the week of Monday, September 19 (i.e., #09/19#), twenty-four subclients were involved in storage operations, which indicates a reduction compared to the previous week. Graph450also illustrates that over an eight-week period (i.e., from Mon. 08/01-Mon. 09/19), six weeks show no subclient activity, as indicated at465.

In addition to graph450, table470may also illustrate the results associated with subclient activities in storage operation cell Hummer. The generated results may provide user and administrators with an indication as to how a particular component or module has been utilized. This may include the amount of data traffic, data copied or moved to and from various locations, resources used such as certain media management components or storage device capacity, system bandwidth etc.

Based on this information, operational trends may be determined, which may provide the ability to forecasting future resource needs. For example, the results shown in graph450or table470may indicate that there is no increase associated with the number of active subclients within the storage operation cell (e.g., based on entries460and462). Thus, no additional resources may need to be allocated based on the observed information, which, in some instances, may indicate the storage operation cell may additional resources to spare. However, if the results had shown an increase in the number of subclients used in the storage operation cell, this increased trend over the eight-week time period allows the system or a user to recognize and plan for any resource shortage or bottleneck including adding or assigning alternative resources to the storage operation cell such as media agents, data paths, storage devices such as tape drives and associated storage media (e.g., tapes, discs, etc.).

In determining a trend or trends in the growth results, various algorithms, formula, and/or data manipulation techniques such as linear regression, extrapolation, interpolation, best fit curves, likelihood functions or other techniques known in the art may be employed based on the data points available and the desired metrics to be calculated.

FIG. 5Ashows another illustrative display512generated by a reporting module according to an embodiment of the invention. Similar to the interface screen ofFIG. 4A, screen512may also include directory tree514, which may allow users to access and manage different parts of a storage operation system from a unified display. For example, directory tree514may also include a “reports” field516. As shown, screen512may include menu option522for selecting components or modules of the storage operation system that may be used in generating growth reports associated with the selected components or modules. In the illustrated embodiment, Media Agent(s) option524has been selected.

Scheduling options526may include various time range selection options. For example, a user may select a growth report that provides information based on frequency (e.g., a weekly basis) and over a specified time range (e.g., over last 8 weeks). Thus, frequency option528and data range option530may provide a report that may be generated based on data agent related information that is collected once a week (i.e., based on option528) over an eight-week period (i.e., based on option530). Scheduling option531may include a display chart option for displaying the report results. In the provided example, a bar graph display may be selected. A report may be generated for data agent of a particular one or more selected storage operation cells using selection field532. Thus, based on exemplary screen512, storage operation cells536and538may be selected for growth report generation purposes. By clicking on “Generate” button540in screen512, a corresponding report may be generated, as illustrated inFIG. 5B.

FIG. 5Bshows an illustrative interface screen545for providing reported results based on the entered scheduling information shown inFIG. 5Aaccording to an embodiment of the invention. The display option for the growth report may be changed using chart option menu547. For example, the current growth report display for data agent components associated with the storage operation cell Hummer” (i.e., as indicated by information bar552within screen545) is displayed by bar graph550. Bar graph550may display the number of data agents in use during storage operations, indicated at555, as a function of a selected time range, indicated at557. Bar560may indicate that during the week of Monday, September 12 (i.e., #09/12#), eight data agents were involved in storage operations. Similarly, bar562may indicate that during the week of Monday, September 19 (i.e., #09/19#), eight subclients were also involved in storage operations, which indicates no change in the number of data agents compared to the previous week. Graph550also illustrates that over an eight-week period (i.e., from Mon. 08/01-Mon. 09/19), six weeks show no data agent activity, as indicated at565.

In addition to graph550, table570also illustrates the results associated with the number of active data agents in storage operation cell Hummer in table form. The generated results may provide users and administrators with an indication as to how a particular component or module has been utilized. As previously described, based on this information trends may be determined, which provides the ability to forecast future resource needs. For example, the results shown in graph550or table570may indicate that there is no increase associated with the number of active data agents used within the storage operation cell. However, if the results indicate an increase in the number of data agents used in the storage operation cell, this increased trend over the eight-week time period may have provided an opportunity for evaluating and adding more data agent resources to the storage operation cell. The number of data agent resources forecasted for addition to a storage operation cell may be based on other calculated metrics associated with the storage operation components such as, for example, the utilized bandwidth of data pathways during storage operations, status of storage operations, data load, available storage devices etc. As mentioned above, various other algorithms, formulae, and/or data manipulation techniques may be incorporated based on the metrics used to evaluate resources within the one or more storage operation cells within a storage operation system.

FIG. 6Ais yet another illustrative screen612generated by a management interface module for entering scheduling information for trending and resource forecasting according to an embodiment of the invention. For example, screen612may also be generated by a reports interface module122(FIG. 1), and accessed and displayed to users via interface module115(FIG. 1). The left side of screen612may include a directory tree614that allows users to access and manage different parts of a storage operation system from a unified display. For example, directory tree614may include a “reports” field616, which may, among other things, provide system administrators or authorized uses with the ability to monitor and manage reports associated with various aspects of the storage operation system. By selecting, for example, “CommCell Growth” element418from “reports” field616, an illustrative display620may be presented to an administrative user. Display620may include menu option622for selecting components or modules of the storage operation system that may be used in generating growth reports associated with the selected components or modules. For example, in the illustrated embodiment ofFIG. 6A, Data Protection Job(s)624has been selected.

Scheduling options626may include various time range selection options. For example, a user may select a growth report that provides information based on frequency (e.g., a daily basis) and over a specified time range (e.g., over last 7 days). Thus, frequency option628and range option630may provide a growth report that may be generated based on the number of data protection jobs carried out daily (i.e., based on option628), and over a seven day period (i.e., based on option630).

Scheduling option631may include a display chart option for displaying the growth report results. In the provided example, a bar graph display is selected. A growth report may be generated for performed data protection jobs of a particular one or more selected storage operation cells, whereby the storage operation cells are selected using selection field632. Thus, based on exemplary screen612, storage operation cells636and638may be selected for growth report generation purposes. By clicking on “Generate” button640in screen612, a corresponding growth report may be generated, as illustrated inFIG. 6B.

FIG. 6Bshows an illustrative interface screen645for providing reported results based on the entered scheduling information shown inFIG. 6Aaccording to an embodiment of the invention. The display option for the growth report may be changed using chart option menu647. For example, the current report display for data protection jobs associated with the storage operation cell Hummer (i.e., as indicated by information bar652within screen645) is displayed by bar graph650. Bar graph650may display the number of data protection jobs, indicated at655, as a function of a selected time range, as indicated at657. Bar660may indicate that during the weekend of September 16-18 (i.e., #09/16-09/18#), forty data protection jobs were performed. Similarly, bar662may indicate that on the following Monday, September 19 (i.e., #09/19#), eighteen data protection jobs were performed, indicating a reduction in data protection jobs compared to the weekend. Graph650also illustrates that over the period of about a week (i.e., from Tues. 09/13-Mon. 09/19), for three days, no data protection jobs are performed, as indicated at665.

In addition to graph650, table670may also illustrate the growth results associated with the listed data protection jobs in storage operation cell Hummer. The generated results may provide users and administrators with information regarding various data protection activities that may have been performed. Based on this information, trends may be determined, which may provide opportunities for forecasting future resource needs. For example, the results shown in graph650or table670may indicate that there may be a trend associated with the increased number of data protection jobs occurring over weekends. Using this information, additional storage system resources may be assigned to handle the increased data load associated with performing the increased number of data protection jobs during busy periods such the weekends. For example, additional storage devices and/or media agents may be utilized during these periods.

In determining a trend or trends in the growth results, various algorithms, formula, and/or data manipulation techniques may be incorporated based on the metrics used to evaluate resources within the one or more storage operation cells within a storage operation system. Moreover, system parameters may change or vary according to needs of the end-user of the storage operation system. For example, if the end-user is in the financial business, the metrics used for determining when and how often to perform data protection jobs may differ from those used in other industries such as retail.

For example, the storage capacity thresholds used to trigger a warning condition may differ depending on the usage rate of storage capacity. If, for example, the rate of data storage capacity usage is high, such as in a financial application, it may be desired to use a lower threshold (e.g., 60%) for a warning condition, thus, providing sufficient advance notice to secure additional resources. In a retail application, however, the rate of consumption of storage media may be much lower, so that a warning threshold level may be set a higher percentage (e.g., 80%) which still providing sufficient time to secure additional resources. Thus the reporting modules of the present invention, may be used to analyze storage capacity usage information to predict future storage resource needs, (e.g., additional storage devices) before the resources become overburdened, reach maximum capacity, or become other unusable or inoperable.

In some embodiments of the invention, user-defined metrics may be utilized for generating system management information that may be associated with one or more storage operation cells within a storage system. In such embodiments, users or system administrators may be able to apply desired metrics for particular storage activities. For example, different statistical predictive analysis routines may be applied to data storage activities (e.g., read and/or write operation) associated with storage devices. Other examples may include applying metrics associated with the data pathways taken by storage data during particular storage operations involving sensitive data (e.g., classified information).

In other embodiments of the invention, default-metrics may be utilized for generating system management information that may be associated with one or more storage operation cells within a storage system. In such embodiments, based on end-user requirements, the storage manager and management interface module may provide a set of standard metrics (e.g., storage device priority level) and scheduling criteria (e.g., data backup frequency) for processing storage activity information prior to generating reports (e.g., growth reports). For example, if the storage system is used in retail based industries, a different set of default settings may be used than if the storage system is being utilized for storage management in, for example, law enforcement. For example, in law enforcement applications, data protection jobs may be scheduled to occur more often, the threshold values for storage capacity alerts associate with storage devices may be lower, and growth reports associated with the data protection jobs may be generated more often (seeFIG. 6B).

FIG. 8Ais an illustrative interface screen712that may be used for specifying and evaluating failed storage operations according to an embodiment of the invention. For example, similar to the screens described above, screen712may be generated by management interface module122(FIG. 1), and accessed and displayed to users via interface module115(FIG. 1). The left side of screen712may include directory tree714, which allows users to access and manage different parts of a storage operation system from a unified display. By selecting, for example, “CommCell Growth” element718from reports field716, an illustrative display of various management scheduling options may be presented to a user via display720. Display720may include various time range selection options. For example, a user may select to receive job failure reports over a specified time range (e.g., over last 7 days). Thus, option725may be used to access failure reports over the last seven days. Scheduling option730may include a failure occurrence setting732, which may allow users to specify the number of consecutive job failures that are to be captured and considered a single failure. This allows a user to exclude spurious or accidental failures and define a number of consecutive failures considered to be operationally relevant.

For example, in storage systems where the end-user requirements are relatively fault tolerant, the number of consecutive job failures that may be defined as a single failure occurrence may be set to higher value (e.g., five consecutive failures defined as one occurrence) as opposed to more sensitive applications (e.g., two failures). Scheduling option730may also include a display setting734, which provides an indication of the number of fault occurrence details that may be displayed in the failure report.

As illustrated in the exemplary embodiment ofFIG. 8A, the displayed occurrences are set to five, but other numbers may be used if desired. A failure report may be generated for a particular one or more selected storage operation cells, whereby storage operation cells or storage operation cell groups may be selected using selection fields744and746, respectively

FIG. 8Bshows an illustrative interface screen745for providing reported results based on the entered scheduling information shown inFIG. 8Aaccording to an embodiment of the invention. Table770may illustrate consecutive failures occurrences for the selected “East Coast CommCells” client group, as indicated at information bar772. The generated results may provide users and administrators with information regarding the occurrences of failures with the selected storage operation cell group (i.e., specified by “East Cost CommCells”). For example, within storage operation cell776, storage operation cell application “Windows 2003 32-bit File System”778has incurred failures during default backup operations. The failure reports may be displayed as failure occurrences, as indicated by780, whereby for each failure occurrence, time and date information782may be displayed.

Based on this information, trends may be determined, which may provide information associated with the root cause of certain failures. For example, a failure occurrence may be correlated with other storage operation metrics and other storage related parameters to determine the possible cause of the failure. If, for example, metrics indicate sufficient storage capacity, transmission bandwidth, and media management components, but one or more links in the data pathway to a storage device show increased congestion or failures, such congestion may be attributed to the possible fault. Such information may be correlated with other reports and performance information to identify common resources involved for fault isolation.

Using trending or forecasting analysis, other fault occurrences may be evaluated and compared with each other in a similar manner. If, for example, other fault occurrences show that a particular pathway or storage device has an increasing number of faults, this may indicate a device or pathway is close to failure or overburdened. This allows the system or a user to employ additional or alternative resources to correct a detected problem or inefficiency. For example, the one or more data pathways may be re-routed or additional data communications link may be installed to alleviate any detected problem.

FIGS. 9A-9Dare illustrative interface screens for creating client groups within a storage operation system according to an embodiment of the invention. Referring toFIG. 9A, a new group of storage operation cells may be created by, for example, clicking on Cell-Client Group field902and selecting the New Cell-Client Group field904from directory tree906. By selecting New Cell-Client Group field904, an interface screen, such as exemplary interface screen915illustrated inFIG. 9B, may be presented to system users according to an embodiment of the invention. Using screen915, a system administrator or authorized user may assign a name for the creation of a new storage operation cell group by making an entry in field917.

Description information associated with the cell group may be entered in field920. Similarly time-zone selection may be set using pull-down menu922. Once the fields in Screen915have been entered, an exemplary illustrative interface screen, such as screen925shown inFIG. 9C, may be presented according to an embodiment of the invention. From screen925, one or more storage operation components may be selected. For example, utilizing fields930, one or more storage operation cells (e.g., draco-61 galaxy, dimsum 5.0) may be selected for incorporation in the created storage operation cell group. Also, for example, fields935may be used to select one or more client computers (e.g., DAGGER COMMVAULT.COM) for each of the selected storage operation cells indicated in fields930. Once the one or more storage operation components have been selected, the illustrative interface screen940ofFIG. 9Dmay be used to select one or more applications for use in association with the selected storage operation cell group. As illustrated inFIG. 9D, fields945may provide a selectable list of applications associate with the storage operation cells associated with the created group. Also, as indicated at fields950, a list of applications may also be selected for the other storage system components (e.g., data agents) within the group's storage operation cells. Once the selections have been made from fields945and950, “Finish” button955may be activated.

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 known in the art to input, access, change, manipulate, modify, alter, and work with information.

While the invention has been described and illustrated in connection with preferred embodiments, many variations and modifications as will be evident to those skilled in this art may be made without departing from the spirit and scope of the invention, and the invention is thus not to be limited to the precise details of methodology or construction set forth above as such variations and modification are intended to be included within the scope of the invention.