Abstract: Tiering snapshots across different storage tiers, including: creating a snapshot of a dataset, wherein the snapshot includes user data and metadata; offloading the snapshot of the dataset to a first storage level storage system; and migrating, in accordance with a lifecycle policy and via one or more copy offload operations, the snapshot from the first storage level storage system to a second storage level storage system.

Abstract: A method for execution by a storage network starts by maintaining loading and data access rate information for a storage node and estimating a future data access rate for the storage node. The method continues by determining a probability level of potential future data loss, based on the estimated future data access rate and in response to a determination that the probability level of potential future data loss compares unfavorably to a maximum probability of data loss threshold level the method continues by facilitating migration of at least a portion of data stored on the storage node for temporary storage in another storage node of the storage network.

Abstract: A method for storage units of a storage network begins by determining whether a first memory compares favorably to a predetermined performance level and determining whether a data access response activity associated with the first memory compares favorably to a data access response activity threshold. The method continues when the first memory compares unfavorably to the predetermined performance level and the data access response activity associated with the first memory compares unfavorably to a data access response activity threshold, by determining to migrate a set of encoded data slices stored in a first format from the first memory to a second memory, where a data object is dispersed error encoded in accordance with dispersed error encoding parameters to produce the set of encoded data slices. The method then continues, by selecting a second format for storing the set of encoded data slices and migrating the set of encoded data slices from the first memory to the second memory.

Abstract: A storage network operates by: encoding at least one data object in the storage network as encoded data slices that include one or more locally decodable code segments; detecting at least one storage error associated with storage of at least one of the encoded data slices in the storage network; and recovering the at least one of the encoded data slices utilizing the one or more locally decodable code segments.

Abstract: A method for a storage network begins by receiving, from a requestor, an access request for metadata associated with a data object, where the data object is dispersed error encoded in accordance with dispersed storage error encoding parameters to produce a set of encoded data slices and distributedly stored among a plurality of storage units, where a decode threshold number of encoded data slices are needed to recover the data object. The method continues, by generating a metadata lookup for the data object and then receiving metadata from one or more storage units associated with the storage network. The method then continues, by mapping, based on the metadata, a file path and a storage location for accessing each encoded data slice of the set of encoded data slices.

Abstract: Declarative provisioning of storage, including: identifying one or more policies associated with a storage object; determining, in dependence upon at least the one or more policies, a storage configuration for the storage object; and provisioning, in accordance with the storage configuration, storage that implements the storage object.

Abstract: A method for extending data lifetime for reference in deduplication is provided. The method includes determining that a quantity of user data has at least a threshold amount of data that is re-created in a storage system. The method includes protecting at least portions of the quantity of user data from erasure by garbage collection in the storage system during a predetermined time interval, wherein the protected at least portions are available for data deduplication of further user data in the storage system during the predetermined time interval.

Abstract: Utilizing data transfer estimates for active management of a storage environment, including: determining an estimated data transfer time from a source storage environment to a destination storage environment; determining whether the estimated data transfer time exceeds a threshold; and performing, in response to the estimated data transfer time exceeding the threshold, a remedial action associated with data transfers between the source storage environment and the destination storage environment.

Abstract: A plurality of storage nodes within a single chassis is provided. The plurality of storage nodes is configured to communicate together as a storage cluster. The plurality of storage nodes has a non-volatile solid-state storage for user data storage. The plurality of storage nodes is configured to distribute the user data and metadata associated with the user data throughout the plurality of storage nodes, with erasure coding of the user data. The plurality of storage nodes is configured to recover from failure of two of the plurality of storage nodes by applying the erasure coding to the user data from a remainder of the plurality of storage nodes. The plurality of storage nodes is configured to detect an error and engage in an error recovery via one of a processor of one of the plurality of storage nodes, a processor of the non-volatile solid state storage, or the flash memory.

Abstract: Non-disruptively moving a storage fleet control plane, including deploying, on an edge device, one or more agents that are managed by a control plane residing in a cloud computing environment; mediating one or more API requests, generated by the control plane, directed to the one or more agents on the edge device; and migrating, in response to a first condition, the control plane to the edge device.

Abstract: A method, apparatus, and computer program product for tier-specific data compression, comprising comparing costs associated with a plurality of storage configurations for storing data based on one or more usage characteristics of data, wherein each storage configuration of the plurality of storage configurations corresponds to a particular storage tier of a plurality of storage tiers and a particular compression algorithm of a plurality of compression algorithms and based on the comparison of the costs, storing the data using a storage configuration of the plurality of storage configurations.

