Abstract: Symmetric storage using a cloud-based storage system, including: receiving, at a cloud-based storage system among storage systems synchronously replicating a dataset, an I/O operation directed to the dataset; determining, in dependence upon the I/O operation, a metadata update describing a mapping of segments of content to an address within a storage object, wherein the storage object includes the dataset; and synchronizing metadata on another storage system of the storage systems by sending the metadata update from the cloud-based storage system to the other storage system to update a metadata representation on the second storage system in accordance with the metadata update.

Abstract: A data structure including a first set of storage devices is generated. Storage devices included in the data structure are to be used to form resiliency groups in a storage system. One or more resiliency groups are formed using the first set of storage devices. The data structure is modified to include a second set of storage devices. One or more subsequent resiliency groups are formed using the second set of storage devices.

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: 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: Corresponding confirmations that distributed agents are in a snapshot creation mode are received by a coordinating agent of the distributed agents. A new snapshot copy identifier for a snapshot is provided to the distributed agents. The snapshot is committed and the snapshot creation mode is exited.

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: One or more data segments to be stored in a storage system are formed. A first data segment of the one or more data segments is written to regions of flash memory of a first storage device of the storage system using an erasure code that divides the first data segment into data shards. Writing the first data segment includes calculating at least one intra-device recovery data shard corresponding to the data shards of the first data segment to be stored in the first storage device that protects the data shards. The data shards of the first data segment and the at least one intra-device recovery data shard are organized and stored into the flash memory of the first storage device based on fault boundaries in flash architectures for writing to flash cells of the flash memory.

Abstract: A method includes a data protection system determining, based on a first security threat detection process, that a storage system is possibly being targeted by a security threat; performing, based on the determining that the storage system is possibly being targeted by the security threat, a first remedial action with respect to the storage system, the first remedial action comprising generating a snapshot of data stored by the storage system; confirming, based on a second security threat detection process, whether the storage system is possibly being targeted by the security threat; and performing, based on the confirming whether the storage system is possibly being targeted by the security threat, a second remedial action with respect to the storage system, the second remedial action comprising specifying a retention duration with respect to the snapshot.

Abstract: An illustrative system is configured to optimize a transfer of a file system from a source storage system to a target storage system. For example, the system, in association with the transfer, determines that a copy of a collection of blocks containing data of block objects of the file system is already stored at the target storage system. In certain examples, an identifier referencing the collection of blocks is shared by the source and target storage systems and is used to determine that the copy of the collection of blocks containing data of block objects of the file system is already stored at the target storage system. The system uses the copy of the collection of blocks already stored at the target storage system instead of transferring the collection of blocks from the source storage system to the target storage system as part of the transfer.

Abstract: A list of a available zones across respective SSD storage portions of a plurality of zoned storage devices of a storage system is maintained. Data is received from multiple sources, wherein the data is associated with processing a dataset, the dataset including multiple volumes and associated metadata. Shards of the data are determined such that each shard is capable of being written in parallel with the remaining shards. The shards are mapped to a subset of the available zones, respectively. The shards are written to the subset of the available zones in parallel.

Abstract: Probabilistic error correction in flash-based storage systems, including: determine that a number of data shards in a data stripe having an unrecoverable error correction code (UECC) error exceeds a number of failed shards allowable under a redundancy level of the data stripe; identifying, in a portion of data in a data shard having the UECC error, a plurality of low-confidence bits, including: performing multiple reads of the portion of data; identifying, as the plurality of low-confidence bits, a plurality of bits having values differing across the multiple reads; and correcting the portion of data by assigning corrected values to the one or more low-confidence bits.

Abstract: Verifying that data has been correctly replicated to a replication target, including: replicating a dataset stored at a first computing system to a second computing system; and determining, based at least on a comparison of a first hash and a second hash, validity of the dataset stored at the second computing system, wherein the first hash is generated by applying a hash function to a copy of the dataset that is stored at the first computing system and the second hash is generated by applying the hash function to a copy of the dataset that is stored at the second computing system.

Abstract: Coordinated checkpoints among storage systems implementing checkpoint-based replication, including orchestrating one or more coordinated lightweight checkpoints for a source dataset stored across two or more source storage systems; and coordinating a replication of the one or more coordinated lightweight checkpoints from the two or more source storage systems to two or more target storage systems.

Abstract: An object store service is operated as a front-end service that stores objects of multiple buckets as objects of multiple back-end object stores. The object store service receives an object to be stored at a particular bucket of the multiple buckets. An object store operation is issued to a particular back-end object store of the multiple of back-end object stores having the particular bucket. The object store operation includes one or more characteristics to be associated with the object stored at the particular bucket.

Abstract: Providing for increased flexibility for large scale parity, the including: writing data to a storage system, including utilizing a first data protection scheme; identifying, for storage media in the storage system, characteristics of the storage media; identifying, in dependence up the characteristics for the storage media, a second data protection scheme to use for the data; and writing the data to the to the storage system utilizing the second data protection scheme.

Abstract: Servicing I/O operations in a cloud-based storage system, including: receiving, by the cloud-based storage system, a request to write data to the cloud-based storage system; storing, in solid-state storage of the cloud-based storage system, the data; storing, in object storage of the cloud-based storage system, the data; detecting that at least some portion of the solid-state storage of the cloud-based storage system has become unavailable; identifying data that was stored in the portion of the solid-state storage of the cloud-based storage system that has become unavailable; retrieving, from object storage of the cloud-based storage system, the data that was stored in the portion of the solid-state storage of the cloud-based storage system that has become unavailable; and storing, in solid-state storage of the cloud-based storage system, the retrieved data.

Abstract: In a particular embodiment, a dataset that is synchronously replicated across a plurality of storage systems is stored on a particular storage system. The storage system identifies input/output (I/O) requests directed to the dataset. The one or more I/O requests are initiated by an application hosted on a platform of the first storage system. The storage system services the one or more I/O requests directed to the dataset.

Abstract: A method for snapshots with crash consistency is provided. The method includes indicating intent to create a snapshot of storage system contents associated with an existing snapshot copy identifier, responsive to confirmation that all of a plurality of distributed agents are in a snapshot creation mode. The method includes responding, with a new snapshot copy identifier that replaces the existing snapshot copy identifier, to one or more inquiries from the plurality of distributed agents regarding one or more I/O operations, after the indicating the intent to create the snapshot. The method includes creating the snapshot using the existing snapshot copy identifier and committing the snapshot, responsive to receiving responses from the plurality of distributed agents that service is complete for all I/O operations that started before the indicating the intent to create the snapshot or that are associated with the existing snapshot copy identifier.

Abstract: An illustrative method includes maintaining, by a data protection system, a metric associated with a similar block detection process performed by a storage system with respect to data processed by the storage system, the metric representative of a measure of similar blocks in the data as detected by the similar block detection process; determining, by the data protection system, that the metric changes by more than a threshold amount; and determining, by the data protection system based on the determining that the metric changes by more than the threshold amount, that the data processed by the storage system is possibly being targeted by a security threat.

Abstract: A storage system has zones in solid-state storage memory, with power loss protection. The system identifies portions of data for processes that utilize power loss protection. The system determines to activate or deactivate power loss protection for the portions of data for the processes. The system tracks activation and deactivation of power loss protection in zones in the solid-state storage memory, in accordance with the portions of data having power loss protection activated or deactivated.