Emc IP Holding Company LLC

Deependra Pratap Singh

Shelesh Chopra

Amarendra Behera

Tushar Dethe

Himanshu Arora

Sunil Kumar Yadav

Ravi Vijayakumar Chitloor

Jigar Premajibhai Bhanushali

Prabhat Kumar Dubey

Sapna Chauhan

Anjana Rao

Vipin Kumar Kaushal

PrabhatKumar Dubey

Gururaj Soma

Described is a system for cloud-based processing of backup data for storage onto various types of object storage systems. A specialized cloud-based component (e.g. proxy server) may act as an intermediary when backing up data from a client system to an object storage. For example, the cloud-based component may be provided as part of backup service that operates in conjunction with a client system. Accordingly, the system may allow different clients of a backup service to efficiently and seamlessly interact with the different third-party object storage providers via a single cloud-based component. To provide such object-storage-agnostic functionality, the cloud-based component may include a function library that includes object-storage-specific functions. For example, the cloud-based component may invoke a specific set of operations that interact with a storage API provided by a particular object storage provider.

Cloud-based processing of backup data for storage onto various types of object storage systems

Described is a system (and method) for specialized data management when performing incremental backups to a cloud-based object storage. When backing up client data, the server may utilize incremental backups to conserve the amount of storage space required on the object storage. However, the server may implement a configuration that enables full reconstruction of the client data at the time of recovery. To provide such capabilities, the server may leverage a specialized metadata database. The metadata database may be an embedded database maintained by the server. The server may leverage the metadata database to provide further storage efficiencies by storing certain incremental backup data exclusively within the metadata database. Accordingly, the server may implement a data management configuration as part of a backup service that conserves storage usage, and as a result, storage costs when using on a third-party cloud-based object storage.

Specialized data management for performing incremental backups to a cloud-based object storage

Described is a system for managing backup data stored on a cloud-based object storage irrespective of the storage provider. The system may include a server (or gateway) that provides a backup service, and acts as an intermediary between a client device and object storage. To provide such capabilities, the system may manage an application programming interface (API) that provides a uniform set of methods to a client device irrespective of the destination object storage provider. A function library may include provider-specific functions that invoke corresponding storage-layer operations provided by the destination object storage. The server may also manage an operation pool to schedule operations and saturate bandwidth to the object storage. The server may also implement a specialized metadata database to provide further storage efficiencies by storing certain backup data exclusively within the metadata database.

Provider-agnostic management of backup data stored on a cloud-based object storage

Described is a system (and method) for providing multiple types of granular delete operations for a cloud-based object storage. The system may include a server that acts as an intermediary between a client device and an object storage that stores client data. The server may allow a client to perform a hard delete (or permanent) delete and a soft delete. The server may perform a specialized processing to synthetically create the soft delete feature using a permanent object delete operation provided by the object storage. The specialized processing may include manipulating retention periods associated with objects depending on whether the object is subject to a hard delete or a soft delete. As a result, the server may provide the ability for clients to perform a soft delete at an object level using existing storage level APIs that do not directly support such a feature.

Synthetically providing multiple types of granular delete operations for a cloud-based object storage

Described is a system for synchronizing expiration times for incremental backup data stored on a cloud-based object storage. More particularly, the system may provide a layer of intelligence when updating the expiration times associated with backup data to ensure that a full recovery of the client data to a point-in-time of any incremental backup may be performed. To provide such a capability, the system may maintain specialized metadata identifying expiration times for objects and a list of objects required to perform a full recovery to a point-in-time for each of the performed backups (e.g. full or incremental). The system may access this metadata to identify which objects stored by a previous backup are still referenced by a subsequent backup. Based on the identified objects, the system may synchronize object expiration times to ensure objects are not prematurely deleted from the object storage.

Synchronizing expirations for incremental backup data stored on a cloud-based object storage

Described is a system for rule-based re-tiering of backup data stored on a cloud-based object storage. More specifically, the system may re-tier objects based on one or more storage rules such that the system retains the ability to efficiently perform a full restore of backup data even when incremental backups are performed to a cloud-based object storage. To provide such a capability, the system may maintain a specialized metadata database that stores information indicating the backup time for each backup, and a list of objects required to perform a full restore to each of the backup times. Accordingly, when initiating a re-tiering based on one or more storage rules, the system may intelligently select candidate objects for re-tiering by leveraging the metadata database to ensure that objects that may still need to be referenced are not unnecessarily moved to a lower storage tier.

Rule-based re-tiering of incremental backup data stored on a cloud-based object storage

Described is a system for intelligent re-tiering of backup data stored on a cloud-based object storage. More specifically, the system may re-tier objects such that the system retains the ability to efficiently perform a full restore of backup data even when incremental backups are performed to a cloud-based object storage. To provide such a capability, the system may maintain a specialized metadata database that stores information indicating the backup time for each backup, and a list of objects required to perform a full restore to each of the backup times. Accordingly, when using a threshold time (e.g. expiry) to select object candidates for re-tiering, the system may leverage the metadata database to ensure that objects that may still need to be referenced are not unnecessarily moved to a lower storage tier.

