Cohesity, Inc.

Vmware, Inc.

Rupesh Bajaj

Sunil Moolchandani

Vivek Velankar

Sandeep Tandekar

Edward Joseph Goggin

Hariharan Subramanian

Vibhor Arunkumar Patale

Apollo Aguilan Tanting

Aditya Tandon

Apurv Gupta

Anand Arun

Abhijit Chakankar

Markose Thomas

Manoj Singhal

Sashikanth Madduri

Zheng Cai

Warren Shen

Amandeep Gautam

Himanshu Mehra

Debasish Garai

Vairavanathan Emalayan

Chinmaya Manjunath

Igor Korsunsky

Prajakta Balkrishna Ayachit

Mukul Sharma

Rajiv Madampath

Sanjana Aswani

Janga Varun

Abhishek Bagchi

Satbir Singh Bhatti

Jitender Rohilla

Properties of one or more databases of nodes of a database system are automatically discovered. The automatically discovered properties for at least one of the databases include a database architecture and a corresponding failover role for each of at least some of the nodes. Based at least in part on the discovered properties, a corresponding one of the nodes as a corresponding backup source node is selected for each of the one or more databases. One or more database backups are allowed to be performed via the one or more selected backup source nodes.

Performing a database backup based on automatically discovered properties

An identification of a new primary snapshot created for a primary storage system is received. A change tracking time window that is at least a portion of a period between a first capture time associated with a previous primary snapshot and a second capture time associated with the new primary snapshot is determined. Entries of a storage log of the primary storage system occurring within the change tracking time window are analyzed to coalesce changes identified in the entries of the storage log occurring within the change tracking time window into a change tracking result set. The change tracking result set is used to identify at least a portion of data changes between the previous primary snapshot and the new primary snapshot to capture in a new backup snapshot stored at a secondary storage system.

Coalescing storage log entries

An identification of a new primary snapshot created for a primary storage system is received. A threshold time window based on a capture time associated with the new primary snapshot is determined. Entries of a storage log of the primary storage system occurring within the threshold time window are analyzed to identify any objects of the primary storage system that have changed during the threshold time window. Changed objects to capture in a new secondary backup stored at a secondary storage system and corresponding to the new primary snapshot are identified. Metadata of the new primary snapshot and metadata of a previous secondary backup are compared to determine for each of the objects of the primary storage system identified as having changed during the threshold time window whether a change to an object since the previous secondary backup is captured in the new primary snapshot.

Using a storage log to generate an incremental backup

A request to restore a primary system to a backed-up state of the primary system that is associated with a particular point in time is received at a storage system. The backed-up state of the primary system corresponds to a particular backup snapshot. The primary system is determined to be corrupted less than a threshold amount of corruption. An indication of a first set of changes that includes one or more changes to the primary system that have occurred since a last backup snapshot is received. A second set of changes that includes one or more changes between the particular backup snapshot and the last backup snapshot is determined. It is determined, based in part on the indication of the first set of changes, which data associated with the second set of changes to provide to the primary system. The determined data is provided to the primary system.

Fast and optimized restore using delta information

A technique for restoring content is described. The technique includes receiving a specification of content to be restored to a target storage from a data source. The technique also includes determining task units to be performed to restore the specified content. Each task unit is associated with a corresponding assigned weight value. Based on the corresponding assigned weight values, the task units are distributed to different task groups. The task groups are processed in parallel with each other to concurrently perform at least a portion of the distributed task units.

Efficient restoration of content

An indication of one or more changes to file system data since a last backup snapshot is received. One or more changes to the file system data between a requested backup version and the last backup snapshot are determined based in part on differences between a first tree data structure corresponding to the requested backup version and a second tree data structure corresponding to the last backup snapshot. The differences correspond to the one or more changes to the file system data between the requested backup version and the last backup snapshot. One or more data blocks corresponding to the one or more changes to the file system data since the last backup snapshot and one or more data blocks corresponding to the one or more changes to file system data between the requested backup version and the last backup snapshot are provided to a primary system.

A request associated with restoring a previous version of a linked clone virtual machine is received. One or more changes between a base image of a parent virtual machine and the previous version of the linked clone virtual machine are determined. One or more data blocks corresponding to the base image and one or more data blocks corresponding to the determined changes are provided to a remote system.

Backup and restore of linked clone VM

A request to migrate from a secondary storage system to a server a requested version of database content of a database backed up at the secondary storage system is received. A new version of the database content at the secondary storage system is instantiated. Functionality of the database is maintained including by allowing a database application hosted on the server to access the database content from the secondary storage system using the instantiated new version of the database content while migrating the requested version of database content from the secondary storage system to the server.

Using a secondary storage system to maintain functionality of a database during database migration

A method and system for restoring a database are described. An identification of a restoration point of the database is received. Using a processor, metadata of a plurality of backups are analyzed to identify from the plurality of backups a reduced dataset required to restore the database to the restoration point. The reduced dataset is provided for use in restoring the database to the restoration point.

Point-in-time database restoration using a reduced dataset

A method and system for migrating data are described. A storage capture instance in a first format from a first type of device is received. Processing utilized to back up the storage capture instance to a second format of a snapshot tree is distributed to multiple storage nodes. A request to migrate at least part of the storage capture instance to a second type of device in a third format is received. In response to the request, processing utilized to migrate the at least part of the storage capture instance from the second format to the second type of device in the third format is distributed to the storage nodes. In one aspect, file(s) in a first network attached storage (NAS) device format are migrated to a second NAS device format. In another aspect, a virtual machine (VM) and/or file(s) therein having a first VM format are migrated to a second VM format.

Multi-format migration for network attached storage devices and virtual machines

Growing community of inventors

Dewas, India

Rupesh Bajaj