Pure Storage, Inc.

Netapp, Inc.

Arun Rokade

Ronald S Karr

Deepak Chawla

Ethan L Miller

David A Grunwald

Jeffrey S Kimmel

Ling Zheng

Taher Vohra

Kayuri Hasmukh Patel

Anshul Pundir

Long Yang

Suhas Prakash

Initiating recovery actions when a dataset ceases to be synchronously replicated across a set of storage systems, including: receiving, by at least one storage system among a plurality of storage systems implementing a symmetric input/output model for a synchronously replicated dataset, a request to modify the dataset; identifying one or more operations associated with the request to modify the dataset that have not been applied to at least one storage system of the plurality of storage systems; and responsive to a system fault among the plurality of storage systems synchronously replicating the dataset, applying a recovery action based on recovery information that identifies one or more operations that have not been applied to the plurality of storage systems.

Initiating recovery actions when a dataset ceases to be synchronously replicated across a set of storage systems

A system may include a plurality of storage systems each configured to operate in accordance with a synchronous replication configuration in which a dataset is synchronously replicated to each of the plurality of storage systems such that each of the plurality of storage systems stores and continually updates a different copy of the dataset. Each of the storage systems may be configured to independently monitor, while operating in accordance with the synchronous replication configuration, for security threats against one of the copies of the dataset; and perform, when the monitoring indicates that the one of the copies of the dataset is possibly being targeted by a security threat, a remedial action with respect to the security threat.

Independent security threat detection and remediation by storage systems in a synchronous replication arrangement

An illustrative method includes determining, by a data protection system, that a dataset stored by a first storage system is possibly being targeted by a security threat while a data synchronization setting for the first storage system is enabled such that the dataset stored by the first storage system is synchronously replicated to a second storage system; and disabling, by the data protection system based on the determining that the dataset stored by the first storage system is possibly being targeted by the security threat, the data synchronization setting to prevent the dataset stored by the first storage system from being synchronously replicated to the second storage system.

Selective control of a data synchronization setting of a storage system based on a possible ransomware attack against the storage system

Recovery for storage systems synchronously replicating a dataset, including: receiving, by at least one storage system among the plurality of storage systems synchronously replicating the dataset, a request to modify the dataset; generating recovery information indicating whether the request to modify the dataset has been applied on all storage systems in the plurality of storage systems synchronously replicating the dataset; and responsive to a system fault, applying a recovery action in dependence upon the recovery information indicating whether the request to modify the dataset has been applied on all storage systems in the plurality of storage systems synchronously replicating the dataset.

Recovery for storage systems synchronously replicating a dataset

A technique efficiently creates a snapshot for a logical unit (LUN) served by a storage input/output (I/O) stack executing on a node of a cluster that organizes data as extents referenced by keys. In addition, the technique efficiently creates one or more snapshots for a group of LUNs organized as a consistency group (CG) and served by storage I/O stacks executing on a plurality of nodes of the cluster. To that end, the technique involves a plurality of indivisible operations (i.e., transactions) of a snapshot creation workflow administered by a Storage Area Network (SAN) administration layer (SAL) of the storage I/O stack in response to a snapshot create request issued by a host. The SAL administers the snapshot creation workflow by initiating a set of transactions that includes, inter alia, (i) installation of barriers for LUNs (volumes) across all nodes in the cluster that participate in snapshot creation, (ii) creation of point-in-time (PIT) markers to record those I/O requests that are included in the snapshot, and (iii) updating of records (entries) in snapshot and volume tables of a cluster database (CDB).

Growing community of inventors

Fremont, CA, United States of America

Arun Rokade