Abstract: Embodiments are described for distributed and scalable client-based storage management and microservices-based storage management, which can operate in combination. Embodiments distribute responsibilities and client-specific information needed for storage management jobs away from a central storage manager and its management database. New features and components minimize communications to/from the storage manager and ensure the integrity and synchronization of data being distributed. The management database at the storage manager retains its role as repository of information for the data storage management system as a whole, yet without being a bottleneck to storage operations. Improvements are implemented within the storage manager, through new functionality added to clients, and further through a new micro-server component interposed between storage manager and clients.

Abstract: Embodiments are described for distributed and scalable client-based storage management and microservices-based storage management, which can operate in combination. Embodiments distribute responsibilities and client-specific information needed for storage management jobs away from a central storage manager and its management database. New features and components minimize communications to/from the storage manager and ensure the integrity and synchronization of data being distributed. The management database at the storage manager retains its role as repository of information for the data storage management system as a whole, yet without being a bottleneck to storage operations. Improvements are implemented within the storage manager, through new functionality added to clients, and further through a new micro-server component interposed between storage manager and clients.

Abstract: Embodiments are described for distributed and scalable client-based storage management and microservices-based storage management, which can operate in combination. Embodiments distribute responsibilities and client-specific information needed for storage management jobs away from a central storage manager and its management database. New features and components minimize communications to/from the storage manager and ensure the integrity and synchronization of data being distributed. The management database at the storage manager retains its role as repository of information for the data storage management system as a whole, yet without being a bottleneck to storage operations. Improvements are implemented within the storage manager, through new functionality added to clients, and further through a new micro-server component interposed between storage manager and clients.

Abstract: A system receives data storage workflow activities that include computer-executable instructions for carrying out data storage workflow in a network data storage system. Once the workflow is received, the system deploys the workflow to one or more workflow engines that can execute the various data storage activities related to the workflow. Prior to executing a data storage activity, the system can determine which workflow engine to use based on an allocation scheme.

Abstract: According to certain aspects, an information management cell can include at least one secondary storage computing device configured to conduct primary data generated by at least one client computing device to a secondary storage device(s) as part of secondary copy operations, wherein the secondary storage computing device normally operates to conduct primary data to the secondary storage device(s) for storage as a secondary copy in a first secondary copy file format, at the direction of a main storage manager; and can include a failover storage manager configured to activate in response to loss of connectivity between the cell and the main storage manager, and instruct a secondary copy application to perform a secondary copy operation in which the primary data generated by the at least one client computing device is stored as a secondary copy in a second secondary copy file format different than the first secondary copy file format.

Abstract: Disclosed herein are systems and methods for managing information management operations. The system may be configured to employ a work flow queue to reduce network traffic and manage server processing resources. The system may also be configured to forecast or estimate information management operations based on estimations of throughput between computing devices scheduled to execute one or more jobs. The system may also be configured to escalate or automatically reassign notification of system alerts based on the availability of system alert recipients. Various other embodiments are also disclosed herein.

Abstract: A resource allocation system begins with an ordered plan for matching requests to resources that is sorted by priority. The resource allocation system optimizes the plan by determining those requests in the plan that will fail if performed. The resource allocation system removes or defers the determined requests. In addition, when a request that is performed fails, the resource allocation system may remove requests that require similar resources from the plan. Moreover, when resources are released by a request, the resource allocation system may place the resources in a temporary holding area until the resource allocation returns to the top of the ordered plan so that lower priority requests that are lower in the plan do not take resources that are needed by waiting higher priority requests higher in the plan.

Abstract: To perform Recovery Point Objective (RPO) driven backup scheduling, the illustrative data storage management system is enhanced in several dimensions. Illustrative enhancements include: streamlining the user interface to take in fewer parameters; backup job scheduling is largely automated based on several factors, and includes automatic backup level conversion for legacy systems; backup job priorities are dynamically adjusted to re-submit failed data objects with an “aggressive” schedule in time to meet the RPO; only failed items are resubmitted for failed backup jobs.

Abstract: A system and method to perform data management operations in a data management system assigns the data management request to one or more available data management resources. If the data management request fails, at least one data management resource at least partially responsible for the failure is determined, as is a category associated with the one data management resource at least partially responsible for the failure. Other data management requests are identified in a list of data management requests that request data management resources having the same category and the list of data management requests is updated to indicate that the data management system should not perform the other identified data management requests.

