Pure Storage, Inc.

Joshua Freilich

Naveen Neelakantam

Aswin Karumbunathan

Ronald S Karr

John Colgrove

Constantine P Sapuntzakis

Sergey Zhuravlev

Radek Aster

Mohit Gupta

Grigori Inozemtsev

Arun Theebaprakasam

Swapnil Chandrashekhar Nagle

Manpreet Singh

Neelesh Thakur

Riley Thomasson

Par Botes

Kiron Vijayasankar

Andrew Kleinerman

Dynamic scaling of a virtual storage system, including: detecting, within one or more virtual components of the virtual storage system, a change in performance; determining, in response to the detected change in performance, a scaling response based on the virtual storage system meeting one or more target performance metrics; and scaling, based on one or more available virtual components of the virtual storage system, up or down such that performance of the virtual storage system is in accordance within the one or more target performance metrics.

Performance-based scaling of a virtual storage system

Determining active membership among a set of storage systems, including: determining, by a cloud-based storage system among the set of storage systems, that a membership event corresponds to a change in membership to the set of storage systems synchronously replicating the dataset; applying, in dependence upon the membership event, one or more membership protocols to determine a new set of storage systems to synchronously replicate the dataset; and for one or more I/O operations directed to the dataset, applying the one or more I/O operations to the dataset synchronously replicated by the new set of storage systems.

Directing I/O to an active membership of storage systems

Data recovery in a virtual storage system, including: detecting, within storage provided by a first tier of storage of the virtual storage system, data loss within a dataset, wherein recovery data for the dataset is stored in a second tier of storage; determining a recovery point for the dataset up to which a consistent version of the dataset is recoverable from the recovery data stored in the second tier of storage; and restoring, within the storage provided by the first tier of storage of the virtual storage system, the consistent version of the dataset.

Recovering data in a virtual storage system

Reconfiguring a storage system based on resource availability, including: limiting a number of storage devices in a storage system that may be simultaneously servicing write operations; determining that an amount of required write bandwidth has changed; and subsequent to determining that the amount of required write bandwidth has changed, adjusting, by a computer processor, the number of storage devices in the storage system that may be simultaneously servicing write operations.

Storage system reconfiguration based on bandwidth availability

A method of providing block-based storage is described. The method comprises: creating a virtual storage system for storing a dataset, the virtual storage system including a virtual drive layer that includes a plurality of virtual drives for storing at least a portion of the dataset as block data; and a block storage backend layer for storing at least the portion of the dataset as block data, the block storage backend layer including one or more block-based storage devices; receiving an I/O operation with respect to the dataset; and based on the received I/O operation, storing, in the block storage backend layer, an update to the dataset.

Providing block-based storage

Synchronously replicating a dataset across cloud-based storage systems, including adding a cloud-based storage system to a set of storage systems that the dataset is synchronously replicated across, where access operations are applied to the dataset equivalently through all storage systems in the set, all storage systems in the set store a separate copy of the dataset, and operations to modify the dataset performed and completed through any of the storage systems in the set are reflected in access operations to read the dataset, the cloud-based storage system including one or more cloud computing instances executing a storage controller application, a virtual drive layer that includes one or more cloud computing instances with local storage for storing at least a portion of the dataset as block data, and an object storage layer for storing at least a portion of the dataset as object data.

Replication utilizing cloud-based storage systems

Taking recovery actions for replicated datasets, including: determining whether a request to modify a dataset that is synchronously replicated among a plurality of storage systems has been applied on a particular storage system of the plurality of storage systems, wherein the plurality of storage systems is synchronously replicating the dataset by acknowledging the request as being complete when each storage system has modified its copy of the dataset; and applying a recovery action based on whether the request to modify the dataset has been applied on the particular storage system of the plurality of storage systems.

Taking recovery actions for replicated datasets

A first read request for data stored at a non-volatile memory is received by a primary storage controller. The data is programmed from the non-volatile memory to a first cache of the primary storage controller, the first cache to store the data over a first time range. A second read request is received for the data. In response to receiving the second read request for the data, the data is programmed to a second cache to store the data over a second time range that is greater than the first time range. A notification is transmitted to a secondary storage controller, the notification including information associated with the programming of the data to the second cache.

Tiered caching of data in a storage system

Examining a cloud-based storage system using codified states includes generating an enumeration of a plurality of resources of the cloud-based storage system; comparing the enumeration to a codified state for the cloud-based storage system; and identifying, based on the comparison, a difference between the enumeration and the codified state.

Examining a cloud-based storage system using codified states

Leveraging distinct storage tiers in a virtual storage system, including: receiving a request to write data to the virtual storage system; selecting, from amongst a plurality of tiers in the virtual storage system, a tier for receiving the data, wherein the plurality of tiers include a write-mostly tier and at least one other tier; and storing, within the selected tier within the virtual storage system, the data.

Leveraging distinct storage tiers in a virtual storage system

Restoring a cloud-based storage system to a selected state, including: generating, over a period of time, one or more snapshot states of a cloud-based storage system, wherein each of the one or more snapshot states describes a respective configuration of the cloud-based storage system at a respective point in time within the period of time; providing, to a computing process, one or more selectable states corresponding to the one or more snapshot states of the cloud-based storage system; and transitioning, in response to a selection of a particular snapshot state from among the one or more snapshot states, the configuration of the cloud-based storage system from a current state to the particular snapshot state.

Restoring a cloud-based storage system to a selected state

Reverting between codified states in a cloud-based storage system, including: generating, in response to receiving a request to change a configuration of the cloud-based storage system to an updated state, a snapshot state of a current state of the cloud-based storage system; transitioning the configuration of the cloud-based storage system from the snapshot state to a next state toward the updated state; and reverting, in response to not configuring the cloud-based storage system in accordance with the updated state, configuration of the cloud-based storage system from the next state to the snapshot state.

Reverting between codified states in a cloud-based storage system

Coalescing write operations in a cloud-based storage system including receiving, from a storage controller application of the cloud-based storage system, a first plurality of write operations, wherein each of the first plurality of write operations comprises a respective write to a storage volume; coalescing the first plurality of write operations into a plurality of coalesced write operations, wherein each of the coalesced write operations are configured to effect two or more of the first plurality of write operations; and performing the plurality of coalesced write operations on the storage volume.

Servicing write operations in a cloud-based storage system

A cloud-based storage system within a cloud computing environment, the cloud-based storage system including: monitoring, for the cloud-based storage system, one or more storage system operations, wherein the cloud-based storage system includes a virtual instance storage layer and a cloud-based storage layer; determining, based at least upon the one or more storage system operations, one or more access patterns for the cloud-based storage system; and modifying, based at least upon the one or more access patterns for the cloud-based storage system, one or more cloud configurations for the cloud-based storage system.

Scaling a cloud-based storage system in response to a change in workload

Using Infrastructure-as-Code ('IaC') to update a cloud-based storage system, including: monitoring one or more performance metrics associated with a cloud-based storage system; generating, based on the performance metrics, a configuration template for the cloud-based storage system, wherein the configuration template specifies a target state for the cloud-based storage system; and updating the cloud-based storage system using the configuration template.

Growing community of inventors

San Francisco, CA, United States of America

Joshua Freilich