Netapp, Inc.

Cohesity, Inc.

Jagavar Nehra

Roopesh Chuggani

Tijin George

Dnyaneshwar Nagorao Pawar

Atul Ramesh Pandit

Kiyoshi James Komatsu

Jose Mathew

Sumith Makam

Sriram Venketaraman

Anil Kumar Ponnapur

Abhisar

Apurv Gupta

Emalayan Vairavanathan

Amandeep Gautam

Debasish Garai

Techniques are provided for an object file system for an object store. Data, maintained by a computing device, is stored into slots of an object. The data within the slots of the object is represented as a data structure comprising a plurality of nodes comprising cloud block numbers used to identify the object and particular slots of the object. A mapping metafile is maintained to map block numbers used to store the data by the computing device to cloud block numbers of nodes representing portion of the data stored within slots of the object. The object is stored into the object store, and the mapping metafile and the data structure are used to provide access through the object file system to portions of data within the object.

Snapshot storage and management within an object store

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

Techniques are provided for caching data during an on-demand restore using a cloud block map. A client may be provided with access to an on-demand volume during a restore process that copies backup data from a snapshot within a remote object store to the on-demand volume stored within local storage. In response to receiving a request from the client for a block of the backup data not yet restored from the snapshot to the on-demand volume, the block may be retrieved from the snapshot in the remote object store. The block may be cached within a cloud block map stored within the local storage as a cached block. The client may be provided with access to the cached block.

On-demand restore of a snapshot to an on-demand volume accessible to clients

Techniques are provided for incremental snapshot copy to an object store. A list of deallocated block numbers of primary storage of a computing device are identified. Entries for the list of deallocated block numbers are removed from a mapping metafile. A list of changed block numbers corresponding to changes between a current snapshot of the primary storage and a prior copied snapshot copied from the primary storage to the object store is determined. The mapping metafile is evaluated using the list of changed block numbers to identify a deduplicated set of changed block numbers without entries within the mapping metafile. An object, comprising data of the deduplicated set of changed block numbers, is transmitted to the object store for storage as a new copied snapshot.

Transferring snapshot copy to object store with deduplication preservation and additional compression

Cloud block map for caching data during on-demand restore

Techniques are provided for managing objects within an object store. An object is maintained within an object store. In an embodiment, a rule is enforced for the object that in-use slots of the object are non-modifiable and unused slots of the object are modifiable. Metadata of additional information for a slot within the object is attached to the object header. A first application allowed to access user data within the slot is provided access to the user data without being provided access to the metadata. A second application allowed access to the user data and the additional information is provided with access to the user data and the metadata for identifying a location of additional information within the object.

Metadata attachment to storage objects within object store

Techniques are provided for managing objects within an object store. An object is maintained within an object store. The object comprises a plurality of slots. Each slot is used to store a unit of data accessible to applications hosted by remote computing devices. The object comprises an object header used to store metadata for each slot. A determination is made that the object is a fragmented object comprising an in-use slot of in-use data and a freed slot from which data was freed. The object is compacted to retain in-use data and exclude freed data as a rewritten object.

Defragmentation for objects within object store

Techniques are provided for managing objects within an object store. An object is maintained within an object store. The object is used to store data of a snapshot of a file system hosted by a remote computing device. A determination is made that the snapshot was deleted by the remote computing device. Bitmaps describing objects within the object store that are related to snapshots of the file system are evaluated to determine that the object is unique to the deleted snapshot. The object is freed from storage within the object store.

Growing community of inventors

Bengaluru, India

Jagavar Nehra