A cluster of one or more computing devices is operably coupled to a plurality of storage devices. Each computing device in the cluster comprises a frontend and a backend. The backend comprises a plurality of buckets. Each bucket is operable to build a failure-protected stipe that spans two or more of the plurality of the storage devices. A file system comprises one or more failure-protected stipes. A client other than the one or more computing devices in the cluster is operable to access at least a portion of the file system via a stateless mount string comprising a cryptographically-signed key.

A device creates virtual storage bucket to abstract the data and the access from another device, and to secure the access using the IAM and the data using encryption and/or Mojette transform in order to generate encrypted/encoded data and transmits the data to another device. The other device saves the encrypted/encoded data for later transmitting the data to the same first device or another for decryption/decoding.

An illustrative embodiment disclosed herein is an apparatus including a processor and a memory. In some embodiments, the memory includes programmed instructions that, when executed by the processor, cause the apparatus to store a first object and a second object in a first region based on the first object and the second object having a first policy. In some embodiments, the memory includes programmed instructions that, when executed by the processor, cause the apparatus to store a third object in a second region based on the third object having a second policy. In some embodiments, a virtual disk includes the first region and the second region.

Example implementations relate to virtual persistent volumes. In an example, a manifest of a containerized application to which a virtual persistent volume is allocated is read from a container orchestrator. An application data store profile that matches information of the manifest is identified from among a plurality of application data store profiles that each include storage parameters preconfigured for a respective application type. The virtual persistent volume is modified according to the identified application data store profile.

Example implementations relate to virtual persistent volumes. In an example, a storage operation request includes a volume identifier. A volume mapping that corresponds to the volume identifier is identified. Underlying volume identifiers are identified based on the volume mapping. The underlying volume identifiers relate to underlying storage volumes that form at least part of a virtual persistent volume associated with the volume identifier. The storage operation request is relayed, using the underlying volume identifiers, to storage systems on which the underlying storage volumes are respectively located.

Disclosed deduplication techniques at a distributed data storage system guarantee that space reclamation will not affect deduplicated data integrity even without perfect synchronization between components. By understanding certain “behavioral” characteristics and schedule cadences of backup operations that generate backup copies received at the distributed data storage system, data blocks that are not re-written by subsequent backup copies are pro-actively aged, while promoting continued retention of data blocks that are re-written. An expiry scheme operates with block-level granularity. Each unique deduplicated data block is given an expiry timeframe based on the block's arrival time at the distributed data storage system (i.e., when a backup copy supplies the block) and further based on backup frequencies of the various virtual disks referencing a unique system-wide identifier of the block, which is based on the block's hash value. Communications between components are kept to an as-needed basis. Cloud-based and multi-cloud configurations are disclosed.

Administering storage access in a cloud-based storage system includes: acquiring, by a first storage controller, in response to a protocol request for exclusive access to an area of storage, a first lease for the area of storage of the cloud-based storage system; and storing, by the first storage controller, a first identifier for the first lease in a predefined portion of the area of storage, where the predefined portion of the area of storage is accessible to a second storage controller.

Techniques are provided for latency-based detection of storage volume type. One method comprises sending read commands using a predefined read command sequence to a recipient storage volume, wherein the predefined read command sequence specifies a request size and/or an offset of at least two of the read commands, and wherein an entity associated with a recipient storage volume of a predefined storage volume type is configured to insert a predefined delay before sending a response to at least one of the read commands when the entity detects the predefined read command sequence; evaluating whether the response to at least one of the read commands comprises the predefined delay; and determining whether the recipient storage volume is the predefined storage volume type based on a result of the evaluating. The recipient storage volume may comprise a storage volume and/or a storage data client that exposes a virtual storage volume.

A technique manages a computing system based on a client/server architecture. In particular, an address mapping of a storage system is managed. The address mapping includes an association between storage spaces in a plurality of storage devices in the storage system and a user of the storage system. A data access service is provided to a client associated with the user based on the address mapping. The client includes at least any one of a user data client for accessing user data associated with the user in the storage system and a control data client for accessing control data associated with the user. Based on a client/server architecture, a uniform management mode is provided for user data and control data, so that the storage system is managed more simply and effectively.

A method includes: receiving, by a storage device from a core in a host, a request to provide exclusive resource to a command of a predefined submission queue of a non-volatile memory (NVM) set in the storage device, wherein the request pertains to operating the NVM set in a deterministic state; generating a virtual NVM set identifier for a virtual NVM set based on a predefined mapping of the predefined submission queue and the NVM set; determining a storage controller associated with the NVM set based on a predefined mapping of the predefined submission queue, the NVM set, and the virtual NVM set identifier; enabling at least one core to operate in a Predictable Latency Mode; and operating the storage controller and the NVM set in the deterministic state by allocating predetermined resources to execute the command and return data with a predictable latency.