Emc IP Holding Company LLC

Dell Products Inc.

Tushar Dethe

Sunil Kumar Yadav

Amarendra Behera

Shelesh Chopra

Himanshu Arora

Anupam Chakraborty

Deependra Pratap Singh

Ravi Vijayakumar Chitloor

Jigar Premajibhai Bhanushali

Soumen Acharya

Sapna Chauhan

Prabhat Kumar Dubey

Gururaj Soma

Anjana Rao

Shubhashish Mallik

Asif Khan

Vipin Kumar Kaushal

Aaditya Rakesh Bansal

Ashish Kumar

Krishnendu Bagchi

Amith Ramachandran

Yasemin Ugur-Ozekinci

Reshmee Jawed

Pati Mohan

PrabhatKumar Dubey

Deepika Nagabushanam

Navneet Upadhyay

Suman Chandra Tokuri

Shraddha Chunekar

Pradeep Anappa

Satyendra Nath Sharma

Roland Fernandes

Vladimir Mandic

Upanshu Singhal

Matthew Dickey Buchman

Mahesh Reddy Appireddygari Venkataramana

Swaroop Shankar D H

Swaroop Shankar Dh

Manjesh Venkatanarayana Chikkanayakanahally

Aditya Kapoor

Nitin Anand

Deepthi Urs

Sainath Gonugunta

Lakshminarayanan Muniswamy

Mahesh Reddy Av

Arun Chakravarthy

Kanagasabapathy Venkatachalam

Deepak Anantha Bellare Mallya

DharmaTeja Challa

Subhashish Mallik

Sanjna Umesh

Techniques described herein relate to a method for performing data protection services for limited access cloud data. The method includes obtaining, by a data manager, an initial cloud service provider (CSP) proxy generation request from a user; in response to obtaining the initial (CSP) proxy generation request: creating an authentication account in a CSP directory based on the initial CSP proxy generation request; instantiating a CSP proxy in an on-premises CSP using authentication information associated with the authentication account; storing the authentication information; and associating the user with the authentication information and the CSP proxy, wherein after the associating the CSP proxy can access limited access cloud data and cloud resources of the on-premises CSP.

Method and system for performing authentication and object discovery for on-premises cloud service providers

Techniques described herein relate to a method for performing data protection services for limited access cloud data. The method includes identifying, by a cloud service provider (CSP) proxy, a protection policy event associated with an incremental approximation backup of an object; in response to identifying the protection policy event: obtaining previous object metadata associated with the object; obtaining object data from on-premises cloud resources associated with the object; generating slices of the object data; generating current checksums and current object metadata associated with each slice; selecting a first slice of the slices; making a first determination that a first current checksum of the current checksums and a first previous checksum associated with the first slice do not match; in response to the first determination: storing the first slice in a backup storage; and updating a first portion of the current object metadata associated with the first slice.

Method and system for generating incremental approximation backups of limited access cloud data

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

Communications are exchanged with a copy service of a host to identify writers associated with the copy service. The identification includes a type of a writer as being a system or application writer. Writers identified as system writers are added to a list of writers that should participate in a backup operation. For writers identified as application writers, components of an application writer are iterated through to determine whether a component of the application writer has a name or logical path that includes a name of a system service. When any component has the name or logical path that includes the name of the system service, the application writer is promoted to be of type system writer by adding the application writer to the list of writers that should participate in the backup operation. Components of each writer listed in the list of writers are backed up.

Dynamic promotion of user data components to system writer components

A registry writer is instructed via a copy service on a host to prepare for generation of a snapshot. The registry writer is responsible for saving system hive files to disk before the snapshot is generated. A reporting of the system hive files is received from the registry writer. Communications are exchanged with an API exposed by an operating system of the host to identify user hive files. The system hive files reported by the registry writer and the user hive files identified using the API exposed by the operating system are backed up from the snapshot to secondary storage.

Hybrid technique to protect a registry

Writers on a host and associated with a copy service are identified. The identification includes names of the writers and writer types as being system or application writers. For each writer identified as a system writer, a size of the system writer is calculated and a check is made as to whether a volume associated with the system writer includes system data. When the volume include system data, the volume is marked as a critical volume and a size of the critical volume is obtained. A tally is maintained summing the sizes of the system writer and critical volume.

Disaster recovery (DR) asset sizing for front end terabyte (FETB) consumption

A data structure is generated to store information about a set of writers associated with a copy service. The information is gathered from the copy service and populated into the data structure. The information includes names of the writers, writer types as being system or application writers, and system writer subtypes as being one of bare metal recovery (BMR) writers or system state recovery (SSR) writers. The data structure is reviewed to determine whether a particular writer should participate in the backup. Based on the review, a list is generated including a subset of the participating writers. Instructions are issued, via the copy service, for the writers in the list to prepare for creation of a snapshot. Upon creation of the snapshot, data is backed up from the snapshot to secondary storage.

Dynamic backup and discovery of new writers of a copy service

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

A target host is booted into a preinstallation environment. A request to register as a recovery agent is issued from a REST API of the target host to a backup management server. A TLS certificate to establish a secure channel is received from the backup management server. A request identifying a backup copy to be stored on the target host is issued from the REST API of the target host and over the secure channel to the backup management server. Credentials required to access a backup storage at which the backup copy is stored is received. Using the credentials, the backup copy is retrieved from the backup storage.

Memory simulation of agent service for secured restore

Network configuration details associated with a host are collected with each bare metal recovery (BMR) backup of the host. The network configuration details are stored in backup storage with each BMR backup copy. A target host is booted into a preinstallation environment. The target host is configured into a DHCP mode to allow the target host to establish a network connection to a backup management server. Details about the host are received from a user. A listing of BMR backup copies corresponding to the host details are retrieved from the backup management server. A selection of a BMR backup copy to be restored onto the target host is received. Network configuration details corresponding to the selected BMR backup copy are downloaded from backup storage. A recovery wizard at the target host is populated with the network configuration details.

Automatically populating network configuration of a host during a bare metal recovery (BMR) restore

Writers participating in a backup are identified. A mapping is generated between the writers and associated files. The mapping includes file properties. The mapping is initialized by tagging the writers with a full backup tag. A base backup copy of the writers is created by conducting a full backup of each writer tagged with the full backup tag. At a current backup operation after creating the base backup, a list of current files that will participate in the current backup operation is generated. The list of current files is compared against the files in the mapping to determine whether a particular writer associated with a current file should be tagged with the full backup tag or an incremental backup tag. The particular writer is tagged with the incremental backup tag when file properties associated with the current file have changed.

Tagging writers for incremental backups of system objects

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

Growing community of inventors

Bengaluru, India

Tushar Dethe