Cohesity, Inc.

Praveen Kumar Yarlagadda

Venkata Ranga Radhanikanth Guturi

Tushar Mahata

Anubhav Gupta

Zhihuan Qiu

Sarthak Agarwal

Vipin Gupta

Markose Thomas

Prashant Pogde

Akshat Agarwal

Aiswarya Bhavani Shankar

Dane Van Dyck

A specification of content to be stored in a cloud storage is received at a client-side component. A first portion of the content is divided into a plurality of data chunks. One or more data chunks of the plurality of data chunks that are to be sent via a network to be stored in the cloud storage are identified. It is determined whether a batch size of the one or more identified data chunks does not meets a threshold size. One or more data chunks of a second portion of the content that are to be stored in the cloud storage are identified. It is determined that a size of a second batch of data chunks that includes the one or more identified data chunks of the first portion of the content and the one or more identified data chunks of the second portion of the content does not meet the threshold size. It is determined that a batch period is greater than or equal to a batch threshold period. The second batch of data chunks is written to a storage of a cloud server included in a data plane.

Efficiently storing data in a cloud storage

One or more objects associated with a source storage is determined to be archived to a remote storage. A corresponding minimum expiration time is stored in nodes of a tree data structure associated with an archive that represents the archived data associated with the source storage. At least a portion of the tree data structure associated with the archive is traversed to identify one or more nodes associated with one or more archived objects having a corresponding expiration time expiring before an expiration time associated with the archive.

Managing expiration times of archived objects

A cloud server component determines that a size of a first cloud storage element object is at least below a first threshold. In response to the first determination, a client-side component is requested to store additional data in the cloud storage element object including by having the client-side component update the first cloud storage element with an updated version that includes previously existing data of the first cloud storage element and the additional data. The first cloud storage element object is added to a set of one or more cloud storage element objects available for update. The client-side component is configured to generate an updated version of the first cloud storage element object that has a size that is greater than or equal to the first threshold.

An amount of expiration time extension for one or more objects associated with a first archive of a first snapshot of a source storage is determined based at least in part on a second data management policy associated with a second archive and one or more dynamically determined metrics. The first archive that includes the one or more objects is caused to be stored to a remote storage. At least a portion of content of the first archive is referenced by data chunks stored in a first chunk object of the remote storage and the first archive is associated with a first data management policy. Based on the determined amount of expiration time extension, an expiration time for the one or more objects associated with the first archive is stored in an archive metadata of the one or more objects associated with the first archive.

Extending an expiration time of an object associated with an archive

An indication to store to a remote storage a new archive of a snapshot of a source storage is received. At least one shared data chunk of the new archive is determined to be already stored in an existing chunk object of the remote storage storing data chunks of a previous archive. One or more evaluation metrics for the existing chunk object are determined based at least in part on a retention period associated with one or more individual chunks stored in the chunk object and a data lock period associated with the entire existing chunk object. It is determined based on the one or more evaluation metrics whether to reference the at least one shared data chunk of the new archive from the existing chunk object or store the at least one shared data chunk in a new chunk object of the remote storage.

Managing objects stored at a remote storage

A request to obtain an identified content item is received. It is determined that the identified content item is stored in a plurality of locations. It is determined to obtain the identified content item from a first storage location storing a first serialized representation of a file system snapshot that includes the identified content item and a second storage location storing a second serialized representation of the file system snapshot that includes the identified content item based on available resources associated with the plurality of locations. The identified content item is extracted from the first serialized representation at the first storage location and from the second serialized representation at the second storage location including building a stubbed tree data structure using the first serialized representation and the second serialized representation. The extracted identified content item is provided using the stubbed tree data structure.

Restoration of specified content from an archive

