Pure Storage, Inc.

Symantec Operating Corporation

Veritas Operating Corporation

Symantec Corporation

Symantec Operating Company

John Colgrove

Ethan L Miller

John Martin Hayes

Ronald S Karr

Oleg Kiselev

Bo Hong

Cary A Sandvig

Feng Wang

Craig Harmer

David A Grunwald

Anand A Kekre

Robert H Lee

Christopher Golden

John D Davis

Constantine P Sapuntzakis

Peter Vajgel

Joseph S Hasbani

Par Botes

Jianting Cao

Naveen Neelakantam

Peter E Kirkpatrick

Sergey Zhuravlev

Lydia Mai Do

Igor Ostrovsky

Thomas Gill

Ron Karr

Andrew R Bernat

Graham Bromley

Joshua Robinson

Thomas Lanzatella

Blaine T Cuykendall

Taher Vohra

Neil A Vachharajani

Matthew Paul Fay

Vinay Perneti

Terence W Noonan

Grigori Inozemtsev

Joshua Freilich

Aswin Karumbunathan

Alan Stuart Driscoll

Steven P Hodgson

Malcolm Sharpe

Allen Unueco

Ganesh Ramanarayanan

Steve Hodgson

Patrick D Lee

Kunal Trivedi

Niranjan Sanjiv Pendharkar

Roland Dreier

Benjamin Scholbrock

Steven Michael Umbehocker

Daquan Zuo

Andrew Kleinerman

Xiaohui Wang

Charles Silvers

Martin Harriman

Marco Sanvido

Timothy W Brennan

Mark L McAuliffe

Raghu Krishnamurthy

Benjamin P Borowiec

Joshua P Robinson

Larry Touchette

Brian Gold

Ankur P Panchbudhe

Connor Brooks

Zoheb Shivani

Luke Paulsen

Deepak Tawri

Lawrence Mertes

Deepak Chawla

Joern W Engel

Hari Kannan

Ying Gao

Chirag Deepak Dalal

Richard A Hankins

Angshuman Bezbaruah

Yuhong Mao

Vaijayanti Rakshit Bharadwaj

Boris Feigin

Pradip Kulkarni

Robert Baird

Vikas Gupta

Samir Desai

Logan Jennings

Aaron Dailey

Andrew Miller

Andrew Kutner

Wei Zhang

Weibao Wu

Milind Vithal Borate

Gordon James Coleman

Dhrubajyoti Borthakur

Michael E Root

Kalaivani Arumugham

Damian Pablo Yurzola

Poonam P Dhavale

Neil Buda Vachharajani

Scott Douglas Kaiser

Intra-block error correction including generating reconstructed sub-portions of a portion of a dataset that is distributed into a plurality of portions that are stored on different storage devices of the storage system, wherein the dataset indicates a first number of errors that is greater than a second number of parity data portions of the dataset, determining that a sub-portion of the dataset does not match a corresponding reconstructed sub-portion of the dataset; and based on the determination, replacing the sub-portion of the dataset with the reconstructed sub-portion of the dataset.

Using intra-block redundancy calculations

Synchronous replication between storage systems with virtualized storage includes: assigning a virtual volume datastore to a pod, the pod including a management object, the virtual volume datastore including virtual machine data; stretching the pod from a first storage system to a second storage system, including copying the virtual machine data from the first storage system to the second storage system; and synchronously replicating access operations of the virtual machine data of the pod between the first and second storage systems.

Virtual volume-based replication

A uniform model for distinct types of data replication, including receiving, at a source data repository, an update to a dataset; generating, based on the update to the dataset, both metadata describing the update to the dataset and also a metadata representation of the dataset; and initiating, based on the same metadata describing the update to the dataset and also based on the same metadata representation of the dataset, either a first type of data replication or a second type of data replication from among a plurality of types of data replication.

Uniform model for distinct types of data replication

A computer system comprising: a data storage medium comprising a plurality of storage devices configured to store data; and a data storage controller coupled to the data storage medium; wherein the data storage controller is configured to: determine a target number of storage devices in a group of storage devices in a storage system that may exhibit variable I/O response times; detect one or more conditions associated with the group of storage devices; and after detecting the one or more conditions, change the target number of storage devices that may exhibit variable I/O response times.

Balancing the number of read operations and write operations that may be simultaneously serviced by a storage system

