Cohesity, Inc.

Manvendra Singh Tomar

Apurv Gupta

Chinmaya Manjunath

Akshat Agarwal

Shobhit Agarwal

Kishan Venkata Sravan Nerella

Shubham Arvind Barai

Mandar Suresh Naik

Kushal Singh

Tarun Kumar Yadav

Donthula Akshith Reddy

Anubhav Gupta

Subramanian Sethumadhavan

Yu-Shen Ng

Jeffrey Howard

Anshu Avinash

Naga Venkata Sai Indubhaskar Jupudi

A repository of replicated chunk files is analyzed to identify chunk files that meet at least a portion of combination criteria. Selected chunk files are associated together under a data protection grouping container. Erasure coding is applied to the data protection grouping container including by utilizing the selected chunk files as different data stripes of the erasure coding and generating one or more parity stripes based on the different data stripes.

Container-based erasure coding

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 mechanism for storing indexing updates is described. A secondary storage system is configured to store a backup of a primary storage system. A plurality of different indexing updates of a data repository associated with the secondary storage system is received. An indexing update may include metadata and/or updates to the metadata for a data item in the backup. The indexing updates may be obtained from an indexing process. At least a portion of the indexing updates are sent for storage in an intermediate store. An indication to commit the indexing updates is received. In response, the indexing updates including the at least the portion of the indexing updates are requested to be committed. The indexing updates batched together into a batch to be committed to a metadata store.

Write optimized, distributed, scalable indexing store

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.

Metadata associated with content stored in a corresponding primary storage system is received receiving from each secondary storage cluster of a plurality of different secondary storage clusters included in different storage domains. The metadata received from the plurality of different secondary storage clusters is stored and indexed together. A unified metadata search interface is provided for stored data of the corresponding primary storage systems and the plurality of different secondary storage clusters of the different storage domains.

Unified metadata search

Growing community of inventors

Madhya Pradesh, India

Manvendra Singh Tomar