Netapp, Inc.

Network Appliance, Inc.

Susan M Coatney

Steven S Watanabe

Alan Rowe

Joydeep Sen Sarma

Stephen H Strange

Yuedong Mu

Pankti Vinay Majmudar

Jeffrey S Kimmel

Samuel M Cramer

David Brittain Bolen

Chaitanya V Patel

Brian Christopher Parkison

Radek Aster

Ching-Yuk Paul Ngan

Balaji Ramani

Hrishikesh Keremane

Vijay Singh

Manoj V Sundararajan

Prachi Deshmukh

Kazunobu Nishime

John T Lloyd

Santosh Ananth Rao

Scott A Schoenthal

Loellyn Jane Cassell

Poonam P Dhavale

Steven H Rodrigues

Amit Valjibhai Panara

Santhosh Unnikrishnan

Sravan Kumar Elpula

Kayuri Hasmukh Patel

Douglas W Coatney

Edward Ramon Zayas

Richard O Larson

Gaurav Agarwal

Randal Thelen

Dongfeng Li

Ye Sun

Gautam Dev Sharma

Atul Goel

Harihara Kadayam

Kalaivani Arumugham

Yong Cho

Vaiapuri Ramasubramaniam

Kyle Diggs Sterling

Brad A Reger

Andrew Eric Dunn

Vani Vully

Anuja Jaiswal

Sreelatha Sunkara Reddy

Sasidharan Krishnan

Laurent Nicolas Lambert

Deepa Ramesh

Thomas B Bolt

Angel B Aviles

Chaitanya Patel

Amit V Panara

One or more techniques and/or devices are provided for storage virtual machine relocation (e.g., ownership change) between storage clusters. For example, operational statistics of a first storage cluster and a second storage cluster may be evaluated to identify a set of load balancing metrics. Ownership of one or more storage aggregates and/or one or more storage virtual machines may be changed (e.g., permanently changed for load balancing purposes or temporarily changed for disaster recovery purposes) between the first storage cluster and the second storage cluster utilizing zero-copy ownership change operations based upon the set of load balancing metrics. For example, if the first storage cluster is experiencing a relatively heavier load of client I/O operations and the second storage cluster has available resources, ownership of a storage aggregate and a storage virtual machine may be switched from the first storage cluster to the second storage cluster for load balancing.

Storage virtual machine relocation

During a storage redundancy giveback from a first node to a second node following a storage redundancy takeover from the second node by the first node, the second node is initialized in part by receiving a node identification indicator from the second node. The node identification indicator is included in a node advertisement message sent by the second node during a giveback wait phase of the storage redundancy giveback. The node identification indicator includes an intra-cluster node connectivity identifier that is used by the first node to determine whether the second node is an intra-cluster takeover partner. In response to determining that the second node is an intra-cluster takeover partner, the first node completes the giveback of storage resources to the second node.

Non-disruptive controller replacement in a cross-cluster redundancy configuration

A primary write request that is to modify a primary portion of primary data stored in a primary storage node is received. The primary write request is to be replicated to create a current secondary write request. The current secondary write request is to modify a current secondary portion of secondary data that is stored in a secondary storage node. A current data range of the current secondary portion is determined. A determination is made of whether a previous secondary write request is in process of modifying a previous data range that at least partially overlaps with a current data range of the current secondary portion. Execution of the primary write request is suspended, until the previous secondary write request has completed updating the secondary storage node.

Overlapping write detection and processing for sync replication

The present invention uniquely names storage devices in a global storage environment with hierarchical storage domains. In particular, according to one or more embodiments of the present invention a storage device (e.g., a disk) is connected at a particular location within the global storage environment. That particular location is associated with a path of each of one or more hierarchical storage domains in which the storage device is located. Accordingly, a name is assigned to the storage device that is the path of the hierarchical storage domains in which the storage device is located.

Uniquely naming storage devices in a global storage environment

A method, non-transitory computer readable medium, and storage node computing device that identifies a subset of a plurality of sections of a shelf that is unowned based on a determined ownership status of a plurality of storage devices hosted by the shelf. Obtained section discriminant data is applied to one of a plurality of ordered storage node identifiers to identify one section of the subset of the sections. Ownership of one or more of the storage devices corresponding to the one section is obtained.

Methods for autonomous disk ownership assignment of nodes in a storage network with a multi-path configuration and devices thereof

Data consistency and availability can be provided at the granularity of logical storage objects in storage solutions that use storage virtualization in clustered storage environments. To ensure consistency of data across different storage elements, synchronization is performed across the different storage elements. Changes to data are synchronized across storage elements in different clusters by propagating the changes from a primary logical storage object to a secondary logical storage object. To satisfy the strictest RPOs while maintaining performance, change requests are intercepted prior to being sent to a filesystem that hosts the primary logical storage object and propagated to a different managing storage element associated with the secondary logical storage object.

Granular sync/semi-sync architecture

A system and method for avoiding object identifier collisions in a cluster environment is provided. Upon creation of the cluster, volume location databases negotiate ranges for data set identifiers (DSIDs) between a first site and a second site of the cluster. Any pre-existing objects are remapped into an object identifier range associated with the particular site hosting the object.

System and method for avoiding object identifier collisions in a peered cluster environment

A storage object is migrated between nodes by a source node automatically verifying that another node is configured to service the storage object and changing ownership of the storage object based on the verifying. A cluster manager for the clustered storage system receives a request and provides the request to the source which owns the storage object. The source verifies that the destination is configured according to a predetermined configuration for servicing the storage object. Based on the verifying, the source offlines the storage object and updates ownership information of the storage object, thereafter allowing the destination to online the storage object. The cluster manager further provides the updated ownership information to all the nodes in the cluster, so an access request intended for the storage object may be received by any node and forwarded to the destination using the updated ownership information to effect a transparent migration.

Transparently migrating a storage object between nodes in a clustered storage system

Growing community of inventors

Cupertino, CA, United States of America

Susan M Coatney