Comm Vault Systems, Inc.

Tinton Falls, Inc.

Amey Vijaykumar Karandikar

Anand Vibhor

Parag Gokhale

Rajiv Kottomtharayil

Bhavyan Bharatkumar Mehta

Manoj Kumar Vijayan

Yu Albert Wang

Paramasivam Kumarasamy

Prakash Varadharajan

Rahul S Pawar

Henry Wallace Dornemann

Amit Mitkar

Jun H Ahn

Brahmaiah Vallabhaneni

Satish Chandra Kilaru

Hemant Mishra

Muthusamy Senthilnathan

Gokul Pattabiraman

Deepak Raghunath Attarde

Mrityunjay Upadhyay

Aaron E Bilbrey

Kedar Sunil Sarmalkar

Durga Prasad Chedalavada

Suma Seshadri

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).

Restoring archived database data

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.

Recovery Point Objective (RPO) driven backup scheduling in a data storage management system

Restoring archived object-level database data

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.

Distributed and scalable client-based and microservices-based storage management

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.

Automation of data storage activities

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.

System and method for client policy assignment in a data storage system

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.

Log monitoring

A system according to certain aspects improves the process of managing log data. The system may receive a log data file including one or more log lines that contain information relating to computing operations. At least some of the log lines may include a static portion and a variable portion. The system may process a first log line to identify and extract a static portion from the first log line, and determine a first value for the first log line based on the extracted static portion. The system may process a second log line to identify and extract a static portion from the second log line, and determine a second value for the second log line based on the extracted static portion. The system may compare the first and second values, and based on the comparison, organize the first and second log lines together for presentation to a user.

Management of log data

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.

Data synchronization management

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.

Sharing of secondary storage data

Distributed and scalable client-based storage management

Distributed and scalable storage management using a storage-microservices server

Growing community of inventors

Long Branch, NJ, United States of America

Amey Vijaykumar Karandikar