Emc IP Holding Company LLC

Dell Products Inc.

Amith Ramachandran

Navneet Upadhyay

Shelesh Chopra

Shraddha Chunekar

Yasemin Ugur-Ozekinci

Adrian Dobrean

Soumen Acharya

Asif Khan

Sunder Ramesh Andra

Deepthi Urs

Reshmee Jawed

Pati Mohan

Amarendra Behera

Tushar Dethe

Ashish Kumar

Himanshu Arora

Sapna Chauhan

Gururaj Soma

Rejith Mohan M

Deepika Nagabushanam

Elango Chockalingam

Ken Owens

Ban Wang

Sunil Kumar Yadav

Mahantesh M Ambaljeri

Krishnendu Bagchi

Jayashree B Radha

Xiaoliang Zhu

Pawan Singh

Shivaraj Abbigeri

Kenneth William Owens

Srikanth Chowdary Marri

Madhukar Shukla

Shaofeng Chang

Arun Chakravarthy

Siddappa N Ambiger

Haritha Kora

Trichy Krishnamurthi Premkumar

Hui Yang

Matt Buchman

Amrit Lal Jain

Rachana Murthy

Hari Palani

Iresha Gadikar

William E Crosby, Iii

Deepak Anantha Bellare Mallya

Kanagasabapathy Venkatachalam

In general, embodiments relate to a method for generating synthetic full backups, the method comprising: performing a verification that a previous backup of source data stored in a data domain is a failed synthetic full backup, obtaining based on the verification a latest snapshot of the source data, obtaining based on the verification a prior snapshot of the source data making a determination, using a copy list that a first portion of the data items in the copy list exists in the previous backup and a second portion of the data items does not exist in the previous backup, and performing based on the determination a copy operation to copy the second portion of the data items to the data domain to obtain a synthetic full backup.

Method and system for idempotent synthetic full backups in storage devices

In general, embodiments relate to a method for backing up databases, the method includes receiving a backup request, wherein the backup request specifies a role of primary and an asset group identifier for an asset group, identifying, based on the backup request, a database in the asset group, and issuing the backup request for the database.

Scheduling backups on a primary database in a high-availability configuration

In general, in one aspect, the technology relates to a method for backing up assets, the method comprising: making a first determination about an asset type of an asset, based on the first determination, associating the asset with an asset group, wherein all assets in the asset group are of the asset type, and protecting the asset in the asset group using a backup strategy associated with the asset group.

Management of asset groups

A method for performing backups. The method includes sending, via a data manager, a quiesce request to a client storage array of a client device to put the client storage array in a quiesced state. The method also includes obtaining, via a primary backup storage system, a snapshot-based backup of a storage volume of the client storage array while the client storage array is in the quiesced state. Further, the method includes sending an unquiesce request to the client storage array in response to determining that the obtaining of the snapshot-based backup is complete. Moreover, the method includes sending the snapshot-based backup from the primary backup storage system to a secondary backup storage system. In addition, the method includes generating, using the secondary backup storage system, a protection copy based on the snapshot-based backup.

System and method to enable a snapshot-based backup

Described is a system for management of specialized files used for a backup restore. The system may allow for an automated recovery to be performed without having to manually identify critical information required to perform a restore of a particular backup within a backup chain. This information may include a control file and a parameter file. A backup agent may store such information within specialized objects that are stored as part of metadata managed by a backup agent to provide an additional layer of recover capability and efficiency. This information may then be leveraged for retrieval during a restore operation, for example, in a disaster recovery scenario.

Efficient management of specialized control files used for backup restore

Techniques described herein relate to a method for reporting database backup information. The method may include starting a monitor process; generating a flag file for the database backup comprising a parent process identifier (PID) of a parent process of a first child process; associating a second child process with the monitor process by identifying the flag file using the parent PID; receiving channel close alerts from the child processes; making a first determination that backup jobs performed in a first channel were successful; making a second determination that backup jobs performed in the second channel were successful; and transmitting, based on the first determination and the second determination, a backup success report to a backup coordinator.

Reporting for database backups