At least a portion of data of a tree data structure is serialized into a first set of flat data. At least a portion of a structure of the tree data structure is serialized to reproduce at least the portion of the structure in a second set of flat data. It is determined to access a desired data of the tree data structure from an archive. The second set of flat data is read to reconstitute at least the portion of a structure of the tree data structure. The reconstituted structure of the tree data structure is used to determine a data offset associated with the first set of flat data, wherein the data offset corresponds to the desired data. The desired data is accessed using the data offset associated with the first set of flat data.

Snapshot archive management

A request to access one or more files associated with a particular pint in time that are archived at a cloud storage is received. A file system metadata tree data structure based on metadata associated with the one or more requested files that is obtained from the cloud storage is partially restored at a storage system. The partially restored file system metadata tree data structure includes one or more stub nodes associated with one or more non-requested files. Access to the one or more requested files is provided using the partially restored file system metadata tree data structure. Metadata associated with the one or more non-requested files is prefetch from the cloud storage. A portion of the file system metadata tree data structure corresponding to the one or more non-requested files is restored in part by replacing the one or more stub nodes associated with the one or more non-requested files with metadata corresponding to the one or more non-requested files.

Remotely mounted file system with stubs

An instruction to generate a cloud instantiation of a secondary storage system is provided. One or more secondary storage clusters are virtually rebuilt in the cloud instantiation of the secondary storage system. A new cloud instance of a user virtual machine is deployed based on at least a portion of data stored in the one or more rebuilt secondary storage clusters of the cloud instantiation of the secondary storage system. A version of at least the portion of the data of the one or more rebuilt secondary storage clusters is provided to a cloud deployment server.

Deploying a cloud instance of a user virtual machine

A specification of content to be stored in a cloud storage is received at a client-side component. A portion of the content is divided into a plurality of data chunks. One or more data chunks of the plurality of data chunks that are to be sent via a network to be stored in the cloud storage are identified. It is determined whether a batch size of the one or more identified data chunks meets a threshold size. Based on the determination of whether the batch size meets the threshold size, a cloud storage destination among a plurality of different cloud storage destinations associated with different performance tiers is selected.

A list of one or more archives available to be restored is provided to an authenticated user. The list of one or more archives available to be restored is based in part on a credential provided by the authenticated user. The credential provided by the user is linked to a subset of a plurality of snapshot archives associated with an enterprise. A selection of one of the one or more archives and an external target for the selected archive is received. A cloud instantiation of a secondary storage system is utilized to reconstitute a tree data structure based on serialized data included in the selected archive. A request to restore data associated with the selected archive to the external target is received. The requested data associated with the archive is provided to the external target.

Restoring an archive authorized by an authenticated user

A first archive of a first snapshot of a source storage is caused to be stored to a remote storage. At least a portion of content of the first archive is stored in data chunks stored in a first chunk object of the remote storage and the first archive is associated with a first data policy. A second archive of a second snapshot of the source storage is caused to be stored to the remote storage. At least a portion of content of the second archive is referenced from data chunks stored in the first chunk object and the second archive is associated with a second data policy. Policy compliance of the chunk object storing data chunks referenced by the first archive and the second archive that are different is automatically managed based on the first data policy and the second data policy that are different.

A cloud server determines that a size of a first cloud storage element object is at least below a first threshold. In response to the first determination, a client-side component is requested to store additional data in the cloud storage element object including by having the client-side component update the first cloud storage element with an updated version that includes previously existing data of the first cloud storage element and the additional data. The first cloud storage element object is added to a set of one or more cloud storage element objects available for update. The client-side component is configured to generate an updated version of the first cloud storage element object that has a size that is greater than or equal to the first threshold.

Metadata of a root node from a serialized representation of a file system metadata tree data structure is obtained. A representation of the root node that references a stub intermediate node that is a placeholder for an intermediate node stored in the serialized representation is created. A request to access data of a leaf node in a tree path including the intermediate node is received. In response to the request, metadata of the intermediate node is obtained from serialized metadata representation.

Growing community of inventors

Santa Clara, CA, United States of America

Praveen Kumar Yarlagadda