Selecting storage resources based on data characteristics, including: determining, for data that is stored within a storage system that includes multiple types of data storage, a storage type to use for the data, wherein: the data is associated with one more snapshots that are stored in the storage system, and the determination is based on whether the data that is stored in at least one volume in the storage system, wherein one storage type is selected if the data is stored in at least one volume and another storage type is selected if the data is not stored in at least one volume; and storing the data in a storage device associated with the determined storage type.

Selecting storage resources based on data characteristics

Utilizing multiple redundancy schemes within a unified storage element, including: receiving, in a storage system at a unified storage element that integrates both fast durable storage and bulk durable storage, a data storage operation from a host computer; storing, in accordance with a first data resiliency technique that corresponds to a RAID N+R format, data corresponding to the data storage operation within the fast durable storage of the unified storage element; and responsive to determining that the complete RAID stripe has been written to the fast durable storage, moving a portion of the stored data from the fast durable storage to the bulk durable storage of the unified storage element, the bulk durable storage storing the data in accordance with a second data resiliency technique that corresponds to a RAID M+R format, wherein M is different from N.

Maintaining multiple redundancy schemes across different storage types

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 method for implementing deduplication process based on performance analyses. The system may include a processing device to determine a first performance metric associated with retrieving a second stored data block that is within a specified range of a duplicate of the first data block and a second performance metric associated with retrieving a hash value corresponding to the second stored data block. The processing device further to retrieve the second stored data block within a specified range of the duplicate of the first data block in response to the first performance metric not exceeding the second performance metric.

Deduplication selection and optimization

A system with storage memory and a processing device has a logical deletion to physical erasure time bound. The system dereferences data, responsive to a direction to delete the data. The system monitors physical blocks in storage memory for live data and the dereferenced data. The system cooperates garbage collection with monitoring the physical blocks, so that at least a physical block having the dereferenced data is garbage collected and erased within a logical deletion to physical erasure time bound.

Guaranteeing physical deletion of data in a storage system

Writing data in a storage system that includes a first type of storage device and a second type of storage device, including: selecting, for one or more unprocessed write requests, a target storage device type from the first type of storage device and the second type of storage device; issuing a first group of write requests to the first type of storage device, the first group of write requests addressed to one or more locations selected in dependence upon an expected address translation to be performed by the first type of storage device; and issuing a second group of write requests to the second type of storage device, the second group of write requests addressed to one or more locations selected in dependence upon a layout of memory in the second type of storage device.

Targeted i/o to storage devices based on device type

Prioritizing highly performant storage systems for servicing a synchronously replicated dataset: detecting a communication fault between two or more storage systems that are synchronously replicating a dataset; identifying a preferred storage system for winning mediation, including determining that the preferred storage system winning mediation would result in better performance than other storage systems winning mediation; and requesting, by the preferred storage system, mediation from a mediation target.

Performance-based prioritization for storage systems replicating a dataset

A first set of physical units of a storage device of a storage system is selected for performance of low latency access operations, wherein other access operations are performed by remaining physical units of the storage device. A determination as to whether a triggering event has occurred that causes a selection of a new set of physical units of the storage device for the performance of low latency access operations is made. A second set of physical units of the storage device is selected for the performance of low latency access operations upon determining that the triggering event has occurred.

Performing low latency operations using a distinct set of resources

A system and method for managing tables in a storage system is described.

Flash system having multiple fingerprint tables

Data protection in a storage system that includes a plurality of Non-Volatile Memory Express ('NVMe') Solid State Drives (‘SSDs’), including: retrieving, from a plurality of NVMe SSDs (‘Non-Volatile Memory Express Solid State Drives’) of a storage system, one or more unencrypted shares of a master secret; reconstructing the master secret using the shares of the master secret; decrypting one or more encrypted device keys using the master secret; and using the decrypted device keys to perform a plurality of accesses to one or more of the NVMe SSDs.

Encrypting data in a storage device

Dynamically adjusting an amount of log data generated for a storage system that includes a plurality of storage devices, including: detecting that a value for a performance-related characteristic of a component of a storage system has reached a performance threshold, and based on the detection, changing an extent to which log data should be generated for the component.

Log data generation based on performance analysis of a storage system

Growing community of inventors

Los Altos, CA, United States of America

John Colgrove