System extracts backup metadata, comprising system committed change numbers, system change numbers, types, and database version identifiers, for backup copies. System generates data structure, comprising start system change numbers, based on minimums of system committed change numbers, end system change numbers, based on maximums of system change numbers, database version identifiers, and identifiers for archive log backup copies. System identifies dependent system change numbers, based on start system change number to end system change number for backup copy corresponding to database version identifier. System identifies, in data structure, backed-up system change numbers, based on start system change numbers to end system change numbers for archive log backup copies corresponding to database version identifier, which are included in dependent system change numbers. If backed-up system change numbers include all of dependent system change numbers, system stores backup copy with each archive log backup copy corresponding to backed-up system change numbers.

Identifying database archive log dependency and backup copy recoverability

Techniques described herein relate to a method for generating synthetic full backups. The method may include obtaining a snapshot associated with a previous backup stored in a data domain; obtaining a second snapshot associated with a current state of the source data; generating a snapshot difference report using the first snapshot and the second snapshot and including a delete list, a rename list, and a copy list; storing a copy of the previous backup in the data domain; performing a delete operation on the copy based on the delete list; performing a rename operation on the copy based on the rename list; and performing a copy operation based on the copy list. In one or more embodiments, performing the delete operation, the rename operation, and the copy operation on the copy of the previous backup generates a first synthetic full backup of the source data.

Methods and systems for differential based backups

A method and system for maintaining live database data across hybrid storage. Specifically, the disclosed method and system entail accessing live backup database data in part residing on local storage and in part residing on remote storage. That is, on occasion, available local storage capacity may fall short of the required free storage space to accommodate the full restoration or recovery of a given database. Accordingly, to overcome this shortfall, the disclosed method and system detect and cycle the recovery of frequently accessed asset (or database) data files, of the given database, from remote storage onto local storage.

Method and system for maintaining live database data across hybrid storage

A method for data consolidation and preservation during backups of data stored in a source device from the source device to a target device is provided. The method is executed by the source device and includes: obtaining a first snapshot of the data and a second snapshot of the data; generating, in response to the obtaining, a first snapshot difference report using the first snapshot and the second snapshot; transmitting, in response to generating the first snapshot difference report, the first snapshot difference report to the target device to be stored with a backup copy of the data; and deleting, in response to transmitting the first snapshot difference report, the first snapshot.

System and method for snapshot cleanup and report consolidation

Creating vendor-neutral data protection operations for vendors' application resources is described. Capabilities specified for data protection operations by a vendor of an application are input from a host of the application. Any capabilities specified for the data protection operations are used to create a vendor-neutral version of a data protection operation for a resource of the application. The vendor-neutral version of the data protection operation for the application resource is output to the host. A result of performing the vendor-neutral version of the data protection operation on the application resource is input from the host.

Creating vendor-neutral data protection operations for vendors' application resources

In general, embodiments relate to a method for performing rename operations, the method comprising: obtaining a rename list from a snapshot difference report, sorting the rename list to obtain an ordered rename list, making a determination using the ordered rename list that circular rename entries exist in the ordered rename list, based on the determination, creating a plurality of temporary target paths based on the circular rename entries, generating a temporary rename list of the rename operations, generating a circular rename list of the rename operations, performing rename operations in the temporary rename list, and after completing operations in the temporary rename list, performing rename operations in the circular rename list.

Method and system for performing rename operations during differential based backups in storage devices

Systems and methods for deleting backup pieces associated with an application such as a database application. Backup pieces are identified and deleted from the database records and from the backup application.

Centralized retention and backup deletions

A method and system for auto live-mounting database golden copies. Specifically, the disclosed method and system entail reactively auto live-mounting golden copy databases on hosts or proxy hosts based on the operational state of one or more database hosts and/or one or more assets (or databases) residing on the database host(s). Should a database host prove to be unresponsive, through periodic monitoring, databases residing on the database host may be brought back online on a proxy database host using stored golden copies respective of the aforementioned databases. Alternatively, should a given database on any database host exhibit an operational abnormality (e.g., an error, failure, etc.), the given database may be brought back online on the database host or a proxy database host using a stored golden copy respective of the given database. Accordingly, through the disclosed method and system, database outages may be minimized.

Method and system for auto live-mounting database golden copies

In general, the invention relates to a method for performing backup operations. The method includes generating a backup on backup storage system, locking the backup for a retention span, generating a backup archive log image using archive log files for the backup, and locking the backup archive log image for a second retention span.

Method and system for generating immutable backups with configurable retention spans

Growing community of inventors

Bengaluru, India

Amith Ramachandran