Netapp, Inc.

Andrew Eric Dunn

Rithin Kumar Shetty

Akhil Kaushik

Ripulkumar Hemantbhai Patel

Vrishali Dattatray Hajare

Yi Yang

Susan M Coatney

Yong Cho

Chaitanya V Patel

Vani Vully

Anuja Jaiswal

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 utilizing a tracking structure for data replication synchronization. For example, a first storage controller, hosting first storage, may have a replication relationship with a second storage controller hosting second storage (e.g., write requests, modifying the first storage, may be replicated to the second storage). The first storage controller maintains a tracking structure comprising hash buckets, dynamic tree structures, and/or a tracking segment bitmap used to identify portions of the first storage as either comprising dirty data (e.g., data, modified by a write request not yet replicated to the second storage, that may be different than corresponding data within the second storage) or clean data (e.g., the same data as the second storage). The tracking structure may be used to resynchronize the second storage to the first storage, perform a quick resync, facilitate semi-synchronous replication, and/or perform snapshot-less resync.

Tracking structure for data replication synchronization

A system and method for avoiding object identifier collisions in a cluster environment is provided. Upon creation of the cluster, volume location databases negotiate ranges for data set identifiers (DSIDs) between a first site and a second site of the cluster. Any pre-existing objects are remapped into an object identifier range associated with the particular site hosting the object.

System and method for avoiding object identifier collisions in a peered cluster environment

Growing community of inventors

Sunnyvale, CA, United States of America

Andrew Eric Dunn