Pure Storage, Inc.

Thomas Gill

David A Grunwald

Ronald S Karr

John Colgrove

Connor Brooks

Luke Paulsen

Larry Touchette

Zoheb Shivani

Kunal Trivedi

Saurabh Shukla

Yao-cheng Tien

Naveen Neelakantam

Aswin Karumbunathan

Alan Stuart Driscoll

Matthew Paul Fay

Lawrence Mertes

Claudiu Schmidt

Verifying that data has been correctly replicated to a replication target, including: replicating a dataset stored at a first computing system to a second computing system; and determining, based at least on a comparison of a first hash and a second hash, validity of the dataset stored at the second computing system, wherein the first hash is generated by applying a hash function to a copy of the dataset that is stored at the first computing system and the second hash is generated by applying the hash function to a copy of the dataset that is stored at the second computing system.

Validating integrity of replicated data

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.

Optimizing availability of mediator services for storage systems

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

Transitioning between replication sources for data replication operations, including: delaying a transition from using a first data repository as a source for data replication to using a second data repository as the source for data replication after detecting that one or more storage operations directed to the first data repository have not been replicated to the second data repository; and promoting the second data repository as the source for data replication such that storage operations received after completing the transition are directed to the second data repository.

Transitioning between source data repositories for a dataset

Continuing to service a dataset after prevailing in mediation, including: requesting, by a first storage system, mediation from a mediation service that is configured to resolve which storage system continues to service a dataset after the triggering event, wherein the dataset is synchronously replicated by a plurality of storage systems that includes the first storage system and a second storage system; and detaching the second storage system from a plurality of storage systems synchronously replicating the dataset.

Continuing to service a dataset after prevailing in mediation

A storage system switching between mediation models within a storage system, where the switching between mediation models includes: determining, among one or more of the plurality of storage systems, a change in availability of a mediator service, wherein one or more of the plurality of storage systems are configured to request mediation from the mediator service in response to a fault; and communicating, among the plurality of storage systems and responsive to determining the change in availability of the mediator service, a fault response model to be used as an alternate to the mediator service among one or more of the plurality of storage systems.

Fault response model management in a storage system

Verifying data has been correctly replicated to a replication target

Creating a modifiable cloned image of a dataset, including: generating, based on a dataset stored within a source data repository, a tracking copy of replica data on a target data repository; generating, after receiving an indication to begin accepting modifications to the tracking copy of the replica data, a cloned image of the dataset that is modifiable without modifying the tracking copy of the replica data; and responsive to a storage operation directed to the target data repository, modifying the cloned image of the dataset without modifying the tracking copy of the replica data.

Creating a modifiable cloned image of a dataset

A method of managing host mappings for replication endpoints, the method including: identifying a target storage system replicating a source dataset of a source storage system, wherein a first host is mapped to the source dataset on the source storage system; providing, to the target storage system and in dependence upon a mapping of the first host to the source dataset, configuration information for connecting to a second host; and implementing, in response to a triggering event, a mapping of the second host to a replica dataset on the target storage system.

Managing host mappings for replication endpoints

Managing storage systems that are synchronously replicating a dataset, including: detecting a change in membership to the set of storage systems synchronously replicating the dataset; and applying one or more membership protocols to determine a new set of storage systems to synchronously replicate the dataset, wherein the one or more membership protocols include a quorum protocol, an external management protocol, or a racing protocol, and wherein one or more I/O operations directed to the dataset are applied to a new set of storage systems.

Growing community of inventors

BURY ST EDMUNDS, United Kingdom

Thomas Gill