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: Continuing replication during storage system transportation, including: replicating, between a first storage system and a second storage system, a dataset; connecting, by the first storage system during movement of the first storage system to a new physical location, to a communication network available at one or more intermediate physical locations; and continuing the replicating of the dataset between the first storage system at one or more of the intermediate physical locations and the second storage system over the communication network available at one or more of the intermediate physical locations.

Abstract: An illustrative method includes a data protection system detecting an anomaly associated with a managed run-time environment; determining, based on the detecting the anomaly, that the managed run-time environment is possibly being targeted by a security threat; and performing, based on the determining that the managed run-time environment is possibly being targeted by the security threat, a remedial action associated with the managed run-time environment. The performing the remedial action may include identifying a recovery dataset generated prior to the detecting the anomaly, the recovery dataset for data associated with the managed run-time environment and stored by a storage system, and converting the recovery dataset into a protected recovery dataset that cannot be deleted without a specific instruction provided by an authorized entity.

Abstract: Supporting multiple replication schemes across distinct network layers, including: replicating, over a first type of network messaging layer, data between a first storage system and a second storage system; selecting a different messaging layer for data replication; and replicating, over a second type of network messaging layer, data between the first storage system and the second storage system.

Abstract: End-to-end encryption in a storage system with multi-tenancy, includes: performing deduplication on a first tenant dataset, the first tenant dataset including data encrypted using a first storage system encryption key; and performing deduplication on a second tenant dataset, the second tenant dataset including data encrypted using a second storage system encryption key, where deduplication is not performed between the first and second tenant datasets.

Abstract: Providing scalable and reliable container-based storage services, including: deploying a containerized storage controller on a first node among of plurality of nodes operable to support execution of the containerized storage controller; associating a dataset stored in backing storage accessible by the first node with one or more virtualized volumes presented by the containerized storage controller; and providing, by the containerized storage controller to one or more client hosts, a set of storage services for the one or more virtualized volumes.

Abstract: A system for cloud-based file services, comprising: a plurality of single-tenant file system nodes configured to provide file system access to an object store via a plurality of multitenant storage nodes; the plurality of multitenant storage nodes sharing access to the object store; and one or more management nodes configured to provision resources for the plurality of single-tenant file system nodes and the plurality of multitenant storage nodes, including modifying resources within the system.

Abstract: Systems, methods, and computer readable storage mediums for blockchain logging of volume-level events in a storage system. Blockchain logging of volume-level event includes receiving, by a storage controller, a storage operation directed to a storage volume; detecting, by the storage controller, that the storage operation is a volume-level event associated that affects the volume as a whole; and updating a blockchain ledger to include information describing the volume-level event, wherein the information comprises data describing a host associated with the event.

Abstract: An illustrative method includes determining that a total amount of read traffic and write traffic processed by a storage system during a time period exceeds a threshold; determining a first compressibility metric associated with the write traffic; determining a second compressibility metric associated with the read traffic; determining, based on a comparison of the first compressibility metric with the second compressibility metric, that the write traffic is less compressible than the read traffic; determining, based on the total amount of read traffic and write traffic exceeding the threshold and on the write traffic being less compressible than the read traffic, that the storage system is possibly being targeted by a security threat; and modifying, in response to the determining that the storage system is possibly being targeted by the security threat, a data protection parameter set for one or more recovery datasets generated by the storage system.

Abstract: A storage system establishes a staging region, for temporary writing of arriving data, and a stable region, for transfer of data from the staging region, in storage memory. The storage system establishes resiliency groups, each with a characteristic level of redundancy that is settable on an individual basis. The storage system performs data accesses of data stripes in accordance with the staging region, the stable region, a first resiliency group and a second resiliency group.

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: 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: Controlling the direction of replication between cross-region replicated object stores is disclosed.

Abstract: Providing application-side infrastructure to control cross-region replicated object stores is disclosed. An embodiment includes determining, for an object store replicated across a plurality of storage systems at a plurality of locations, a minimum time interval between requests to modify the object store that are received by differing storage systems of the plurality of storage systems that ensures a predictable result on all storage systems among which the requested modifications are replicated; and providing, through an application programming interface (API) to a client that utilizes the object store, one or more object store parameters including the minimum time interval.

Abstract: A storage system switching mediators within a storage system synchronously replicating data, where the switching between mediators includes determining that availability of a first mediator service has decreased to a particular level, wherein the first mediator service can provide mediation services at the particular level to a plurality of storage systems and is external to the plurality of storage systems; and based on the determination, switching from use of the first mediator service to use of a second mediator service that is external to the plurality of storage systems.

Abstract: Application-managed fault detection for cross-region replicated object stores is disclosed. An embodiment includes determining, by a first storage system among a plurality of storage systems replicating an object store, a faulted state in response to identifying a fault that prevents replication of updates to the object store to at least a second storage system of the plurality of storage systems; providing, through an API, an indication that the first storage system has entered the faulted state; and receiving a request indicating how to proceed in the presence of the fault.

Abstract: A read request with a high priority indication is received. A determination as to whether an in progress flash programming operation would delay processing the read request for a threshold amount of time is made. In response to determining that the in progress flash programming operation delays processing the read request for the threshold amount of time, the in progress flash programming operation is interrupted.

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: High availability and disaster recovery for replicated object stores is disclosed. An embodiment includes receiving, by a first storage system of a plurality of storage systems symmetrically replicating objects of a bucket, a request to establish immutable content for the bucket; indicating, by the first storage system to a second storage system of the plurality of storage systems, the request to establish immutable content, wherein the second storage system establishes an ordering for conflicting requests of different storage systems to establish immutable content for the bucket; and processing, by the first storage system, the request based on ordering information received from the second storage system.

Abstract: An illustrative method includes an object retention management system establishing a retention policy for a bucket of an object-based storage system, detecting an operation that causes an object to be stored within the bucket, and applying, based on the detecting of the operation, the retention policy to the object, wherein the retention policy prevents the object from being deleted or overwritten for a predefined time duration and the retention policy cannot be modified or disabled for the bucket by a user.