Cohesity, Inc.

Manoj Singhal

Abhijit Chakankar

Warren Shen

Sashikanth Madduri

Anubhav Gupta

Rupesh Bajaj

Sunil Moolchandani

Vivek Velankar

Sandeep Tandekar

Apollo Aguilan Tanting

Aditya Tandon

Prashant Gothi

A request to restore a database to a particular point in time is received. It is determined that a closest preceding backup to the particular point in time is an incremental backup. One or more transaction log file segments needed to restore the database to the particular point in time are determined. An updated incremental backup is generated by applying the one or more determined transaction log file segments to the incremental backup. The updated incremental backup is restored to a primary system.

Restoring a database using a fully hydrated backup

Data chunks sent to a content destination are tracked. It is determined whether content of a portion of an object to be sent to the content destination matches one of the data chunks previously sent to the content destination. In response to the determination that the portion of the object to be sent to the content destination matches one of the data chunks previously sent to the content destination, a source reference to the matching previously sent data chunk where the content destination can locally obtain the content for the portion of the object is provided to the content destination.

Reducing the impact of network latency during a restore operation

A backup of a database is determined to be performed. A backup of at least a portion of contents of a storage volume that includes data of the database is performed. The backup includes a step of creating a new metadata tree root node. Creating the new metadata tree root node includes copying from another metadata tree root node of a tree data structure corresponding to a previous backup instance, one or more references to one or more lower tier metadata tree nodes associated with the tree data structure corresponding to the previous backup instance.

A portion of contents of a database is received from a first server. The received contents of the database is stored in a secondary storage system that tracks changes between different backup versions of contents of the database. A request to migrate the contents of the database to a second server is received. A version of contents of the database is provided to the second server using the secondary storage system. The secondary storage system is configured to determine an amount of changes to the database content from one of the versions of the database content provided to the second server and the amount of changes is utilized in determining whether to quiesce the database hosted on the first server.

Efficient database migration using an intermediary secondary storage system

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.

Growing community of inventors

Sunnyvale, CA, United States of America

Manoj Singhal