Abstract: Disclosed herein are systems and methods for managing information management operations. The system may be configured to employ a work flow queue to reduce network traffic and manage server processing resources. The system may also be configured to forecast or estimate information management operations based on estimations of throughput between computing devices scheduled to execute one or more jobs. The system may also be configured to escalate or automatically reassign notification of system alerts based on the availability of system alert recipients. Various other embodiments are also disclosed herein.

Abstract: A system receives data storage workflow activities that include computer-executable instructions for carrying out data storage workflow in a network data storage system. Once the workflow is received, the system deploys the workflow to one or more workflow engines that can execute the various data storage activities related to the workflow. Prior to executing a data storage activity, the system can determine which workflow engine to use based on an allocation scheme.

Abstract: A system and method for property assignment in a data storage system is presented. A data storage system defines a client configuration profile comprising a set of storage operation properties, wherein the storage operation properties regulate criteria for performing storage operations by the data agent on client devices that are associated with the client configuration profile. A storage management system associates a first client device to the client configuration profile; and communicates the set of properties of the client configuration profile to property tables of corresponding objects in the first client device.

Abstract: A resource allocation system begins with an ordered plan for matching requests to resources that is sorted by priority. The resource allocation system optimizes the plan by determining those requests in the plan that will fail if performed. The resource allocation system removes or defers the determined requests. In addition, when a request that is performed fails, the resource allocation system may remove requests that require similar resources from the plan. Moreover, when resources are released by a request, the resource allocation system may place the resources in a temporary holding area until the resource allocation returns to the top of the ordered plan so that lower priority requests that are lower in the plan do not take resources that are needed by waiting higher priority requests higher in the plan.

Abstract: An information management system according to certain aspects allows users to share a portion of a file (e.g., a document) stored in secondary storage. The user may specify a portion of a secondary storage file to share and send a link to the portion to another user. The other user can access the shared portion from the link, and just the shared portion may be restored from secondary storage. The system according to certain aspects provides a native view of secondary storage data on a client computing device. The index data and/or metadata relating to secondary storage data may be stored in native application format for access via the native source application.

Abstract: A system and method to perform data management operations in a data management system assigns the data management request to one or more available data management resources. If the data management request fails, at least one data management resource at least partially responsible for the failure is determined, as is a category associated with the one data management resource at least partially responsible for the failure. Other data management requests are identified in a list of data management requests that request data management resources having the same category and the list of data management requests is updated to indicate that the data management system should not perform the other identified data management requests.

Abstract: To perform Recovery Point Objective (RPO) driven backup scheduling, the illustrative data storage management system is enhanced in several dimensions, including an illustrative enhanced data agent and an illustrative enhanced storage manager. Illustrative enhancements include: streamlining the user interface to take in fewer parameters; backup job scheduling is largely automated based on several factors, and includes automatic backup level conversion for legacy systems; backup job priorities are dynamically adjusted to re-submit failed data objects with an “aggressive” schedule in time to meet the RPO; only failed items are resubmitted for failed backup jobs.

Abstract: A log monitoring system uses log monitoring rules to monitor log data generated by applications executing on a client computing device. By monitoring log data, the system detects that one or more triggering events have occurred on the client computing device. In response, the log monitoring system can perform one or more appropriate remedial actions. Additionally, in response to the detected event(s), the log monitoring system can extract a select subset of relevant data from the client and transmit the subset of data to a separate repository for storage and/or processing.

Abstract: A system and method for property assignment in a data storage system is presented. A data storage system defines a client configuration profile comprising a set of storage operation properties, wherein the storage operation properties regulate criteria for performing storage operations by the data agent on client devices that are associated with the client configuration profile. A storage management system associates a first client device to the client configuration profile; and communicates the set of properties of the client configuration profile to property tables of corresponding objects in the first client device.

Abstract: To perform Recovery Point Objective (RPO) driven backup scheduling, the illustrative data storage management system is enhanced in several dimensions. Illustrative enhancements include: streamlining the user interface to take in fewer parameters; backup job scheduling is largely automated based on several factors, and includes automatic backup level conversion for legacy systems; backup job priorities are dynamically adjusted to re-submit failed data objects with an “aggressive” schedule in time to meet the RPO; only failed items are resubmitted for failed backup jobs.

Abstract: According to certain aspects, systems and methods are provided for grouping clients together in a networked data storage environment. For instance, clients can be grouped together based on the software installed on the client or the client type. Each client group can be configured to maintain the configuration of clients within the client group. For example, one client group can be configured to ensure that a particular software suite remains up-to-date. Another client group can be configured to ensure that data within a particular directory or on a particular storage device associated with each client of the client group is backed up each night.