Abstract: A selected data chunk associated with an object is determined to be sent to a destination. A chunk compression grouping storing the selected data chunk associated with the object is identified. The identified chunk compression grouping includes a plurality of data chunks compressed together. A data content version that includes the selected data chunk associated with the object to be provided to the destination is determined from a plurality of data content versions based at least in part on a metric associated with the identified chunk compression grouping.

Abstract: A virtual machine disk image file backup is selected among a plurality of virtual machine disk image file backups stored on a backup storage based on a backup update policy. A version of the selected virtual machine disk image file backup is mounted. Based on the backup update policy, an update to the mounted version of the selected virtual machine disk image file backup is applied without restoring the selected virtual machine disk image file backup. The updated version of the selected virtual machine disk image file backup is stored on the backup storage.

Abstract: 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.

Abstract: 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.

Abstract: Data is ingested from a source system. Ingesting the data includes determining corresponding chunk identifiers for a plurality of data chunks corresponding to the ingested data and for each of the plurality of data chunks, verifying whether the corresponding chunk identifier is included in a data structure tracking identifiers of data chunks that were already stored in a storage of a storage system before the data ingestion started and storing the data chunk in a storage based on the verification. After the ingesting is completed, deduplication of the ingested data chunks stored in the storage having a same chunk identifier is performed and the data structure is updated based on the deduplication.

Abstract: A request to restore an instance of an object that is stored in a storage associated with a cluster of nodes to a target destination is received. Data of the object is divided into a plurality of data portions. Corresponding data portions of the plurality of data portions are assigned to each node of a plurality of nodes of the cluster. It is determined that a first node of the cluster of nodes does not currently store in a storage associated with the first node at least a part of a corresponding data portion of the object assigned to the first node. At least the part of the corresponding data portion of the object assigned to the first node is received at the first node from a second node of the cluster of nodes. At least the part of the corresponding data portion of the object received from the second node is provided from the first node to the target destination.

Abstract: 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.

Abstract: 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.

Abstract: Content of an object of a source system for backup is received at a backup system different from the source system. A standby version of at least a portion of the object of the source system is maintained at a recovery system. A backup of the received content is performed using the backup system. In response to a request to place the standby version at a specified recovery time point, backup data utilized in updating the standby version to the specified recovery time point is provided to the recovery system via the backup system.

Abstract: 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.

Abstract: Metadata of each file of a group of files of a storage and chunk file metadata are analyzed to identify one or more file segment data chunks that are not referenced by the group of files of the storage. Fragmented chunk files to be combined together are identified based at least in part on the one or more identified file segment data chunks. The chunk file metadata is updated with an update that concurrently reflects the removal of at least a portion of the one or more file segment data chunks that are not referenced by the group of files and the combination of the identified fragmented chunk files.

Abstract: One or more event logs are received. The one or more event logs are analyzed using a plurality of models to detect one or more anomalous events. A graphical representation of risk entities associated with at least one of the one or more detected anomalous events is provided. A visual representation of automatically detected relationships between the risk entities associated with the at least one of the one or more detected anomalous events is provided in the graphical representation. Indications of measures of anomaly associated with detected anomalous events are provided for the associated risk entities.

Abstract: One or more data packets at a storage node of a storage cluster system is received via a virtual network associated with a storage tenant. A connection between the storage tenant and a tenant communication component of the storage cluster system is terminated. A new connection is established between the tenant communication component of the storage cluster system and a destination associated with the one or more data packets. The one or more data packets are provided to the destination associated with the one or more data packets using a virtual network associated with storage nodes of the storage cluster system.

Abstract: Techniques for cloning, writing to, and reading from file system metadata. Cloning involves identifying a first set of pointers included h a first root node in a file system metadata tree structure that stores file system metadata n leaf nodes of the tree structure, creating a first copy of the first root node that includes the first set of pointers, creating a second copy of the first root node that includes the first set of pointers, associating the first copy with a first view, and associating the second copy with a second view. Reading generally involves traversing the tree structure towards a target leaf node that contains data to be read. Writing generally involves traversing the tree structure in the same manner, but also creating copies of any nodes to be modified if those nodes are deemed to have a different treeID than a particular root node.

Abstract: 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.

Abstract: An indication to perform a backup of file system data is received. The file system data includes a content file having a size greater than a threshold size. A plurality of component file metadata structures for the content file are generated. File metadata of the content file split across the plurality of component file metadata structures is stored. The plurality of component file metadata structures are associated with different portions of the content file. A component file metadata structure of the plurality of component file metadata structures stores file metadata corresponding to a portion of the content file. The file metadata corresponding to the portion of the content file includes one or more references to locations of data chunks associated with the portion of the content file.

Abstract: A request to perform a storage operation for a storage system is received. It is determined that the requested storage operation is associated with a policy that requires a quorum of approvals before being allowed to be performed. It is determined whether the quorum of approvals has been obtained. In response to a determination that the quorum of approvals has been obtained, a command to perform the requested operation is provided to the storage system.

Abstract: 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.

Abstract: A tree data structure for a file is maintained. The tree data structure is used to capture different versions of the file at different moments of time. An access pattern associated with the file stored on a storage system is determined based at least in part on time-series data associated with the file using the tree data structure that captures different versions of the file at different moments in time. The determined access pattern indicates a period for which the file is likely to be accessed. The file is migrated from a secondary storage tier to a primary storage tier.

Abstract: 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.