Comm Vault Systems, Inc.

Jun H Ahn

Manas Bhikchand Mutha

Rahul S Pawar

Henry Wallace Dornemann

Brahmaiah Vallabhaneni

Paramasivam Kumarasamy

Sri Karthik Bhagi

Anup Kumar

Rajiv Kottomtharayil

Waqas Ashraf

Girish Ramohalli Gopala Rao

Yan Liu

David Ngo

Muthusamy Senthilnathan

Parag Gokhale

Tirthankar Chatterjee

Amit Mitkar

Amey Vijaykumar Karandikar

Satish Chandra Kilaru

Prosenjit Sinha

Duncan Alden Littlefield

Bhavyan Bharatkumar Mehta

Prasad Nara

Kuldeep Kumar

Ketan Bansod

Priya Sundaresan

Check Abdoul Cader Sabjan

Anand Prahlad

Deepak Raghunath Attarde

Marcus S Muller

Brian Brockway

Jeremy Alan Schwartz

Anand Vibhor

Pavan Kumar Reddy Bedadala

Arun Prasad Amarendran

Ho-Chi Chen

Vipul Pawale

Pavlo Mazur

Christopher A Alonzo

Yongtao Liu

Chitra Ramaswamy

Sudha Krishnan Iyer

Amit Mahajan

Jatin Kirtikumar Sanghvi

Oleg Kobozev

Lei Wang

Vishal Prakashchand Khule

Sesha N Krishnan

Arun Kumar Krishna Shankar

Sunghyun Wang

A system for performing continuous transaction log backups with minimal resource usage of the client computing devices that are processing the transactions is disclosed. The system detects at least one input/output (I/O) activity at a client computing device. The I/O activity can be associated with at least one database operation performed via the client computing device. The system then executes one or more native commands to backup transactions log data associated with the detected I/O activity to a virtualized location. Backing-up the transactions log data comprises dynamically identifying a mount path location corresponding to the virtualized location, and transferring the transactions log data to the dynamically identified mount path using the one or more native commands. The system can then perform data processing operations (for example, data chunking and deduplicating) on the transactions log data after it is received at the dynamically identified mount path location.

Continuously run log backup with minimal configuration and resource usage from the source machine

An illustrative data storage management system comprises a management database that stores administrative preferences and system configurations, as well as results and/or statistics of completed secondary storage operations, i.e., information needed by the system to protect customers' data and to track and recover the protected data, including secondary copies such as backup copies, archive copies, etc. The disclosed data storage management system is configured to protect its own system data subject to a very aggressive (short) Recovery Point Objective (RPO), by using an innovative infrastructure that enables the system's storage manager to fail over to any number of other failover destination storage managers, each one comprising a destination management database. An illustrative database granularly tracks whether each and every transaction log file has been successfully applied to each and every destination management database to synchronize with the source management database.

Resiliency of a data storage system by protecting its management database to meet a recovery point objective (RPO)

The present inventors devised a holistic approach for protecting serverless applications in single-cloud, multi-zone, multi-cloud, and/or non-cloud data center computing environments. An illustrative data storage management system discovers application assets, relationships, and interoperability dependencies and creates an 'application entity' that references the various assets. Protection preferences apply to the application entity as a whole. An orchestration function in the system coordinates storage management operations (e.g., backup, replication, live synchronization, etc.) in a suitable order of operations gleaned from asset dependencies, if any. A set of copies of the application's discovered assets are generated in coordinated fashion and represent a point-in-time copy of the application. The point-in-time copy can be restored and/or migrated to other computing services by the data storage management system. The orchestration function coordinates restore and migration operations, including any cloud-to-cloud or cloud-to/from-non-cloud conversions that might be necessary to activate the application in a different computing environment.

Holistic protection of cloud-based serverless applications

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

An information management system according certain aspects for archiving file system content may include a third-party application archiving data agent configured to: access third-party application archiving rules for archiving data to one or more secondary storage devices, wherein the third-party application archiving rules are defined by a third-party application to archive files associated with the third-party application; access third-party metadata associated with a plurality of files in a file system, wherein the plurality of files is associated with the third-party application and the third-party metadata is defined by the third-party application; determine whether to archive one or more files of the plurality of files based at least in part on the third-party application archiving rules and the third-party metadata; and in response to determining that a first file of the plurality of files should be archived, archive the first file to the one or more secondary storage devices.

File system content archiving based on third-party application archiving rules and metadata

An information management system according to certain aspects may be configured to generate a snapshot of data relating to a plurality of applications. The system may include a plurality of data agents, wherein each data agent is associated with at least one of a plurality of applications, and data generated by the plurality of applications is stored in a logical volume in primary storage. The system may also include a snapshot manager configured to detect the plurality of applications; check with the plurality of data agents whether the associated applications are in consistent states; obtain a snapshot of the logical volume in response to receiving notifications from the plurality of data agents that the associated applications are in consistent states; and generate mapping information between a particular one of the plurality of applications and a portion of the snapshot relating to the particular one of the plurality of applications.

Single snapshot for multiple applications

Certain embodiments described herein relate to an improved selective data backup system. In some embodiments, one or more components in an information management system can determine that a portion of the primary data scheduled for backup was previously backed up or is scheduled to be backed up as part of another backup operation. For example, a data agent performing a cluster-level backup operation for an entire cluster of storage servers may check whether any part of the primary data was previously backed up by a prior server-level backup operation for one of the storage servers in the cluster. If so, the data agent may skip, in the cluster-level backup operation, any portion of the primary data stored in the storage server previously backed up as part of the prior server-level backup operation.

Skipping data backed up in prior backup operations

Systems and methods for providing and/or facilitating live browsing of granular mail or mailbox data, such as data stored within Exchange mailboxes, are described. For example, the systems and methods may provide mechanisms for browsing and/or restoring granular data (e.g., email data) from an Exchange database backup copy (or other secondary copy), without having to restore the entire database from the backup copy.

Live browsing of granular mailbox data

Protecting a management database of a data storage management system to meet a recovery point objective (RPO)

A system for providing user access to electronic mail includes an email client and an email server. The email client receives and communicates a user interaction with an email message The email server that receives the communication, determines whether the email message stored in a live database or in a backup storage. Upon determination that the email message is stored in a backup storage, the email server performs a message exchange with a backup storage system to perform the user-requested action.

Techniques for serving archived electronic mail

Data storage management system for holistic protection of cloud-based serverless applications in single cloud and across multi-cloud computing environments

An information management system according to certain aspects can implement application archiving. The system may archive one or more applications on computing devices to make more storage space available on these devices. The system can determine which applications on client computing device to archive based on various factors. Some examples of factors can include frequency of use, application type, amount of application data and/or storage, user and/or device location, etc. The data to be archived can include one or more executable file(s), metadata, actual data, etc. After an application is archived, the system can generate a placeholder for the application; a placeholder can include information for restoring the archived application.

Archiving applications in information management systems

Restoring archived object-level database data

Growing community of inventors

Manalapan, NJ, United States of America

Jun H Ahn