Synchronous replication
First Claim
1. A method comprising:
- receiving a replication operation, corresponding to a replication of a write operation received by a first device for implementation upon a storage object hosted by the first device, for implementation upon a replication storage object hosted by a second device;
receiving a retry replication operation, before receiving the replication operation, corresponding to a retry of the replication operation triggered in response to a lifecycle of the write operation indicating that the replication operation has not been implemented by the second device;
implementing the retry replication operation upon the replication storage object; and
avoiding implementing the replication operation based upon successful implementation of the retry replication operation.
0 Assignments
0 Petitions
Accused Products
Abstract
One or more techniques and/or computing devices are provided for synchronous replication. For example, synchronous replication relationships are established between a first storage object (e.g., a file, a logical unit number (LUN), a consistency group, etc.), hosted by a first storage controller, and a plurality of replication storage objects hosted by other storage controllers. In this way, a write operation to the first storage object is implemented in parallel upon the first storage object and the replication storage objects in a synchronous manner, such as using a zero-copy operation to reduce overhead otherwise introduced by performing copy operations. Reconciliation is performed in response to a failure so that the first storage object and the replication storage objects comprise consistent data. Failed write operations and replication write operations are retried, while enforcing a single write semantic. Dependent write order consistency is enforced for dependent write operations, such as overlapping write operations.
-
Citations
19 Claims
-
1. A method comprising:
-
receiving a replication operation, corresponding to a replication of a write operation received by a first device for implementation upon a storage object hosted by the first device, for implementation upon a replication storage object hosted by a second device; receiving a retry replication operation, before receiving the replication operation, corresponding to a retry of the replication operation triggered in response to a lifecycle of the write operation indicating that the replication operation has not been implemented by the second device; implementing the retry replication operation upon the replication storage object; and avoiding implementing the replication operation based upon successful implementation of the retry replication operation. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17)
-
-
18. A non-transitory machine readable medium having stored thereon machine executable code which when executed by a machine, causes the machine to:
-
receive a replication operation, corresponding to a replication of a write operation received by a first device for implementation upon a storage object hosted by the first device, for implementation upon a replication storage object hosted by a second device; receive a retry replication operation, before receiving the replication operation, corresponding to a retry of the replication operation triggered in response to a lifecycle of the write operation indicating that the replication operation has not been implemented by the second device; implement the retry replication operation upon the replication storage object; and avoid implementing the replication operation based upon successful implementation of the retry replication operation. - View Dependent Claims (19)
-
Specification