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: A disclosure for management of multiple information management cells running different versions of software applications using a gateway system is provided herein. The disclosure addresses the drawbacks associated with the current environment of managing multiple information management cells through a separate URL by centralizing the user interfaces (UI) to a single front-end administrative UI that is specific to the version of software application operating on that cell. The gateway system comprises a mapping module, a storage module, a UI module, and a communication module that interoperate to retrieve the version of a software application operating on the targeted cell, the UI running that version of software application, and presenting a user interface that can view and manage the operations of that targeted cell. The gateway system serves the UI specific for the version of software application for that cell from its local collection.

Abstract: Described herein are techniques for better understanding problems arising in an illustrative information management system, such as a data storage management system, and for issuing appropriate alerts and reporting to data management professionals. The illustrative embodiments include a number of features that detect and raise awareness of anomalies in system operations, such as in deduplication pruning operations. Such anomalies can include delays in the processing of archive files to be deleted and/or delays in the generation of the list of archive files to delete. Anomalies are characterized by frequency anomalies and/or by occurrence counts. Utilization is also of interest for certain key system resources, such as deduplication databases, CPU and memory at the storage manager, etc., without limitation.

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: Described herein are techniques for better understanding problems arising in an illustrative information management system, such as a data storage management system, and for issuing appropriate alerts and reporting to data management professionals. The illustrative embodiments include a number of features that detect and raise awareness of anomalies in system operations. Categories of interest include events and job anomalies, such as long-running jobs and job success/failure rates. Anomalies are characterized by frequency anomalies and/or by occurrence counts. Utilization is also of interest for certain key system resources, such as deduplication databases, CPU and memory at the storage manager, etc., without limitation. Predicting low utilization periods for these and other key resources is useful for scheduling maintenance activities without interfering with ordinary data protection jobs.

Abstract: A system may measure one or more metrics relating to the performance of a job for a set of occurrences of the job with respect to a data set. The measurements may be used to predict a completion time for a subsequent job or phase of the job on the data set. This prediction may be used to present a more accurate indication of a job completion status on the data set. The process may be repeated or performed separately for each client or set of data to provide an individualized progress meter or indicator. Thus, in some cases, variances in the data or computing systems may be reflected in the displayed progress of the job providing for a more accurate indication of job progress.

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 region-based distributed information management system is described herein in which some or all of the operations typically performed by a centralized storage manager can be distributed to storage managers located in the various geographic regions. These regional storage managers can manage components of the information management system located in their respective geographic region, and communicate with the centralized storage manager (also referred to herein as a “master storage manager”) for synchronization purposes and/or to hand off operations that cannot be performed by the regional storage manager.

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, a method can include electronically accessing, by a storage manager, a stored synchronization policy specifying at least a first folder associated with a first computing device and a second folder associated with a second computing device; identifying a first file stored in the first folder as a candidate for synchronization; receiving an indication as to a location of the first computing device and the second computing device; in response to a determination that the first computing device is not located within a geographic region, electronically generating and transmitting instructions to the first computing device to remove the first file from the first folder; and in response to a determination that the second computing device is located within the geographic region, electronically generating and transmitting instructions to cause transmission of the first file to the second computing device for storage in the second folder.

Abstract: Techniques for providing data preview before recalling large data files are disclosed. In one aspect, a data file is made accessible while being offline by converting the data file from a native format to a preview format, storing the data file in the preview format in a primary storage that is locally available and moving, after the conversion to the preview format, the data file in the native format to a secondary storage. When a viewing request is received for the data file, the data file in the preview format is displayed to fulfill the viewing request.

Abstract: A disclosure for management of multiple information management cells running different versions of software applications using a gateway system is provided herein. The disclosure addresses the drawbacks associated with the current environment of managing multiple information management cells through a separate URL by centralizing the user interfaces (UI) to a single front-end administrative UI that is specific to the version of software application operating on that cell. The gateway system comprises a mapping module, a storage module, a UI module, and a communication module that interoperate to retrieve the version of a software application operating on the targeted cell, the UI running that version of software application, and presenting a user interface that can view and manage the operations of that targeted cell. The gateway system serves the UI specific for the version of software application for that cell from its local collection.

Abstract: The data storage system according to certain aspects can allow users to share a portion of a file (e.g., a document) 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 data storage system according to certain aspects can also provide a native view of secondary storage data on a client computer. The index data and/or metadata relating to secondary storage data may be stored in native format (e.g., format of the application(s) that generated the secondary storage data) so that the secondary storage data can be displayed in a native view. The index data and/or metadata may be synchronized on the client without synchronizing the secondary storage data itself.

Abstract: An illustrative expandable data storage management system includes rules for assigning data protection operations to suitable subtending storage service cells. Each cell is specially configured to protect certain data types and/or to provide certain storage resources for backup data. The system controls customer account access, authentication, service allocation, data security, and sharing of information between a centralized “hub manager” and the storage service cells that perform storage operations, including data backup, data recovery, and data lifecycle management. The system maintains a many-to-many relationship between distinct customers and storage service cells so that any storage service cell may be responsible for protecting any number of data sources of any number of distinct customers, and responsibility for protecting any given customer's data sources may be distributed among any number of storage service cells.

Abstract: Techniques for providing data preview before recalling large data files are disclosed. In one aspect, a data file is made accessible while being offline by converting the data file from a native format to a preview format, storing the data file in the preview format in a primary storage that is locally available and moving, after the conversion to the preview format, the data file in the native format to a secondary storage. When a viewing request is received for the data file, the data file in the preview format is displayed to fulfill the viewing request.

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 region-based distributed information management system is described herein in which some or all of the operations typically performed by a centralized storage manager can be distributed to storage managers located in the various geographic regions. These regional storage managers can manage components of the information management system located in their respective geographic region, and communicate with the centralized storage manager (also referred to herein as a “master storage manager”) for synchronization purposes and/or to hand off operations that cannot be performed by the regional storage manager.

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: Described herein are techniques for better understanding problems arising in an illustrative information management system, such as a data storage management system, and for issuing appropriate alerts and reporting to data management professionals. The illustrative embodiments include a number of features that detect and raise awareness of anomalies in system operations, such as in deduplication pruning operations. Such anomalies can include delays in the processing of archive files to be deleted and/or delays in the generation of the list of archive files to delete. Anomalies are characterized by frequency anomalies and/or by occurrence counts. Utilization is also of interest for certain key system resources, such as deduplication databases, CPU and memory at the storage manager, etc., without limitation.

Abstract: Described herein are techniques for better understanding problems arising in an illustrative information management system, such as a data storage management system, and for issuing appropriate alerts and reporting to data management professionals. The illustrative embodiments include a number of features that detect and raise awareness of anomalies in system operations. Categories of interest include events and job anomalies, such as long-running jobs and job success/failure rates. Anomalies are characterized by frequency anomalies and/or by occurrence counts. Utilization is also of interest for certain key system resources, such as deduplication databases, CPU and memory at the storage manager, etc., without limitation. Predicting low utilization periods for these and other key resources is useful for scheduling maintenance activities without interfering with ordinary data protection jobs.