Emc IP Holding Company LLC

Emc Corporation

Cohesity, Inc.

Suman Chandra Tokuri

Sunil Kumar Yadav

Soumen Acharya

Aaditya Rakesh Bansal

Sudha Hebsur

Pradeep Anappa

Vladimir Mandic

Upanshu Singhal

Matthew Dickey Buchman

Poornima Ramu

Tushar Dethe

Anupam Chakraborty

Abhijit Chakankar

Bala Vijayakumar

Prajakta Balkrishna Ayachit

Prashant Gothi

Anappa Pradeep

Dominic Tu Ping Cheah

Sai Madan Mohan Reddy Patlolla

Shelesh Chopra

Manish Sharma

Aditya Kapoor

Gajendran Raghunathan

Nikhil Ambastha

Hareej G Hebbur

Ramachandran Srinivasan

Elango Chokalingam

Ramachandaran Srinivasan

A request to restore an instance of an object that is stored in a storage associated with a cluster of nodes to a target destination is received. Data of the object is divided into a plurality of data portions. Corresponding data portions of the plurality of data portions are assigned to each node of a plurality of nodes of the cluster. It is determined that a first node of the cluster of nodes does not currently store in a storage associated with the first node at least a part of a corresponding data portion of the object assigned to the first node. At least the part of the corresponding data portion of the object assigned to the first node is received at the first node from a second node of the cluster of nodes. At least the part of the corresponding data portion of the object received from the second node is provided from the first node to the target destination.

Parallel restore of a large object

In one example, a method includes receiving, at a physical proxy node, a backup request from a client outside the cluster environment, the backup request identifies a VM that is to be backed up, and including data that resides on a virtual federated database that is an element of the cluster environment and to which respective databases of each node of the cluster environment are mapped, and the backup request is received at the physical proxy node due to the position of the physical proxy node in a PSOL. Next, initiating, with an agent at the physical proxy node, a save program on the physical proxy node, and initiating, with the save program, a secondary save process on the physical proxy node that is a federated backup process and includes reading the VM identification from the backup request, and backing up the VM identified in the backup request.

Proxy based backup and restore of hyper-v cluster shared volumes (CSV)

In one example, a method includes obtaining cluster and machine configuration information, sending a restore request for one or more machines, and loading a backup of a virtual machine, the backup having been created by a federated backup process involving the physical proxy node, and the virtual machine includes data that resides on a virtual federated database that is an element of a cluster environment and to which respective databases of each of a plurality of nodes of the cluster environment are mapped. Next, the virtual machine is taken offline after the backup of the virtual machine has been loaded, and after the virtual machine has been taken offline, the virtual machine is removed from the node where it resides. The backup of the virtual machine is then restored, and the restored virtual machine brought online, after which the restored virtual machine is enabled as a cluster-wide virtual machine.

Proxy based backup and restore of Hyper-V cluster shared volumes (CSV)

Embodiments for a method of backing up virtual hard disks by: parsing a list of base parent and differencing disks to identify disk parameters and child disks of immediate parent disks; creating a differencing disk chain in reverse time order of modification of the base parent disk starting from the base parent disk to a latest child differencing disk; identifying changed sectors in each child disk starting from the latest child differencing disk; creating a list detailing a respective differencing disk, sector offsets and logical data sector index for each changed sector; iteratively adding updated sectors to the list for latest changed sectors that were not previously added to the list by a later child disk by reading the changed sectors from their respective child disk; and merging, in a single step, the changed sectors read from their respective child disks into the base parent disk.

Single step merging of a virtual hard disk chain

A unified backup workflow process for different hypervisor configurations of virtual machines on different storage of a cluster leverages RCT-based backup functionality so that backup operations can be performed by a single host of the cluster. The process enables backing up together virtual machines that are local, as well as part of CSV or SMB storage using virtual machine level snapshots as checkpoints rather than volume level snapshots that were traditionally used. Backup data is sent to a backup server as a data stream rather than a file, which avoids the necessity of maintaining chains or structures that identify parent-child disks on the server.

Unified RCT backup for different hypervisor configurations

A virtual machine backup process where a plurality of types of snapshots of the virtual machine coexist includes: obtaining a list of files comprising virtual hard disks and differencing virtual hard disks associated with the virtual machine; sorting the list of files to identify relationships and to generate a current tree in which differencing virtual hard disks point to corresponding parent virtual hard disks; comparing the current tree with a previous tree associated with the virtual machine from the last backup of the virtual machine; identifying differencing virtual hard disks in the current tree that are not present in the previous tree as incremental backup data; and backing up the incremental data. The incremental data is merged with a previous synthetic full backup of the virtual machine to generate a new synthetic full backup of the virtual machine.

