Pure Storage, Inc.

Intel Corporation

Naveen Neelakantam

Aswin Karumbunathan

Ronald S Karr

Joshua Freilich

Taher Vohra

John Colgrove

Constantine P Sapuntzakis

Sergey Zhuravlev

Marco Sanvido

Mark L McAuliffe

Neil A Vachharajani

Luis Pablo Pabón

Ethan L Miller

Yuval Frandzel

Richard A Hankins

Denis M Khartikov

Christopher Golden

John H Kelm

Yanwei Jiang

David A Grunwald

Ivan Jibaja

Matthew Paul Fay

Connor Brooks

Zoheb Shivani

Polychronis Xekalakis

Kunal Trivedi

Joern W Engel

Par Botes

David Pardo Keppel

Radek Aster

Thomas Gill

Xiaohui Wang

Gregory McNutt

Peter E Kirkpatrick

Kiron Vijayasankar

Fernando Latorre

Arun Theebaprakasam

Grigori Inozemtsev

Jaroslaw Topp

Neil Buda Vachharajani

Nidhi Pankaj Doshi

James Fisher

Swapnil Chandrashekhar Nagle

Neelesh Thakur

Scott Chao

HuiHui Cheng

Bo Feng

Junming Zhu

Michael Goldsby

Gunjan Dang

Huihui Cheng

Naveen Kumar

H Peter Anvin

Niranjan L Cooray

Roland Dreier

Joshua B Fryman

Michael Zelikson

Grigorios Magklis

Benjamin Scholbrock

Pedro Lopez

Sebastian Winkel

Ethan Schuchman

Marc Lupon

Raul Martinez

Allan Douglas Knies

Patrick P Lai

Vjekoslav Svilan

Demos Pavlou

Georgios Tournavitis

Kelvin Kwan

Norbert Unger

Brandon Davis

Varun Mohandru

Rupert Brauch

Li-Gao Zei

Rami May

Gregor Stellpflug

Thang Vu

Ori Lempel

Michael Neilly

Thomas Gaertner

Mirem Hyuseinova Seidahmedova

Nirajan L Cooray

Pete Kirkpatrick

Gregory Schultz

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

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.

Providing application-side infrastructure to control cross-region replicated object stores

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

Systems and methods for orchestrating coordinated snapshots across distinct storage environments are disclosed. The methods include steps for determining, for storage systems storing portions of a dataset, that a local checkpoint at a storage system of the storage systems meets dependency requirements for a coordinated checkpoint of the dataset relative to another local checkpoint at another storage system of the storage systems while storage operations are being applied to the dataset, and based on the determination, orchestrating the coordinated checkpoint.

Orchestrating coordinated snapshots across distinct storage environments

Establishing a guarantee for maintaining a replication relationship between object stores during a communications outage, an embodiment including identifying, by a first storage system, respective local clock values of one or more second storage systems, wherein the first storage system and the one or more second storage systems are among a plurality of storage systems replicating an object store, wherein the plurality of storage systems are configured to receive requests directed to the replicated object store; determining, by the first storage system in dependence upon the respective local clock values, respective clock differences of the one or more second storage systems relative to the first storage system; and ordering, by the first storage system, one or more updates to the replicated object store in dependence upon the respective clock differences.

Establishing a guarantee for maintaining a replication relationship between object stores during a communications outage

An illustrative method includes receiving, by a container storage interface (CSI) filter driver executing on a node of a cluster managed by a container orchestrator, a request to deploy a containerized application; selecting, by the CSI filter driver based on one or more attributes of the containerized application, a storage system from a plurality of storage systems attached to a plurality of clusters managed by the container orchestrator; and transmitting, by the CSI filter driver, a command to a CSI driver executing on a node of a cluster to which the storage system is attached, the cluster included in the plurality of clusters, the command configured to direct the CSI driver to provision a volume on the storage system for use with the containerized application.

Container storage interface filter driver-based determination of optimal storage system to provide storage for a containerized application deployment

An illustrative method includes receiving, by a container storage interface (CSI) filter driver, a request provided by a source for a CSI driver associated with a storage system to perform a control plane operation with respect to the storage system, wherein the CSI filter driver and the CSI filter execute on a node of a cluster managed by a container orchestrator, and wherein the storage system is configured to store data associated with one or more containerized applications executing on the node; performing, by the CSI filter driver in response to receiving the request, an access control operation with respect the request; and allowing, by the CSI filter driver, the CSI driver to perform the control plane operation when the access control operation determines that the source is authorized to initiate the control plane operation.

Container storage interface filter driver-based security for a storage system

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.

Metadata-based recovery of a dataset

Sizing a virtual storage system, including: determining a change to one or more resource demands; determining, based on the change to the one or more resource demands, one or more modifications to one or more virtual components included as part of a virtual storage system architecture of a virtual storage system within a cloud computing environment; and initiating, responsive to the change to the one or more resource demands, the one or more modifications to the one or more virtual components included as part of the virtual storage system architecture of the virtual storage system, including replacing one or more of the virtual components with a higher performance virtual component.

Sizing a virtual storage system

An illustrative method may include passing, by a container storage interface (CSI) filter driver, requests received by way of a node agent to a CSI driver associated with a storage system, the requests comprising requests for the CSI driver to perform control plane operations with respect to the storage system, wherein the node agent, the CSI filter driver, and the CSI filter all execute on a node of a cluster managed by a container orchestrator, and wherein the storage system is configured to store data associated with one or more containerized applications executing on the node; identifying, by the CSI filter driver based on the requests, attributes associated with the control plane operations; determining, by the CSI filter driver based on the attributes, a usage profile associated with the storage system; and performing, by the CSI filter driver based on the usage profile, an optimization operation.

Container storage interface filter driver-based optimization of a storage system

Replicating multiple storage systems utilizing coordinated snapshots, including identifying a replica dataset stored across two or more target storage systems, wherein the replica dataset is a replication target for a source dataset stored across two or more source storage systems; identifying two or more local replicated checkpoints that are replicated from the two or more source storage systems to the two or more target storage systems, wherein two or more local source checkpoints for the two or more local replicated checkpoints are associated with a coordinated source checkpoint for the source dataset; and determining, based on the two or more local replicated checkpoints, a coordinated target checkpoint for the replica dataset.

Replicating multiple storage systems utilizing coordinated snapshots

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

Determining storage consumption in group of storage resources, including for the group of data units within a group of storage resources: for each data unit in the group of data units, determining whether the data unit is associated with one or more client entities; and for each data unit associated with one or more client entities, determining a category for the data unit; calculating storage consumption for a client based on the category of each data unit; and reporting the calculated storage consumption.

Calculating storage utilization for distinct types of data

A system and method of uniform sampling in an append-only database to determine temporal distribution of data.

Data stability in data storage system

Managing disaster recovery to a cloud computing environment, including: receiving recovery objectives associated with a dataset that is stored in a primary storage system; creating a cloud-based storage system; suspending the cloud-based storage system; and resuming, periodically and based on the recovery objectives, the cloud-based storage system, including refreshing a copy of the dataset that is maintained by the cloud-based storage system.

Managing disaster recovery to cloud computing environment

Growing community of inventors

Mountain View, CA, United States of America

Naveen Neelakantam