Emc IP Holding Company LLC

Rejith Mohan M

Navneet Upadhyay

Shelesh Chopra

Amith Ramachandran

Shraddha Chunekar

Yasemin Ugur-Ozekinci

Ken Owens

Reshmee Jawed

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

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

System extracts metadata of system committed change numbers, system change numbers for backup copies. System generates start system change numbers as minimums of committed change numbers, end system change numbers as maximums of change numbers, and identifiers for archive log backup copies. System identifies dependent system change numbers from start number to end number for backup copy. System identifies backed-up system change numbers, from start numbers to end numbers for log backup copies, which are in dependent numbers. If backed-up numbers don't include all dependent numbers, system outputs missing system change numbers. System generates start numbers, end numbers, and identifiers for new archive log backup copies, identifies new backed-up system change numbers, from start numbers to end numbers for new log backup copies, which are in missing numbers. If new backed-up numbers include all missing numbers, system stores backup copy with each log backup copy corresponding to any backed-up numbers.

Dynamically updating database archive log dependency and backup copy recoverability

In general, the invention relates to a method for performing operations. The method includes protecting a database includes detecting a first trigger event for a first backup operation targeting an user asset of a client device of client devices, wherein the first trigger event specifies first metadata associated with the first backup operation, acquiring a first byte-range lock associated with a backup type specified in the first metadata in an asset lock file associated with the user asset, acquiring a second byte-range lock of the asset lock file that is associated with a storage mounting operation, after acquiring the first byte-range lock and the second byte-range lock, mounting a backup storage to the client device using the first metadata, unlocking the second byte-range lock, and performing, after unlocking the second byte-range lock, the first backup operation on the user asset.

Method and system for parallel data transmission and cooperating backups

System extracts backup metadata, comprising committed change numbers, system change numbers, types, database version identifiers, and details, for backup copies. System generates data structure, comprising start system change numbers, based on minimums of system committed change numbers, end system change numbers and maximums of system change numbers, database version identifiers, and identifiers including details, for the backup copies. System identifies at least first type of backup copies as candidate dependent backup copies and at least second type of backup copies as candidate preceding backup copies. System outputs identifiers of candidate dependent backup copy, corresponding dependency, and candidate preceding backup copy, based on identifying same database version identifier of candidate dependent backup copy and candidate preceding backup copy, and maximum of end system change numbers of candidate preceding backup copies which is less than or equal to start system change number and/or end system change number of candidate dependent backup copy.

Identifying database backup copy chaining

In general, the invention relates to a method for performing backup operations. The method includes generating a full backup of a user asset at a first point in time, generating an incremental backup after the full backup is generated, applying the incremental backup to the full backup to generate a second full backup, obtaining a distinct data files subset associated with the second full backup, and deleting the distinct data files subset from the second full backup to obtain a third full backup.

Growing community of inventors

Thiruvanathapuram, India

Rejith Mohan M