Cohesity, Inc.

Amandeep Gautam

Apurv Gupta

Debasish Garai

Venkata Ranga Radhanikanth Guturi

Rupesh Bajaj

Anand Arun

Himanshu Mehra

Vairavanathan Emalayan

Emalayan Vairavanathan

Jagavar Nehra

Data associated with an object to be stored is received from a source system for a destination logical storage container selected among a plurality of destination logical storage containers. A total number of the destination logical storage containers allowed to be concurrently supported by the source system is limited. The selected destination logical storage container is shared by a plurality of objects of the source system. Based at least in part on an identifier associated with the object, a child logical storage container corresponding to the object is identified. The child logical storage container is different from the selected destination logical storage container. The data associated with the object received for the selected destination logical storage container is automatically stored in the identified child logical storage container.

Performing a backup of an object based on an identifier associated with the object

An assigned subgroup that includes a plurality of entries is traversed by a prefetcher. It is determined that an expected number of entries associated with the assigned subgroup have been traversed. In response to determining that expected number of entries associated with the assigned subgroup have been traversed, it is determined that a last read entry associated with the assigned subgroup does not correspond to a last entry associated with the assigned subgroup. The prefetcher is preempted by stopping the prefetcher from obtaining a list of entries associated with a remaining portion of the assigned subgroup.

Parallelization of incremental backups

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

A backup of a current state of a storage is determined to be initiated. A previous state of the storage storing key-object entries is analyzed to identify parallelization partition identifiers. At least a portion of the partition identifiers is used as boundaries between subgroups of the key-object entries processed in parallel to perform the backup of the current state of the storage.

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.

Growing community of inventors

San Jose, CA, United States of America

Amandeep Gautam