IP Library Granted Patent US 11,797,406
Granted Patent B2
US 11,797,406 · App. 17/947,389 · Granted Oct 24, 2023

Moving a consistency group having a replication relationship

Inventors: Pranab Patnaik (Cary, NC); Nagender Somavarapu (Sunnyvale, CA); Yuedong Mu (San Jose, CA); Rithin Kumar Shetty (Sunnyvale, CA); Devang Kundanlal Shah (San Jose, CA)
Assignee: NetApp, Inc.
G06F11/2094G06F11/1441G06F11/2097
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,797,406
App. No.
17/947,389
Granted
Oct 24, 2023
Kind
B2
Abstract

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.

Claims (52)

1. A method, comprising:

removing a set of storage items from a first consistency group within first storage;

moving the set of storage items from the first storage to second storage to create a set of moved storage items within the second storage as a new first consistency group, wherein during the moving:

in response to receiving a first operation targeting a first storage item not yet moved from the first storage to the second storage, directing the first operation to the first consistency group and tracking the first operation within a first log; and

in response to receiving a second operation targeting a second storage item already moved from the first storage to the second storage, directing the second operation to the new first consistency group and tracking the second operation within a second log different than the first log; and

performing a rebaseline operation to reconstruct the new first consistency group at the second storage, wherein the new first consistency group comprises the set of moved storage items, wherein the rebaseline operation includes creating a new replication relationship between the moved storage items within the new first consistency group and a second consistency group.

2. The method of claim 1 , comprising:

creating the second consistency group within second storage, wherein the second consistency group is maintained as a replica of the first consistency group.

3. The method of claim 1 , comprising:

moving a sync cache, describing how endpoints are synchronously replicated, from the first storage to the second storage for performing the rebaseline operation.

4. The method of claim 1 , comprising:

moving an inflight tracker, used to capture inflight operations targeting the first consistency group, from the first storage to the second storage for performing the rebaseline operation.

5. The method of claim 1 , comprising:

utilizing, by the rebaseline operation, a first dirty region log used to track modification to the set of storage items and a second dirty region log used to track modifications to the set of moved storage items to resynchronize the new first consistency group and the second consistency group, wherein the first dirty region log and the second dirty region log are compared to identify data differences to reconcile by the rebaseline operation.

6. The method of claim 1 , comprising:

executing single file move on demand (SFMOD) commands to move active file system data of the set of storage items to the second storage.

7. The method of claim 1 , wherein performing the rebaseline operation comprises:

utilizing a baseline snapshot to transfer data from the first storage to the second storage to create the new first consistency group.

8. The method of claim 1 , wherein performing the rebaseline operation comprises:

utilizing one or more incremental snapshots to transfer delta data between the first storage and the second storage.

9. The method of claim 1 , wherein the moving triggers the tracking by the first log and the second log.

10. A non-transitory machine readable medium comprising machine executable code which when executed by a machine, causes the machine to:

remove a set of storage items from a first consistency group within first storage;

move the set of storage items from the first storage to second storage to create a set of moved storage items within the second storage as a new first consistency group, wherein during the moving

in response to receiving a first operation targeting a first storage item not yet moved from the first storage to the second storage, directing the first operation to the first consistency group and tracking the first operation within a first log; and

in response to receiving a second operation targeting a second storage item already moved from the first storage to the second storage, directing the second operation to the new first consistency group and tracking the second operation within a second log different than the first log; and

perform a rebaseline operation to reconstruct the new first consistency group at the second storage, wherein the new first consistency group comprises the set of moved storage items, wherein the rebaseline operation includes creating a new replication relationship between the moved storage items within the new first consistency group and a second consistency group.

11. The non-transitory machine readable medium of claim 10 , wherein the machine executable code causes the machine to:

create the second consistency group within second storage, wherein the second consistency group is maintained as a replica of the first consistency group.

12. The non-transitory machine readable medium of claim 10 , wherein the machine executable code causes the machine to:

moving a sync cache, describing how endpoints are synchronously replicated, from the first storage to the second storage for performing the rebaseline operation.

13. The non-transitory machine readable medium of claim 10 , wherein the machine executable code causes the machine to:

move an inflight tracker, used to capture inflight operations targeting the first consistency group, from the first storage to the second storage for performing the rebaseline operation.

14. The non-transitory machine readable medium of claim 10 , wherein the machine executable code causes the machine to:

utilize by the rebaseline operation, a first dirty region log used to track modification to the set of storage items and a second dirty region log used to track modifications to the set of moved storage items to resynchronize the new first consistency group and the second consistency group, wherein the first dirty region log and the second dirty region log are compared to identify data differences to reconcile by the rebaseline operation.

15. The non-transitory machine readable medium of claim 10 , wherein the machine executable code causes the machine to:

execute single file move on demand (SFMOD) commands to move active file system data of the set of storage items to the second storage.

16. A computing device comprising:

a memory comprising machine executable code; and

a processor coupled to the memory, the processor configured to execute the machine executable code to cause the processor to:

remove a set of storage items from a first consistency group within first storage;

move the set of storage items from the first storage to second storage to create a set of moved storage items within the second storage as a new first consistency group, wherein during the moving:

in response to receiving a first operation targeting a first storage item not yet moved from the first storage to the second storage, directing the first operation to the first consistency group and tracking the first operation within a first log: and

in response to receiving a second operation targeting a second storage item already moved from the first storage to the second storage, directing the second operation to the new first consistency group and tracking the second operation within a second log different than the first log

perform a rebaseline operation to reconstruct the new first consistency group at the second storage, wherein the new first consistency group comprises the set of moved storage items, wherein the rebaseline operation includes creating a new replication relationship between the moved storage items within the new first consistency group and a second consistency group.

17. The computing device of claim 16 , wherein the machine executable code causes the processor to:

utilize a baseline snapshot to transfer data from the first storage to the second storage to create the new first consistency group.

18. The computing device of claim 16 , wherein the machine executable code causes the processor to:

utilize one or more incremental snapshots to transfer delta data between the first storage and the second storage.

19. The computing device of claim 16 , wherein the moving triggers the tracking by the first log and the second log.

20. The computing device of claim 16 , wherein the machine executable code causes the processor to

utilize by the rebaseline operation, a first dirty region log used to track modification to the set of storage items and a second dirty region log used to track modifications to the set of moved storage items to resynchronize the new first consistency group and the second consistency group, wherein the first dirty region log and the second dirty region log are compared to identify data differences to reconcile by the rebaseline operation.

Continuity (3)
Continuation 16806110 · Mar 2, 2020
Continuation 15142186 · Apr 29, 2016
Related Publication 20230012563A1 · Jan 19, 2023