Cohesity, Inc.

Karandeep Singh Chawla

Nagapramod S Mandagere

Yu-Shen Ng

Anubhav Gupta

Apurv Gupta

Chinmaya Manjunath

Sudhir Srinivas

Colin Scott Johnson

Sidharth Mishra

Prashant Gaurav

Amitabh Sinha

Nilesh Pathak

Virupaksha Kanjilal

Dayanand Sharma

Prakash Veljibhai Vaghela

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

An amount of data change associated with a version of a content file with respect to one or more previous versions of the content file is determined. The amount of change associated with the version of the content file is determined using a tree data structure associated with the content file that is stored on a storage cluster. One or more statistics associated with backup snapshot are provided to a server. The server is configured to determine that the amount of data change associated with the version of the content file is anomalous based in part on the one or more statistics associated with the backup snapshot. A notification that data associated with the backup snapshot is potentially infected by malicious software is received from the server. The version of the content file is indicated as being potentially infected by malicious software.

Malicious software detection

A request to restore a plurality of files to a first storage system from a backup stored at a second storage system is received. Corresponding file relocation metadata for each of the plurality of files is provided to the first storage system. The corresponding file relocation metadata for each of the plurality of files enables accessibility of contents of the plurality of files at the first storage system without storing entire contents of the plurality of files at the first storage system. A corresponding full content version for at least one of the plurality of files that is to be utilized by the first storage system is provided to enable direct access at the first storage system to contents of the at least one of the plurality of files instead of utilizing corresponding file relocation metadata for the at least one of the plurality of files to access the contents of the at least one of the plurality of files.

Restoring a storage system using file relocation metadata

A plurality of scanned backup snapshots are generated. A backup snapshot among a plurality of backup snapshots is selected. At least a portion of the selected backup snapshot is restored in a temporary environment to create a restored instance of at least the portion of the selected backup snapshot. A vulnerability scan of the restored instance of at least the portion of the selected backup snapshot is performed. One or more vulnerabilities of the scanned portion of the selected backup snapshot are tracked. A request associated with identifying a scanned backup snapshot to restore from the plurality of scanned backup snapshots is received. In response to the request, at least a predetermined identification of the one or more vulnerabilities of the selected backup snapshot is provided.

Scanning a backup for vulnerabilities

A copy of files of a primary storage system are stored at a secondary storage system. The metadata associated with the copy of the files of the primary storage system stored at the secondary storage system are analyzed to determine at least a portion of a hierarchical storage tier management plan for the primary storage system including by identifying one or more files to be migrated from a first tier of storage of the primary storage system to a different storage tier. An implementation of at least a portion of the hierarchical storage tier management plan is initiated.

Using a secondary storage system to implement a hierarchical storage management plan

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.

Growing community of inventors

Santa Clara, CA, United States of America

Karandeep Singh Chawla