Netapp, Inc.

Garima Choudhary

Cheryl Marie Thompson

Rajesh Sudarsan

Ananthan Subramanian

Anil Paul Thoppil

Qinghua Zheng

Kevin Daniel Varghese

Techniques are provided for migrating a volume utilizing an object copy work queue and an object copy driver module. Data of the volume is stored within objects stored across a storage tier and capacity tier of a source object store. As part of migrating the volume to a destination object store, the objects are migrated to the destination cluster. Directly copying the objects involves multiple read operations to the source object store and a write operation at the destination object store. The techniques provided herein improve the efficiency of the migration by initially sending metadata from the source object store to the destination object store for performing backend object copy operations to migrate the volume. This results in fewer operations and less network usage, thus improving the efficiency and cost of migrating the volume.

Object copy driver module for object migration

Techniques are provided for modifying a read path to process read operations during a storage operation, such as an operation to migrate objects storing data of a volume. The objects are stored across a storage tier and capacity tier of a source object store. As part of migrating the volume to a destination object store, the objects are migrated to the destination cluster. Directly copying the objects involves multiple read operations to the source object store and a write operation at the destination object store. The techniques provided herein improve the efficiency of the migration by initially sending metadata from the source object store to the destination object store for performing backend block copy operations to migrate the volume.

Modified read path for processing read operations during object migration

Systems and methods for performing a zero-copy volume move between nodes of a distributed storage system are provided. In one example, an approach for performing a zero-copy volume move is proposed in which volume data may be maintained in place within a storage pod and need not be copied to move a given volume between the source node and the destination node. In one embodiment, metadata (e.g., a top-most physical volume block number (PVBN) of a node tree representing the volume at issue) of a write-anywhere file system is copied from the source node to the destination node. Since the storage pod is associated with a global PVBN space that is visible and accessible to all nodes of the distributed storage system, as a result of copying the top-mode PVBN of the volume to the destination node, anything below the top-most PVBN will automatically be visible to the destination node.

Zero-copy volume move within a distributed storage system

Techniques are provided for processing read operations while splitting a clone volume from a parent volume whose data is stored within objects of an object store. A transfer map is created to track mappings of child object identifiers to parent object identifiers of the parent objects to copy as child objects having the child object identifiers. The transfer map for the object store is traversed to copy the parent objects as the child objects for the split clone operation. The child objects are verified as being successfully created with valid data. In response to determining that the parent object has been copied as the child object, a context check is performed using the reverse map to verify a block within the child object. In response a successful context check, the read operation is processed using the block of the child object.

Read access during clone volume split operation

Techniques are provided for splitting a clone volume from a parent volume whose data is stored within objects of an object store. A transfer map is used to track mappings of selectively created child object identifiers used to subsequently copy the one or more parent objects to create child objects corresponding to the child object identifiers. A consistency point phase is performed. For each child object identifier processed during the consistency point phase, an object state for a corresponding child object is set to a copy pending state. A reverse map is populated with a reverse map entry. The transfer map is traversed to copy the one or more parent objects as the child objects for splitting the clone volume from the parent volume. The reverse map is used to verify that the child objects are successfully created with valid data.

Growing community of inventors

San Jose, CA, United States of America

Garima Choudhary