Netapp, Inc.

Bipul Raj

Alok Sharma

Dnyaneshwar Nagorao Pawar

Praveen Killamsetti

Albert E Yong

Naresh Sivakumar

Subramaniam Periyagaram

Karthik Chandrasekaran

Siddhartha Nandi

Gaurav Makkar

Ameya Prakash Usgaonkar

Parag Deshmukh

Satbir Singh

Arjun Gopalan

Praseem Banzal

Mandar D Kulkarni

Described herein is a system and method for retaining deduplication of data blocks of a resulting storage object (e.g., a flexible volume) from a split operation of a clone of a base storage object. The clone may comprise data blocks that are shared with at least one data block of the base storage object and at least one data block that is not shared with at least one data block of the base storage object. The data blocks of the clone that are shared with the base storage object may be indicated to receive a write allocation that may comprise assigning a new pointer to an indicated data block. Each data block may comprise a plurality of pointers comprising a virtual address pointer and a physical address pointer. As such, data blocks of the clone comprising the same virtual address pointer may be assigned a single physical address pointer. Thus, a new physical address pointer is assigned or allocated once to a given virtual address pointer of data blocks of a clone.

Maintaining data block maps of clones of storage objects

Systems and methods which provide mount catalogs to facilitate rapid volume mount are shown. A mount catalog of embodiments may be provided for each aggregate containing volumes to be mounted by a takeover node of a storage system. The mount catalog may comprise a direct storage level, such as a DBN level, based mount catalog. Such mount catalogs may be maintained in a reserved portion of the storage devices containing a corresponding aggregate and volumes, wherein the storage device reserved portion is known to a takeover node. In operation according to embodiments, a HA pair takeover node uses a mount catalog to access the blocks used to mount volumes of a HA pair partner node prior to a final determination that the partner node is in fact a failed node and prior to onlining the aggregate containing the volumes.

Systems and methods providing mount catalogs for rapid volume mount

Described herein is a system and method for a scalable crash-consistent snapshot operation. Write requests may be received from an application and a snapshot creation request may further be received. Write requests received before the snapshot creation request may be associated with pre-snapshot tags and write requests received after the snapshot creation request may be associated with post-snapshot tags. Furthermore, in response to the snapshot creation request, logical interfaces may begin to be switched from a pre-snapshot configuration to a post-snapshot configuration. The snapshot may then be created based on the pre-snapshot write requests and the post-snapshot write requests may be suspended until the logical interfaces have switched configuration.

System and method for a scalable crash-consistent snapshot operation

Described herein is a system and method for retaining deduplication of data blocks of a resulting storage object (e.g., a flexible volume) from a split operation of a clone of a base storage object. The clone may comprise data blocks that are shared with at least one data block of the base storage object and at least one data block that is not shared with at least one data block of the base storage object. The data blocks of the clone that are shared with the base storage object may be indicated to receive a write allocation that may comprise assigning a new pointer to a indicated data block. Each data block may comprise a plurality of pointers comprising a virtual address pointer and a physical address pointer. As such, data blocks of the clone comprising the same virtual address pointer may be assigned a single physical address pointer. Thus, a new physical address pointer is assigned or allocated once to a given virtual address pointer of data blocks of a clone.

System and method for retaining deduplication in a storage object after a clone split operation

A system and method for providing a substantially constant-time copy operation for file system objects managed by a storage server begins by generating a snapshot of at least a portion of a data set managed by the storage server. The system then performs a copy operation in the storage server to generate a copy of the data set separate from the snapshot, on a set of block locations containing a predetermined reference value. During the copy operation to generate the copy of the data set separate from the snapshot, the system can receive from a requester a first read request directed to the copy of the data set that the copy operation is to generate. In response to the first data request, the system provides data from the snapshot to the requester by the storage server.

Method and system for providing substantially constant-time execution of a copy operation

Method and system for initializing a plurality of virtual machines sharing a physical storage unit managed by a storage system for storing a boot image used for initializing the plurality of virtual machines are provided. A data structure is maintained by a virtual machine monitor that manages the plurality of virtual machines. The data structure includes a file block number for accessing a boot image that can be used for initializing the plurality of virtual machines and a unique signature for the physical storage unit storing the boot image and a memory address of a cache memory where the boot image is stored after it is obtained from the storage system. The plurality of virtual machines is initialized using the boot image from the cached memory without having to obtain the boot image for each individual virtual machine except for a first virtual machine.

Caching system and methods thereof for initializing virtual machines

One or more techniques and/or systems are provided for configuring a storage environment. In particular, the storage environment may be configured with a symmetric frontend and an asymmetric backend. That is, an owner storage controller may be granted read/write access to a storage device owned by the owner storage controller, while a non-owner storage controller may be granted merely read access. In this way, the owner storage controller may execute, log, and/or commit a write command to the storage device, while the non-owner storage controller may merely execute, but not log and/or commit, a write command. Write buffers, log memories, and/or file system metadata may be synchronized between the owner storage controller and the non-owner storage controller, such that the non-owner storage controller may efficiently take ownership of the storage device in response to a failure of the owner storage controller.

Storage environment with symmetric frontend and asymmetric backend

A storage server is coupled to a storage device that stores data blocks, and generates a fingerprint for each data block stored on the storage device. The storage server creates a master datastore and a plurality of datastore segments. The master datastore comprises an entry for each data block that is written to the storage device and a datastore segment comprises an entry for a new data block or a modified data block that is subsequently written to the storage device. The storage server merges the entries in the datastore segments with the entries in the master datastore in memory to free duplicate data blocks in the storage device. The storage server overwrites the master datastore with the entries in the plurality of datastore segments and the entries in the master datastore to create an updated master datastore in response to detecting that the number of datastore segments meets a threshold.

Segmented fingerprint datastore and scaling a fingerprint datastore in de-duplication environments

A system and method for providing a substantially constant-time copy operation for file system objects managed by a network storage server begins by generating a new file based on metadata in a source file. The system then generates a snapshot of the source file or the logical volume in which the source file resides. The system then copies each of the indirect blocks of the source file to a corresponding location in the destination file. During the copy process, a modified set of file system operations can be executed on the destination metadata container. In response to a read request directed to a target block in the destination file, the system determines if target block has been copied. If the block has not been copied, the system provides a data segment from the corresponding data block in the snapshot. Write requests are processed by generating a new data block and adding a reference to the new data block to the target location in the destination metadata container. During the copy process, the system checks each block reference before copying to determine if the block reference has been modified by a write operation. If the block was modified, the system skips copying that particular block reference. The system provides additional operations to execute truncate and append operations during the copy process.

A method and apparatus for deduplication of files of a storage system is described. During a gathering phase, a file may be simultaneously processed by two or more threads to produce and store content identifiers for data blocks of the file. Each file may be sub-divided into multiple file sub-portions, each file sub-portion comprising a predetermined number of data blocks. A thread may be assigned to each sub-portion of a file for processing the data blocks. The currently assigned sub-portion for each thread may be recorded and used upon a system crash to restart each scanner thread at the currently assigned sub-portion to minimize the data blocks that are re-processed. The size of a file sub-portion may be predetermined based on the organization of inode data structures representing the files (e.g., based on the maximum number of pointers that an indirect block in the inode data structure may contain).

Growing community of inventors

Bengaluru, India

Bipul Raj