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:
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:
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, a system may include a data agent configured to: process a database file residing on a primary storage device(s) to identify a subset of data in the database file for archiving, the database file generated by a database application; and extract the subset of the data from the database file and store the subset of the data in an archive file on the primary storage device(s) as a plurality of blocks having a common size; and at least one secondary storage controller computer configured to, as part of a secondary copy operation in which the archive file is copied to a secondary storage device(s): copy the plurality of blocks to the secondary storage devices to create a secondary copy of the archive file; and create a table that provides a mapping between the copied plurality of blocks and corresponding locations in the secondary storage device(s).
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:
In general, a data synchronization management system is disclosed in which files (and/or other data) are synchronized among two or more computing devices. Synchronization policies specify files to be synchronized based on selected criteria including file data, metadata, and location information. In general, files are initially copied from a primary client computing device to secondary storage. Thereafter, files to be synchronized are identified from the secondary storage and copied to other computing devices. Additionally, synchronized files may be viewed and accessed through a cloud and/or remote file access interface.
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:
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.