# US 2022/0035837 A1 · Timestamp consistency for synchronous replication

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0035837 A1
- Document ID: US20220035837A1
- Status: Published application
- Kind: A1
- Application number: 17/503,945
- Filed: 2021-10-18
- Published: 2022-02-03
- Earliest claimed: 2019-03-19
- Assignees: NetApp, Inc.
- Applicants: NetApp Inc.
- Inventors: Krishna Murthy Chandraiah setty Narasingarayanapeta; Rakesh Bhargava M.R.; Harsha Handral Sridhara
- Web page: https://patentgrep.com/patent/US20220035837A1

## CPC

- G06F 16/275: {Synchronous replication}
- G06F 3/0619: {in relation to data integrity, e.g. data losses, bit errors}
- G06F 3/065: {Replication mechanisms}
- G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]}
- G06F 16/2322: {using timestamps}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Techniques are provided for timestamp consistency. An operation targeting a first storage object having a synchronous replication relationship with a second storage object is intercepted. A timestamp is assigned to the operation. A replication operation is created as a replication of the operation. The same timestamp is assigned to the replication operation. The operation is implemented upon the first storage object and the replication operation is implemented upon the second storage object.

## Claims

### Claim 1

A method comprising:
hosting a file system operation handler on a first node for processing replication operations received from a second node;
reconfiguring the file system operation handler to assign timestamps, stored within replication operations, to storage objects upon which the replication operations are executed;
receiving, by the file system operation handler, a replication operation comprising a timestamp corresponding to a first point in time;
executing, by the file system operation handler, the replication operation upon a first storage object at a second point in time; and
assigning, by the file system operation handling, the timestamp, corresponding to the first point in time different than the second point in time at which the replication operation was executed, to the first storage object.

### Claim 2 (depends on 1)

The method of claim 1, wherein the reconfiguring comprises:
reconfiguring a default configuration of the file system operation handler to assign the timestamps, stored within the replication operations, to the storage objects upon which the replication operations are executed, wherein the default configuration corresponds to the file system operation handler assigning timestamps to the storage objects based upon times at which the replication operations are executed upon the storage objects.

### Claim 3 (depends on 1)

The method of claim 1, wherein the first point in time corresponds to a time at which an operation, of which the replication operation is a replica of, was previously executed upon a second storage object at the second node.

### Claim 4 (depends on 1)

The method of claim 1, comprising:
replicating operations executed upon the first storage object to the second node for execution upon a second storage object; and
refraining from replicating an operation to the second node based upon a result of the operation having a zero on-disk modification.

### Claim 5 (depends on 1)

The method of claim 1, comprising:
replicating operations executed upon the first storage object to the second node for execution upon a second storage object; and
refraining from replicating an operation to the second node based upon the operation having a zero payload.

### Claim 6 (depends on 1)

The method of claim 1, comprising:
sequentially replicating operations executed upon the first storage object to the second node for execution upon a second storage object based upon the operations having a file access permission policy flag.

### Claim 7 (depends on 1)

The method of claim 1, comprising:
replicating, in parallel, operations executed upon the first storage object to the second node for execution upon a second storage object based upon the operations without a file access permission policy flag.

### Claim 8

A non-transitory machine readable medium comprising instructions for performing a method, which when executed by a machine, causes the machine to:
reconfigure a file system operation handler on a first node to assign timestamps, stored within replication operations received from a second node, to storage objects upon which the replication operations are executed;
receive, by the file system operation handler, a replication operation comprising a timestamp corresponding to a first point in time;
execute, by the file system operation handler, the replication operation upon a first storage object at a second point in time; and
assign, by the file system operation handling, the timestamp, corresponding to the first point in time different than the second point in time at which the replication operation was executed, to the first storage object.

### Claim 9 (depends on 8)

The non-transitory machine readable medium of claim 8, wherein the instructions cause the machine to:
reconfigure a default configuration of the file system operation handler to assign the timestamps, stored within the replication operations, to the storage objects upon which the replication operations are executed, wherein the default configuration corresponds to the file system operation handler assigning timestamps to the storage objects based upon times at which the replication operations are executed upon the storage objects.

### Claim 10 (depends on 8)

The non-transitory machine readable medium of claim 8, wherein the first point in time corresponds to a time at which an operation, of which the replication operation is a replica of, was previously executed upon a second storage object at the second node.

### Claim 11 (depends on 8)

The non-transitory machine readable medium of claim 8, wherein the instructions cause the machine to:
replicate operations executed upon the first storage object to the second node for execution upon a second storage object; and
refrain from replicating an operation to the second node based upon a result of the operation having a zero on-disk modification.

### Claim 12 (depends on 8)

The non-transitory machine readable medium of claim 8, wherein the instructions cause the machine to:
replicate operations executed upon the first storage object to the second node for execution upon a second storage object; and
refrain from replicating an operation to the second node based upon the operation having a zero payload.

### Claim 13 (depends on 8)

The non-transitory machine readable medium of claim 8, wherein the instructions cause the machine to:
sequentially replicate operations executed upon the first storage object to the second node for execution upon a second storage object based upon the operations having a file access permission policy flag.

### Claim 14 (depends on 8)

The non-transitory machine readable medium of claim 8, wherein the instructions cause the machine to:
replicate, in parallel, operations executed upon the first storage object to the second node for execution upon a second storage object based upon the operations without a file access permission policy flag.

### Claim 15 (depends on 8)

The non-transitory machine readable medium of claim 8, wherein the instructions cause the machine to:
replicate operations executed upon the first storage object to the second node for execution upon a second storage object; and
replicate an operation to the second node based upon the operation performing an on-disk modification.

### Claim 16

A computing device comprising:
a memory comprising machine executable code for performing a method; and
a processor coupled to the memory, the processor configured to execute the machine executable code to cause the processor to:
reconfigure a file system operation handler on a first node to assign timestamps, stored within replication operations received from a second node, to storage objects upon which the replication operations are executed;
receive, by the file system operation handler, a replication operation comprising a timestamp corresponding to a first point in time;
execute, by the file system operation handler, the replication operation upon a first storage object at a second point in time; and
assign, by the file system operation handling, the timestamp, corresponding to the first point in time different than the second point in time at which the replication operation was executed, to the first storage object.

### Claim 17 (depends on 16)

The computing device of claim 16, wherein the machine executable code causes the processor to:
reconfigure a default configuration of the file system operation handler to assign the timestamps, stored within the replication operations, to the storage objects upon which the replication operations are executed, wherein the default configuration corresponds to the file system operation handler assigning timestamps to the storage objects based upon times at which the replication operations are executed upon the storage objects.

### Claim 18 (depends on 16)

The computing device of claim 16, wherein the first point in time corresponds to a time at which an operation, of which the replication operation is a replica of, was previously executed upon a second storage object at the second node.

### Claim 19 (depends on 16)

The computing device of claim 16, wherein the machine executable code causes the processor to:
replicate operations executed upon the first storage object to the second node for execution upon a second storage object; and
refrain from replicating an operation to the second node based upon a result of the operation having a zero on-disk modification.

### Claim 20 (depends on 16)

The computing device of claim 16, wherein the machine executable code causes the processor to:
replicate operations executed upon the first storage object to the second node for execution upon a second storage object; and
refrain from replicating an operation to the second node based upon the operation having a zero payload.
