Comm Vault Systems, Inc.

Brahmaiah Vallabhaneni

Paramasivam Kumarasamy

Jun H Ahn

Rahul S Pawar

Henry Wallace Dornemann

Girish Ramohalli Gopala Rao

Amit Mitkar

Muthusamy Senthilnathan

Amey Vijaykumar Karandikar

Satish Chandra Kilaru

Vimal Kumar Nallathambi

Waqas Ashraf

Anup Kumar

Dmitriy Borisovich Zakharkin

Sanjay Harakhchand Kripalani

David Alan Oshinsky

Bheemesh R Dwarampudi

Prashanth Nagabhushana Bangalore

Sunil Babu Telagamsetti

Ravi Thati

Manoj Kumar Vijayan

Rajesh Polimera

Saurabh Agrawal

Hetal Kapadia

Navatha Devi Chintala

Prakash Varadharajan

Ketan Bansod

Chandresh Sharma

A disclosed framework enables virtually any aggressive Recovery Point Objective (RPO) to be enforced for a production database, without limitation on type of database management system (DBMS) or size of the production database. The framework overcomes technological barriers of the prior art, such as bottlenecks presented by a storage manager computer that traditionally managed database backups. To avoid the bottlenecks, an illustrative data storage management system does not engage the storage manager computer in storage operations that could impact the database RPO. Certain components are added and enhanced to autonomously capture database transaction logs, which are stored securely and persistently away from the DBMS. In a separate and less frequent operation, and with involvement of the storage manager computer, the illustrative system generates secondary copies in their final form. Meanwhile, temporary backup files can be used in restore operations without first being converted into secondary copies.

Enforcing a recovery point objective (RPO) for a production database without generating secondary copies of the production database

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

Systems and methods for enforcing a recovery point objective (RPO) for a production database without generating secondary copies of the production database

A streamlined approach enables customers to retain management control over their data in a database-as-a-service ('DBaaS') setting, by providing managed backup copies outside cloud service providers' sphere of control. An illustrative data storage management system provides control over performing backup operations to generate managed backup copies, storing managed backup copies, recovering managed backup copies in whole or in part, migrating managed backup copies, and migrating DBaaS instances. Management control also extends to choices of where to store the managed backup copies, whether on the same cloud computing platform as the source DBaaS, on a different cloud computing platform, and/or in a non-cloud data center.

Data storage management system for multi-cloud protection, recovery, and migration of databases-as-a-service (DBAAS) and/or serverless database management systems (DBMS)

A data storage system according to certain aspects can share a single snapshot for multiple applications and/or agents. For example, the data storage system can receive snapshot commands from multiple applications and/or agents, and can group them for a single snapshot (e.g., based on time of receipt of the snapshot commands). Data associated with the multiple applications and/or agents may reside on a single LUN or volume. The data storage system can take a single snapshot of the LUN or volume, and generate metadata regarding which portion of the snapshot is related to which application. The single snapshot can be stored in one or more secondary storage devices. The single snapshot may be partitioned into portions relating to different applications and stored separately.

Single snapshot for multiple agents

Restoring archived object-level database data

The data storage system according to certain aspects can implement table level database restore. Table level database restore may refer to restoring a database table and its related data without restoring the entire database. The data storage system may use table metadata index to implement table level restore. A table metadata index may be created for each table, e.g., during a backup of the database. The table metadata index for a table can include any type of information for restoring the table and its related data. Some examples of the type of information included in the table metadata index include the following: container for the table, table backup location, system data, table index, table relationships, etc. Table metadata index can make the restoring of tables fast and efficient by packaging information that can be used to restore a table and its related data in an easily accessible manner.

Table level database restore in a data storage system

Rather than relying on pre-defined scheduling of secondary copy operations such as backup jobs, the illustrative opportunistic approach initiates secondary copy operations based on changing operational conditions in a storage management system. An adaptive backup readiness score is based on a number of backup-readiness operational factors. An illustrative enhanced data agent which is associated with the target database application (or other executable component) may monitor the operational factors and determine the backup readiness score based on weights assigned to the respective operational factors. The enhanced data agent may evaluate recent backup jobs to determine which of the operational factors that contributed to the backup readiness score may have been most relevant. Based on the most-relevant analysis, the enhanced data agent may adapt the weights assigned to the monitored operational factors, so that the backup readiness score may be more suitable and responsive to ongoing operational conditions in the system.

Opportunistic execution of secondary copy operations

Storage managers are used in data storage management systems for license distribution, compliance, and updates. A licensed quota is managed at an aggregate level applicable to a collective plurality of storage operation cells and not by licensing each individual storage operation cell. A multi-cell environment belonging to a given customer is licensed by using an enhanced storage manager in each cell. One storage manager is a 'license server' to the other storage managers or 'child licensees.' A licensor issues a global license to the customer's designated license server, which distributes child licenses and manages other licensing aspects. Rather than licensing usage for individual storage operation cells, licensed usage is managed at an aggregate level using the license server and child licensees in a &#x201c;self-service&#x201d; model.

Using storage managers in data storage management systems for quota distribution, compliance, and updates

The systems and methods provide for migrating database management system (DBMS) applications to cloud storage by automating a continuous replication of changes made to the DBMS from the DBMS to an associated cloud instance. For example, the systems and methods facilitate the migration of the DBMS via multiple processes performing in parallel&#x2014;a process to create and provision a new machine instance (e.g., an EC2 instance), a process to clone and transfer parameters of the operating system/software of the DBMS, and a process that backs up and/or captures the application data of the DBMS. In some embodiments, the systems and methods, utilizing parallel processes, and combining outputs of the processes to a synchronization process, efficiently and quickly migrate DBMS applications to cloud storage, among other benefits.

Migration of a database management system to cloud storage

Data storage management system for protecting cloud-based data including on-demand protection, recovery, and migration of databases-as-a-service and/or serverless database management systems

According to certain aspects, a system may include a computing device configured to: intercept a request from a database application to read a portion of a database file, where a secondary copy of the database file resides on a secondary storage device(s) and is organized as a plurality of first blocks, wherein the request includes a database file offset(s) corresponding to the requested portion; and map the database file offset(s) to a subset of the first blocks that correspond to requested database object(s). The system may include a secondary storage controller computer(s) configured to: access a table that maps the plurality of first blocks to storage locations on the secondary storage device(s); using the table, locate and retrieve the subset of the first blocks on the secondary storage device(s); and forward the retrieved first blocks for storage in a primary storage device(s).

Object-level database restore

Data storage management system for multi-cloud protection, recovery, and migration of databases-as-a-service and/or serverless database management systems

Using storage managers in data storage management systems for license distribution, compliance, and updates

Growing community of inventors

Marlboro, NJ, United States of America

Brahmaiah Vallabhaneni