Cohesity, Inc.

Chinmaya Manjunath

Shobhit Agarwal

Kishan Venkata Sravan Nerella

Markose Thomas

Anubhav Gupta

Zhihuan Qiu

Anirvan Duttagupta

Karandeep Singh Chawla

Colin Scott Johnson

Manvendra Singh Tomar

Sidharth Mishra

Shubham Arvind Barai

Amitabh Sinha

Himanshu Mehra

Dayanand Sharma

Prakash Veljibhai Vaghela

Ashish Patwardhan

Rupesh Bajaj

Anand Arun

Zheng Cai

A stream of data changes to content of an object associated with a source system is received. A hot standby version of at least a portion of the object maintained at a recovery system is updated by streaming the received stream of data changes to the recovery system. It is determined that a gap exists in the stream of data changes. In response to determining that the gap exists in the stream of data changes, a reference snapshot is requested from the source system. A current state of the hot standby version of at least the portion of the object maintained at the recovery system is caused to be updated to a state of the portion of the object associated with the reference snapshot.

Standbys for continuous data protection-enabled objects

A current configuration of one or more data management services is monitored. It is determined that the current configuration is insufficient to achieve a data protection intent indicated by a specification of the data protection intent. In response to determining that the current configuration is insufficient to achieve the data protection intent indicated by the specification of the data protection intent, the current configuration of the one or more data management services is modified in a manner to achieve the data protection intent indicated by the specification of the data protection intent.

Automatically implementing a specification of a data protection intent

A remote data recovery system is determined to be unsuitable for communications. A stream of source system storage changes associated with an object is received at a backup system from a source system while the remote data recovery system is unsuitable for communications. The backup system is utilized to generate one or more reference restoration points based on the stream of source system storage changes associated with the object. The remote data recovery system is determined to be suitable for communications. In response to determining that the remote data recovery system is suitable for communications, a hot standby of the object hosted by the remote data recovery system is updated to a reference restoration point generated by the backup system prior to the remote data recovery system becoming suitable for communications.

Using a stream of source system storage changes to update a continuous data protection-enabled hot standby

A reference snapshot of a storage is stored. Data changes that modify the storage are received. The data changes are captured by a write filter of the storage. The received data changes are logged. The data changes occurring after an instance time of the reference snapshot are applied to the reference snapshot to generate a first incremental snapshot corresponding to a first intermediate reference restoration point. The data changes occurring after an instance time of the first incremental snapshot are applied to the first incremental snapshot to generate a second incremental snapshot corresponding to a second intermediate reference restoration point.

Continuous data protection using a write filter

Content of an object of a source system for backup is received at a backup system different from the source system. A standby version of at least a portion of the object of the source system is maintained at a recovery system. A backup of the received content is performed using the backup system. In response to a request to place the standby version at a specified recovery time point, backup data utilized in updating the standby version to the specified recovery time point is provided to the recovery system via the backup system.

A stream of source system storage changes associated with an object are received at a backup system from a source system. The source system storage changes associated with the object are provided to a remote data recovery system. The remote data recovery system is configured to store the provided source system storage changes associated with the object. The backup system is utilized to generate one or more reference restoration points based on the stream of source system storage changes associated with the object.

A virtual machine container file is analyzed to determine which portion of the virtual machine container file corresponds to a virtual machine file system metadata of the virtual machine container file. One or more differences between a first version of a virtual machine container file and a second version of the virtual machine container file are determined at least in part by traversing a snapshot structure associated with the virtual machine container file. The determined one or more differences that corresponds to the virtual machine file system metadata portion of the virtual machine container file are identified based at least in part on the analysis of the virtual machine container file. The identified one or more differences corresponding to the virtual machine file system metadata portion of the virtual machine file are utilized to identify one or more changes from the content files included in the first version of the virtual machine container file to content files included in the second version of the virtual machine container file.

Incremental virtual machine metadata extraction

A specification of a data protection intent is received. Configurations for a plurality of different data management services are automatically determined in an attempt to achieve the specified data protection intent. The determined configurations in the plurality of different data management services are automatically implemented.

An indication of an instantiation of a first graphical user interface item representing a first data pool component being specified to be included in a data pool is received. An indication of an instantiation of a second graphical user interface item representing a second data pool component being specified to be included in the data pool is received. The second graphical user interface item is graphically instantiated as connected with the first graphical user interface item to indicate that the first data pool component and the second data pool component belong to the same data pool able to be referenced as a combined single data entity. An indication of an instantiation of a third graphical user interface item representing a data management action to be applied to the data pool, wherein the third graphical user interface item is graphically instantiated as connected with a graphical representation of the data pool is received.

Graphical user interface to specify an intent-based data management plan

A method and apparatus for dynamically adjusting an ingestion rate for backup operations on a source system. The method generally includes monitoring a resource utilization related to one or more performance metrics of the source system in performing at least a primary workload. Based on the monitored resource utilization, the backup system determines a data ingestion rate for backup operations on the source system. The backup system ingests data from the source system to a backup repository at the determined data ingestion rate.

Dynamic throughput ingestion of backup sources

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.

Growing community of inventors

San Jose, CA, United States of America

Chinmaya Manjunath