Hyper-V virtual machine synthetic full backup where user and recovery snapshots coexist

In one example, a method for data protection in a cluster environment includes identifying data in the cluster environment that is to be backed up, where the identified data includes data that resides on a shared disk of the cluster environment. Next, a physical proxy node, from which a backup of the identified data will be performed, is selected. The selected physical proxy node is in the cluster environment. A federated backup of the identified data is then performed from the physical proxy node and generates a backup. The backup is then stored for later restoration to a node of the cluster environment.

Proxy-based backup and restore of hyper-V cluster shared volumes (CSV)

A remote backup agent that provides data storage services to virtual machines includes a persistent storage and a processor. The persistent storage stores workflows for the virtual machines. The processor performs a first remote backup of the virtual machines based on the workflows using production agents hosted by production hosts that also host the virtual machines; obtains a workflow update; updates the workflows based on the workflow update to obtain updated workflows; and performs a second remote backup of the virtual machines based on the updated workflows using the production hosts without modifying the production agents.

System and method for backup in a virtualized environment

According to one embodiment, a system in response to a request to back up a virtual machine (VM) to a backup storage system, retrieves history data from the backup storage system. The history data has been previously backed up in the backup storage system during a previous backup operation of the VM. The history data includes a change tracking identifier (ID) associated with a consistent state of a VM disk attached to the VM at the point-in-time of the previous backup operation. The system validates the history data against a current configuration of the VM. The current configuration includes information of one or more current consistent states of the VM disk. The system determines a backup type for each of the current consistent states based on the validated history data. The system backs up each of the current consistent states based on the backup type.

Virtual machine backup with efficient checkpoint handling based on a consistent state of the virtual machine of history data and a backup type of a current consistent state of the virtual machine

Embodiments described herein provide for a system and associated logic to enable browsing of a federated backup having a plurality of portions, each portion separately generated and indexed by a plurality of nodes. In one embodiment, the system performs a federated backup by generating a unique identifier on a primary node and providing the unique identifier to each secondary node tasked with generating the plurality of portions. The secondary nodes associate the unique identifier with each of the plurality of portions. The unique identifier can then be used by a recovery UI to generate and display a consolidated view of the plurality of portions.

Browsing federated backups

A method and system for implementing data lossless synthetic full backups. Specifically, the method and system disclosed herein improves upon traditional synthetic full backup operations by considering all user-checkpoint branches, rather than just the active user-checkpoint branch, representing all chains of incremental changes to a virtual disk of a virtual machine. In considering all user-checkpoint branches, no data pertinent to users involved in the development of the non-active (or inactive) user-checkpoint branches is lost.

Method and system for implementing data lossless synthetic full backups

A backup and recovery architecture for applications compatible with the Microsoft Windows Volume Shadow Copy Service (VSS) includes a backup client module that includes an orchestration engine, an application manager, a common requestor, and a save transports component. The client module interacts with the VSS on the client in the generation of a shadow copy. Data is backed up from the shadow copy to a backup storage server. In various specific embodiments, the application manager includes functions that are application-specific and the orchestration engine includes functions that are not application-specific. A single consolidated log may be generated by the backup client module for a backup or recover operation.

Extensible workflow manager for backing up and recovering microsoft shadow copy compatible applications

An incremental backup of a database includes issuing a request to a copy service requesting a snapshot of a volume having the database, and identifying a writer of the database that should participate in creating the snapshot. From the snapshot, changes to the database since a last backup of the database and log files associated with the database that include data not yet committed to the database, are transmitted to a backup storage unit.

Incremental forever backups for exchange

A first cluster node receives a request for a backup of files stored in a CSV shared with a second cluster node. A first VSS writer determines a first set of files associated with the first cluster node. A second VSS writer determines a second set of files associated with the second cluster node. A WMD file associated with the backup is generated to include a first component describing the first set of files and a second component describing the second set of files. A BCD file associated with the backup is modified to store information indicating the first VSS writer to restore the first and second sets of files, such that the first and second sets of files can be restored using the first VSS writer without having to use the second VSS writer. The backup is then performed to a backup storage device.

Growing community of inventors

Bengaluru, India

Suman Chandra Tokuri