Methods for improved data store migrations and devices thereof

• US 10,031,682 B1
• Filed: 04/28/2017
• Issued: 07/24/2018
• Est. Priority Date: 04/28/2017
• Status: Active Grant

• Current Assignee: NetApp, Inc.
• Original Assignee: NetApp, Inc.
• Inventors: George, Tijin, Thompson, Cheryl, Subramanian, Ananthan
• Primary Examiner(s): Nguyen, Than Vinh
• Application Number:
  US15/581,742
• Time in Patent Office: 452 Days
• Field of Search: 711155
• CPC Class Codes: G06F 3/0605 by facilitating the interaction with a user or administrator
• CPC Class Codes: G06F 3/0647 Migration mechanisms
• CPC Class Codes: G06F 3/0665 at area level, e.g. provisioning of virtual or logical volumes
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]

Abstract

A method, non-transitory computer readable medium, and computing device that receives metadata for a block associated with an object from a source storage node. The metadata comprises a source object identifier and the object is associated with a source volume of a source aggregate owned by the source storage node. A determination is made when another block associated with the object has been previously received. A destination object identifier is obtained based on the source object identifier, when the determining indicates that the other block associated with the object has been previously received. A new aggregate block number is assigned to the block based on the destination object identifier and another portion of the metadata. Ownership of the source volume is transferred upon receipt of an indication of a cutover from the source storage node in order to migrate the source volume to a destination volume of a destination aggregate.

Claims

1. A method, comprising:

receiving, by a computing device, metadata for a block associated with an object from a source storage node, wherein the metadata comprises at least a source object identifier and the object is associated with a source volume of a source aggregate owned by the source storage node;

determining, by the computing device, when another block associated with the object has been previously received and obtaining a destination object identifier based on the source object identifier, when the determining indicates that the other block associated with the object has been previously received;

assigning, by the computing device, a new aggregate block number to the block based on the destination object identifier and another portion of the metadata; and

transferring, by the computing device, ownership of the source volume upon receipt of an indication of a cutover from the source storage node in order to migrate the source volume to a destination volume of a destination aggregate without moving any user data.

2. The method of claim 1, wherein the source aggregate and the destination aggregate comprise composite aggregates each comprising data in a respective local storage and a same remote cloud repository.

3. The method of claim 1, further comprising generating, by the computing device, another destination object identifier and inserting the other destination object identifier into an object mapping file as associated with the source object identifier, when the determining indicates that another block associated with the object has not been previously received.

4. The method of claim 1, wherein the source and destination aggregates are associated with a same cluster and the method further comprises:

receiving, by the computing device, a source volume identifier for the source volume prior to receiving the metadata for the block; and

updating, by the computing device, an entry of a database of the cluster associated with the source volume identifier in order to transition ownership of the source volume.

5. The method of claim 1, wherein the other portion of the metadata comprises an offset within the object associated with the block.

6. The method of claim 1, wherein the source volume comprises a plurality of objects including the object, the objects are associated with monotonically increasing sequence numbers, and the indication of the cutover comprises an indication of a last one of the sequence numbers for the source volume.

7. A non-transitory machine readable medium having stored thereon instructions for improved data store migrations comprising machine executable code which when executed by at least one machine causes the machine to:

receive metadata for a block associated with an object from a source storage node, wherein the metadata comprises at least a source object identifier and the object is associated with a source volume of a source aggregate owned by the source storage node;

determine when another block associated with the object has been previously received and obtain a destination object identifier based on the source object identifier, when the determining indicates that the other block associated with the object has been previously received;

assign a new aggregate block number to the block based on the destination object identifier and another portion of the metadata; and

transfer ownership of the source volume upon receipt of an indication of a cutover from the source storage node in order to migrate the source volume to a destination volume of a destination aggregate without moving any user data.

8. The non-transitory machine readable medium of claim 7, wherein the source aggregate and the destination aggregate comprise composite aggregates each comprising data in a respective local storage and a same remote cloud repository.

9. The non-transitory machine readable medium of claim 7, wherein the machine executable code when executed by the machine further causes the machine to generate another destination object identifier and inserting the other destination object identifier into an object mapping file as associated with the source object identifier, when the determining indicates that another block associated with the object has not been previously received.

10. The non-transitory machine readable medium of claim 7, wherein the source and destination aggregates are associated with a same cluster and the machine executable code when executed by the machine further causes the machine to:

receive a source volume identifier for the source volume prior to receiving the metadata for the block; and

update an entry of a database of the cluster associated with the source volume identifier in order to transition ownership of the source volume.

11. The non-transitory machine readable medium of claim 7, wherein the other portion of the metadata comprises an offset within the object associated with the block.

12. The non-transitory machine readable medium of claim 7, wherein the source volume comprises a plurality of objects including the object, the objects are associated with monotonically increasing sequence numbers, and the indication of the cutover comprises an indication of a last one of the sequence numbers for the source volume.

13. A computing device, comprising:

a memory containing machine readable medium comprising machine executable code having stored thereon instructions for facilitating planned data container transitions; and

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

receive metadata for a block associated with an object from a source storage node, wherein the metadata comprises at least a source object identifier and the object is associated with a source volume of a source aggregate owned by the source storage node;

determine when another block associated with the object has been previously received and obtain a destination object identifier based on the source object identifier, when the determining indicates that the other block associated with the object has been previously received;

assign a new aggregate block number to the block based on the destination object identifier and another portion of the metadata; and

transfer ownership of the source volume upon receipt of an indication of a cutover from the source storage node in order to migrate the source volume to a destination volume of a destination aggregate without moving any user data.

14. The source storage node computing device of claim 13, wherein the source aggregate and the destination aggregate comprise composite aggregates each comprising data in a respective local storage and a same remote cloud repository.

15. The source storage node computing device of claim 13, wherein the processor is further configured to execute the machine executable code to further cause the processor to generate another destination object identifier and inserting the other destination object identifier into an object mapping file as associated with the source object identifier, when the determining indicates that another block associated with the object has not been previously received.

16. The source storage node computing device of claim 13, wherein the source and destination aggregates are associated with a same cluster and the processor is further configured to execute the machine executable code to further cause the processor to:

receive a source volume identifier for the source volume prior to receiving the metadata for the block; and

update an entry of a database of the cluster associated with the source volume identifier in order to transition ownership of the source volume.

17. The source storage node computing device of claim 13, wherein the other portion of the metadata comprises an offset within the object associated with the block.

18. The source storage node computing device of claim 13, wherein the source volume comprises a plurality of objects including the object, the objects are associated with monotonically increasing sequence numbers, and the indication of the cutover comprises an indication of a last one of the sequence numbers for the source volume.