Intelligent re-tiering of incremental backup data stored on a cloud-based object storage

A system including persistent storage for storing an object repository and a user data backup. The system also includes a manager that obtains fragmented user data associated with an object that is potentially duplicative of an object stored in the object repository; makes a determination that the object is duplicative based on a copy of the object stored in the object repository; in response to making the determination, adds the fragmented user data to a user data backup without adding the object to the backup; associates the fragmented user data in the user data backup with the copy of the object stored in the object repository; and stores the user data backup in the persistent storage.

Method and system for indexing fragmented user data objects

A system for providing backup services for limited-access user data includes persistent storage for storing a user data visualization enhanced user data backup and a manager. The manager identifies a backup generation event for limited-access user data based on a protection policy; in response to identifying the backup generation event, obtains fragmented user data from an application that gates access to the limited-access user data; obtains organizational metadata associated with the fragmented user data from the application; makes a determination that the fragmented user data is associated with a user data visualization; in response to making the determination, obtains user data visualization metadata associated with the fragmented user data from the application; and generates the user data enhanced user data backup using the organizational metadata, the user data visualization metadata, and the fragmented user data.

Method and system for generating user data visualization enhanced user data backups of limited-access user data

A method and system for asset protection threat detection and mitigation using interactive graphics. Specifically, the disclosed method and system entail discerning protection vulnerabilities exhibited by assets (or databases) based on maintained backup metadata. These protection vulnerabilities may subsequently be visualized as part of a projected graphical user interface, which may not only disclose the protection vulnerabilities to a user but also may enable the user to rectify the disclosed protection vulnerabilities through on-demand asset backup operations.

Method and system for asset protection threat detection and mitigation using interactive graphics

A system for providing data protection services for user data generated by an application, includes persistent storage for storing user data backups and a manager. The manager is programmed to identify a backup generation event for user data based on a protection policy, in response to identifying the backup generation event, obtain user data associated with the backup generation event from the application, select a calendar of calendars included in the user data, obtain user metadata associated with the calendar, and generate a user data backup using the user data and the user metadata, in which the user data backup comprises calendar events of the calendar and portions of the user metadata associated with the calendar events.

Method and system for performing data protection services for user data associated with calendar events

A system for providing data protection services for user data associated with calendar groups generated by an application includes persistent storage for storing user data backups and a manager. The manager is programmed to identify a backup generation event for the user data associated with a calendar group based on a protection policy, obtain user data associated with the backup generation event from the application in response to identifying the backup generation event, select a calendar of calendars included in the user data, obtain user metadata associated with the calendar, generate calendar group information associated with the calendar using the user data and the user metadata, generate a user data backup using the user data, the calendar group information, and the user metadata, in which the user data backup comprises backup data and backup metadata.

Method and system for performing data protection services for user data associated with calendar groups

A system for providing data protection services for user data generated by an application includes persistent storage that includes an archive storage and a backup storage. The system also includes a manager. The manager is programmed to generate data chunks using user data, generate backup object metadata associated with the data chunks; obtain previously generated backup object metadata associated with the user data using an archive value, make a first determination that at least one data chunk of the data chunks is to be archived using the backup object metadata and the previously generated backup object metadata, and, in response to the first determination: store the at least one data chunk in the archive storage as a portion of a user data backup, and store remaining data chunks of the data chunks in the backup storage as the remaining portion of the user data backup.

Method and system for archiving user data during backup generation

In some embodiments, described is a system (and method) for providing an efficient preview capability for emails backed up to a cloud-based object storage. The email preview may be provided as part of an interface allowing a user to select individual emails to restore from the object storage. The system may extract specialized preview information as part of a backup procedure. The preview information may include metadata and email content. For example, the preview information may include various email details such as sender, receiver, subject line, time sent/received, filenames of any attachments, etc. The preview information may also include email content such as particular sentences from the email body containing keywords. The system may also store extracted preview information in a specialized manner such that the preview information may be retrieved without having to access the actual backup data.

Providing an efficient preview capability for restoring emails backed up to an object storage

Described is a system (and method) for managing specialized metadata that may be used to manage and search incremental backup data stored on a cloud-based object storage. The system may create and store such metadata as part of a specialized metadata database that includes a data catalog and a backup catalog. The system may leverage the metadata database to initiate operations to efficiently manage incremental backup data stored on the object storage. For example, the metadata may be relied upon to efficiently reconstruct (e.g. synthetically) the client data to a point-in-time of any incremental backup. In addition, the metadata may include properties of the backed-up data, which are maintained separately from the backup data stored as objects. Accordingly, these properties may be searched to identify and locate backup data without having to retrieve the stored objects.

Growing community of inventors

Bengaluru, India

Deependra Pratap Singh