Netapp, Inc.

Ameya Prakash Usgaonkar

Kamlesh Advani

Siddhartha Nandi

Shehbaz Jaffer

Mangesh Chitnis

Bipul Raj

Parag Deshmukh

Bhaskar Singhal

Deepti Banka

Ramana Reddy

A request to change one or more storage characteristics associated with a virtual storage device is received. Communications identifying the virtual storage device are routed, via a network, to a first storage endpoint. One or more operations are performed in accordance with the request. A configuration of the network is updated to route communications identifying the virtual storage device to a second storage endpoint.

Network-based elastic storage

A host machine may host a virtual machine. Virtual machine reboot information, used to reboot the virtual machine in the event of a failure or restart of the virtual machine, may be identified (e.g., file system metadata buffers, a virtual non-volatile random access memory log, user data buffers, and/or data used to reboot the virtual machine such as to perform a reboot mounting operation and/or a reboot replay operation of a volume of data associated with the virtual machine). The virtual machine reboot information may be cached within relatively fast host memory of the host machine (e.g., instead of merely within a relatively slower hard drive or other storage device). In this way, the cached virtual machine reboot information may be quickly retrieved so that the virtual machine may be rebooted in a relatively shorter amount of time.

Virtual machine reboot information persistence into host memory

A method, non-transitory computer readable medium, and storage controller computing device that establishes an application interface and a source interface to a programmable switch. A flow table of the programmable switch is updated to insert routing actions associated with the application and source interfaces. Next, when an application request received from an application is locally serviceable is determined. When the determination indicates the application request is not locally serviceable, a migration request for data associated with the application request is sent to the programmable switch from the source interface and a destination address of a source storage server is used. Additionally, a migration response to the migration request including the data from the source storage server is received from the source interface. The data is then stored locally in a destination storage server and thereby is migrated from the source storage server.

Methods for migrating data between heterogeneous storage platforms and devices thereof

A distributed control protocol dynamically establishes high availability (HA) partner relationships for nodes in a cluster. A HA partner relationship may be established by copying (mirroring) information maintained in a non-volatile random access memory (NVRAM) of a node over a HA interconnect to the NVRAM of a partner node in the cluster. The distributed control protocol leverages a Cluster Liveliness and Availability Manager (CLAM) utility of a storage operating system executing on the nodes to rebalance NVRAM mirroring and alter HA partner relationships of the nodes in the cluster. The CLAM utility is configured to maintain various cluster related issues, such as CLAM quorum events, addition or subtraction of a node in the cluster and other changes in configuration of the cluster. Notably, the CLAM utility is an event based manager that implements the control protocol to keep the nodes informed of any cluster changes through event generation and propagation.

Distributed control protocol for high availability in multi-node storage cluster

A live non-volatile (NV) replay technique enables a partner node to efficiently takeover a failed node of a high-availability pair in a multi-node storage cluster by dynamically replaying operations synchronously logged in a non-volatile random access memory (NVRAM) of the partner node, while also providing high performance during normal operation. Dynamic live replay may be effected through interpretation of metadata describing the logged operations. The metadata may specify a location and type of each logged operation within a partner portion of the NVRAM, as well as any dependency among the logged operation and any other logged operations that would impose an ordering constraint. During normal operation, the partner node may consult the metadata to identify dependent logged operations and dynamically replay those operations to satisfy one or more requests. Upon failure of the node, the partner node may replay, in parallel, those logged operations having no imposed ordering constraint, thereby reducing time needed to complete takeover of the failed node.

Live NV replay for enabling high performance and efficient takeover in multi-node storage cluster

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 method, apparatus, and system of presentation of a read-only clone Logical Unit Number (LUN) to a host device as a snapshot of a parent LUN are disclosed. In one embodiment, a method includes generating a read-write clone LUN of a parent LUN and coalescing an identical data instance of the read-write clone LUN and the parent LUN in a data block of a volume of a storage system. A block transfer protocol layer is modified to refer the read-write clone LUN as a read-only clone LUN, according to the embodiment. Furthermore, according to the embodiment, the read-only clone LUN is presented to a host device as a snapshot of the parent LUN.

Presentation of a read-only clone LUN to a host device as a snapshot of a parent LUN

A method, apparatus and system of restoration of a parent LUN through modification of a read-write clone LUN as the parent LUN are disclosed. In one embodiment, the method includes transforming a snapshot of a parent LUN from a read-only state to a read-write clone LUN using a target module of a storage system. The method also includes changing a first data structure of a block transfer protocol to refer to the parent LUN as another clone LUN. Further, the method includes modifying a second data structure of the block transfer protocol to refer to the read-write clone LUN as the parent LUN. Then, the method includes restoring the parent LUN when the modification of the second data structure is completed.

Growing community of inventors

Old Goa, India

Ameya Prakash Usgaonkar