Emc IP Holding Company LLC

Dell Products Inc.

Dell & Products L.p.

Amarendra Behera

Shelesh Chopra

Sunil Kumar Yadav

Tushar Dethe

Himanshu Arora

Jigar Premajibhai Bhanushali

Deependra Pratap Singh

Ravi Vijayakumar Chitloor

Sapna Chauhan

Prabhat Kumar Dubey

Gururaj Soma

Krishnendu Bagchi

Anjana Rao

Elango Chockalingam

Anupam Chakraborty

Manjesh Venkatanarayana Chikkanayakanahally

Vipin Kumar Kaushal

Sudha Hebsur

Ken Owens

Pallavi Prakash

Jayashree Radha

Vipin Kaushal

Ashish Kumar

Soumen Acharya

Amith Ramachandran

Asif Khan

Yasemin Ugur-Ozekinci

Sunder Ramesh Andra

Nikhil Ambastha

Reshmee Jawed

Pati Mohan

Deepika Nagabushanam

PrabhatKumar Dubey

Navneet Upadhyay

Shraddha Chunekar

Pradeep Anappa

Hareej G Hebbur

Roland Fernandes

Sonali Sengupta

Upanshu Singhal

Aaditya Rakesh Bansal

Matthew Dickey Buchman

Jerzy Gruszka

Aditya Kapoor

Nitin Anand

Aneesh Kumar Gurindapalli

Challa Dharmateja

Michael Jones

Yagnavalkya Chennojwala

Prashant Shukla

Arun Chakravarthy

Sekhar Samala

DharmaTeja Challa

Kanagasabapathy Venkatachalam

Deepak Anantha Bellare Mallya

Sanjna Umesh

Abhinash Kumar

Mahesh Biradar

Sunil Yadav

A method for managing data protection includes initiating, by a backup server, discovery for a new virtual machine (VM) in a production environment, performing, using an active directory listener (AD), listening on active directory (AD) applications in the production environment, wherein the new VM executes one of the AD applications, and wherein the one of the AD applications comprises a set of AD objects and a directory service for managing the set of AD objects, storing, based on the listening, monitored changes to obtain stored changes in the AD applications, generating a change report based on the stored changes, and using the change report to perform an incremental backup of the new VM and store a VM backup of the new VM and an AD application backup of the one of the AD applications in a backup storage system.

Active directory data protection by leveraging virtual machine backup with change notification-based active directory backup

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

A method for managing data protection includes initiating, by a backup server, identifying an active directory (AD) application on the VM, wherein the AD application comprises a set of AD objects and a directory service for managing the set of AD objects, in response to identifying the AD application, installing a new AD listener in the production environment, performing listening on the AD application in the production environment to detect changes to the set of AD objects, monitoring, by the backup server, generating a VM backup of the VM and an AD application backup of the AD application, and storing the VM backup and the AD application backup in a backup storage system, based on the VM backup generation, and based on the listening, performing a backup schedule analysis on the backup schedule, and based on the backup schedule analysis, performing a backup schedule modification on the backup schedule.

Active directory object observability for backup policy management in a production environment

Detecting the most recent state of an active directory object and recovering using backups or production tombstones

System selects application hosts which meet update requirements, then downloads update for instances of application agent corresponding to selected application hosts. System puts selected application hosts in maintenance mode, which prevents selected application hosts from beginning execution of any operations, until updating selected application hosts is completed. System creates backup copy of state of instances of application agent. System generates installation instructions that, when executed by update sessions to install update, enable roll back from updated instances of application agent to state of instances of application agent recorded in backup copy. System initiates update sessions which install update in instances of application agent corresponding to selected application hosts. If update sessions failed to install update in any instances of application agent in cluster of application hosts, system rolls back update for updated instances of application agents in cluster to previous conditions and configurations of instances of application agents.

Generating installation software that rolls back agent updates when cluster updates fail

System enables selection of application hosts which meet update requirements, then downloads update for instances of application agent corresponding to selected application hosts. System puts selected application hosts in maintenance mode, which prevents selected application hosts from beginning execution of any operations, until updating selected application hosts is completed. System creates copy of instructions, which when executed, installs update in instance of application agent in one of application hosts, and reports on update process to server which communicates with application hosts. System launches worker process from copy of instructions. System initiates update sessions which install update in instances of application agent corresponding to selected application hosts. If update sessions failed to install update in any of instances of application agent in cluster of application hosts, system rolls back update for updated instances of application agents in cluster of application hosts to previous conditions of instances of application agents.

Launching copies of installation software that rolls back agent updates when cluster updates fail

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

Agent lifecycle management for backup and restore applications is described. A system enables selection of application hosts, each of which meets installation requirements for installing instances of application agents from a backup and restore application, then downloads, in parallel, the instances of the application agent to the corresponding selected application hosts. The system installs, in parallel, the instances of the application agent in the corresponding selected application hosts, then registers, in parallel, the instances of the application agent with the backup and restore application. The system subsequently initiates sessions which download and install, in parallel, an update in instances of the application agent in in corresponding application hosts. The system unregisters at least one of the instances of the application agent, in at least one application host, from the backup and restore application. The system decommissions the at least one application host from protection by the backup and restore application.

Agent lifecycle management for backup and restore applications

A data protection agent is installed within a virtual machine (VM). A request to perform a backup is received. The request includes identifications of virtual machine disks (VMDKs) associated with the virtual machine. Communications are exchanged with a disk manager of a guest operating system of the VM to generate a map that maps the VMDKs to volumes attached to the VM. Communications are exchanged with an application in the VM to be protected to identify which of the volumes contain application databases associated with the application. A copy service is instructed to prepare the application for backup. A request is issued to a snapshot data mover for a snapshot of the application. The snapshot request includes identifications of a subset of the VMDKs mapped to corresponding volumes that contain the application databases. VMDKs mapped to corresponding volumes not containing the application databases are excluded from the snapshot request.

System and method to exclude unsupported disks during application consistent backups

Automatically updating agents from backup and restore applications is described. A system enables selection of application hosts which meet update requirements, then downloads an update for instances of an application agent corresponding to selected application hosts. The system puts selected application hosts in maintenance mode, which prevents selected application hosts from beginning execution of any operations, until updating selected application hosts is completed. The system initiates update sessions which install update in instances of application agent corresponding to selected application hosts. If update sessions did not fail to install update in any of instances of application agent in cluster of application hosts, then the system stores the updated instances of the application agents in a non-volatile storage.

Automatically updating agents from backup and restore applications

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

A data protection agent is installed within a virtual machine (VM). A request to freeze an application in the VM is issued to a copy service. A request for a snapshot is issued to a snapshot data mover, external to the VM. Upon receiving an identifier for the snapshot, communications are exchanged with the copy service to thaw the application, the snapshot identifier is passed to the agent thereby allowing the agent to access the snapshot and rollover data from the snapshot to secondary storage for the backup, and notification to the copy service about a success of the backup is withheld. During the rollover, listening begins for status updates concerning a progress of the rollover. Based on the status updates, the copy service is notified that the backup failed or succeeded.

System and method for avoiding unwanted log truncation (data loss) during application consistent virtual machine snapshots

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

Growing community of inventors

Bengaluru, India

Amarendra Behera