Netapp, Inc.

Salesforce Com, Inc.

Network Appliance, Inc.

Rithin Kumar Shetty

Andrew Eric Dunn

Akhil Kaushik

Yuedong Mu

Pranab Patnaik

Ripulkumar Hemantbhai Patel

Vrishali Dattatray Hajare

Nagender Somavarapu

Yi Yang

Venkateswararao Jujjuri

Devang Kundanlal Shah

Andrey Yegorov

Ching-Yuk Paul Ngan

Pawan Saxena

David W Minnich

Preethi Gopaulakrishnan

Paul Lockwood

Alan Stuart Driscoll

Stephen Wu

David Brittain Bolen

Jose Mathew

Vikas Yadav

Brian Christopher Parkison

Amol Chitre

Kiran Kumar Modukuri

Vishwajith Shivappa

Guillermo Roa

Aditya Toomula

Anudhar Emani

Adarsh Seetharam

A system and method for efficiently restoring one or more data containers is provided. A common persistent consistency point image (PCPI) is identified between a source and a destination storage systems prior to the destination storage system performing a rollback operation to the commonly identified PCPI. Differential data is then transmitted from the source storage system in a line efficient manner to the destination storage system.

System and method for efficient block level granular replication

One or more techniques and/or computing devices are provided for snapshot creation. For example, a request may be received to create a snapshot of a first storage object, hosted by a first storage controller, having a synchronous replication relationship with a second storage object hosted by a second storage controller. A coordinator workflow is initialized to issue a drain and hold request to a splitter. Responsive to an indication that the splitter has stopped processing and started queuing incoming write operations and has drained current write operations based upon the drain and hold request, snapshot creation requests are sent to the first storage controller and the second storage controller. Responsive to the first storage controller creating a first snapshot of the first storage object and the second storage controller creating a second snapshot of the second storage object, the splitter may be resumed to process write operations.

Snapshot creation with synchronous replication

One or more techniques and/or computing devices are provided for replicating virtual machine disk clones. For example, a first storage controller, hosting first storage, may have a synchronous replication relationship with a second storage controller hosting second storage. A virtual machine, within the first storage, may be specified as having synchronous replication protection. Accordingly, virtual machine disk clones of a virtual machine disk of the virtual machine may be replicated from the first storage to the second storage. For example, virtual machine disk clones may be synchronous replicated, replicated by a resync process invoked by a hypervisor agent, and/or stored and replicated from a clone backup directory.

Cloned virtual machine disk replication

One or more techniques and/or computing devices are provided for resynchronization. For example, a request may be received to create pseudo snapshots of a first consistency group, hosted by a first storage controller, and a second consistency group, hosted by a second storage controller, having a synchronous replication relationship with the first consistency group. Incoming client write requests are logged within an intercept tracking log at the first storage controller. After a first drain without hold of incoming write requests is performed, a first pseudo common snapshot of the second consistency group is created. After a second drain without hold of incoming write operations is performed, a second pseudo common snapshot of the first consistency group and the intercept tracking log is created. The pseudo snapshots and the intercept tracking log (e.g., indicating a delta between the pseudo snapshots) are used to resynchronize the first and second consistency groups.

Low overhead resynchronization snapshot creation and utilization

One or more techniques and/or computing devices are provided for non-disruptively establishing a synchronous replication relationship between a primary volume and a secondary volume and/or for resynchronizing the primary volume and the secondary volume. For example, a baseline snapshot and one or more incremental snapshots of the primary volume are used to construct and incrementally update the secondary volume with data from the primary volume. A dirty region log is used to track modifications to the primary volume. A splitter object is used to split client write requests to the primary volume and to the secondary volume. A synchronous transfer engine session is initiated to processing incoming client write requests using the dirty region log. A cutover scanner is used to transfer dirty data from the primary volume to the secondary volume. In this way, a synchronous replication relationship is established between the primary volume and the secondary volume.

Non-disruptive baseline and resynchronization of a synchronous replication relationship

One or more techniques and/or computing devices are provided for moving a consistency group having a replication relation. For example, a first consistency group of storage objects (e.g., files, logical unit numbers (LUNs), etc.) within first storage may have a replication relationship with a second consistency group within second storage (e.g., the second consistency group is maintained as a synchronously replicated copy of the first consistency group). A volume copy operation, a single file move on demand command, a single file restore command, or other functionality is used to move the first consistency group from the first storage to third storage, such as for load balancing, to create a moved first consistency group within the third storage. A new replication relationship is established between the moved first consistency group and the second consistency group, and the moved first consistency group and the second consistency group are resynchronized.

Moving a consistency group having a replication relationship

Restoration process to restore corrupted data of a volume

In some embodiments, a server node may transmit metrics to a client piggy-backed on (appended to) responses to regular read/write requests. Other embodiments may be disclosed and/or claimed.

Dissemination of node metrics in server clusters

Growing community of inventors

Sunnyvale, CA, United States of America

Rithin Kumar Shetty