Abstract: Illustrative in-line data processing (e.g., data transformations) as part of fulfilling read and/or write requests to a storage system are described. In an example method, a storage system or a component of a storage system receives a request from a client of the storage system to read or write data in the storage system, the request defined in accordance with a storage access protocol and indicating a data transformation function to be applied to the data as part of fulfilling the request; initiates, based on the request, execution of the data transformation function to transform the data into transformed data; and uses the transformed data to fulfill the request.

Abstract: An exemplary method includes a data protection system detecting one or more delete requests to delete one or more recovery datasets of a storage system, determining that the one or more delete requests are inconsistent with a recovery dataset deletion pattern associated with the storage system, and determining, based on the determining that the one or more delete requests are inconsistent with the recovery dataset deletion pattern, that data stored by the storage system is possibly being targeted by a security threat.

Abstract: Ensuring resiliency to storage device failures in a storage system, including: determining a number of storage device failures within a particular write group that are to be tolerated by the storage system; for a plurality of datasets stored within the storage system, writing each dataset to at least a predetermined number of storage devices within the particular write group, wherein the predetermined number of storage devices is greater than the number of storage device failures within the particular write group that are to be tolerated by the storage system; and responsive to recovering from a system interruption: determining a number of readable storage devices that contain a copy of the dataset; and if the number of readable storage devices that contain a copy of the dataset is not greater than the number of failures that are to be tolerated, writing the dataset to one or more additional storage devices.

Abstract: In one implementation, a method includes identifying a first content-dependent feature associated with a data sector. The method further includes determining a baseline data sector associated with the data sector. The method further includes determining, by a processing device, a content-dependent delta between the first content-dependent feature and a second content-dependent feature of the baseline data sector. The method further includes providing the content-dependent delta and an indicator to the baseline data sector for storage on a plurality of storage devices.

Abstract: A method of scheduling input/output operations for a storage system including determining a deadline for a storage operation, wherein the deadline is dependent on an expected latency of the storage operation; adding the storage operation to a queue of storage operations; and reordering the queue dependent upon the deadline of the storage operation and one or more deadlines of one or more storage operations in the queue of storage operations.

Abstract: Methods and apparatus for efficient storage of a data object in a storage network. A method for execution by one or more processing modules of a storage network begins by receiving a store data request including a data object and a data identifier, and generating a source name for the data object. The method continues by determining whether the data object is already stored in memory of the storage network. In response to determining that the data object is already stored in the memory of the storage network, the method further includes identifying location information for the data object, storing the location information using the source name, and updating metadata for the data object to indicate that an additional copy of the data object is stored in the memory of the storage network.

Abstract: Methods and apparatus for storage pool tiering in a storage network. In an embodiment, a method executed by one or more processing modules of a storage network includes maintaining a storage network access control list (ACL) registry. The ACL registry includes a storage network sub-registry and one or more vault sub-registries, and each of the sub-registries includes one or more ACLs. The method further includes receiving a storage network access request from a requesting entity, identifying a request type of the storage network access request, and identifying the one or more ACLs of a sub-registry associated with the request type. The method continues with retrieving the one or more ACLs, identifying an ACL of the one or more ACLs based on an identifier associated with the requesting entity, and comparing the storage network access request to permissions of the identified ACL to determine whether the access request is authorized.

Abstract: A virtual storage volume may be implemented as one or more chunks stored on a set of storage nodes. The virtual storage volume may be dynamically adjusted by adjusting the one or more chunks that make up the virtual storage volume, without taking the virtual storage volume offline. Such dynamic volume adjustment may allow for increasing volume size without moving data unnecessarily. In addition or alternatively, such dynamic volume adjustment may free up storage space in a node with minimum movement of data.

Abstract: An illustrative method includes accessing, by a controller operating within a global control plane, a recovery policy that specifies parameters for generating recovery data associated with one or more resources of a first cluster comprising a first one or more containers, wherein the first cluster comprises a first local control plane separate from the global control plane; determining, by the controller and based on the recovery policy, a second cluster comprising a second one or more containers, wherein the second cluster comprises a second local control plane separate from the global control plane; and generating, by the controller and with respect to the second cluster, the recovery data associated with the one or more resources of the first cluster.