Netapp, Inc.

Symantec Operating Corporation

Kalaivani Arumugham

Poonam P Dhavale

Ronald S Karr

Sasidharan Krishnan

Oleg Kiselev

Ram Kesavan

Santosh Ananth Rao

Ravikanth Dronamraju

Gopal Sharma

Ratnesh Gupta

Ryan Edward Bartlett

Preksha Bansal

Parag Sarfare

Shie-rei Huang

Vijaya Kumar Chakravarthy Ekkaladevi

Prachi Deskmukh

Randy Shingai

John Colgrove

Anand A Kekre

Susan M Coatney

Atul Ramesh Pandit

Ching-Yuk Paul Ngan

Douglas W Coatney

Hrishikesh Keremane

Vijay Singh

Rakesh Bhargava M R

Akhil Kaushik

Kyle Diggs Sterling

Kazunobu Nishime

Randall K Shingai

Deepa Ramesh

Michael Wahl

Vijay Kumar Chakravarthy Ekkaladevi

Sravana Kumar Elpula

William R Taylor

Dean Lyle Voiss

Methods and systems for Vserver migration are provided. One method includes executing a transfer phase of a migrate operation for migrating a Vserver of a source cluster to a destination cluster, using asynchronous baseline transfer to transfer a plurality of source storage volumes configured in a consistency group (CG) for the migrate operation to a plurality of destination storage volumes of a destination cluster; updating a state of each of the plurality of source storage volumes to a sync state indicating completion of a pre-commit phase of the migrate operation to initiate a commit phase of the migrate operation; and generating a snapshot of the plurality of destination storage volumes for performing data integrity checks between data stored at the source cluster and migrated data at destination cluster, after completing a commit phase of the migrate operation.

Methods and systems for storage virtual machine migration between clusters of a networked storage system

A data management system can include a disk unit and a set of controllers. The disk unit can contain, at least in part, a set of storage media, a first persistent memory, and a second persistent memory. The set of storage media can be configured to implement a storage space. The set of controllers can be configured to write to the storage space and to implement a set of nodes including a first node and a second node. The first node can be configured to generate and write first node journal data to the first persistent memory. The second node can be configured to obtain a failure indication for the first node, obtain the first node journal data from the second persistent memory, and generate and provide a reply to a backend using the first node journal data.

Systems and methods for data management using a disk unit

Failover methods and systems for a storage environment are provided. During a takeover operation to take over storage of a first storage system node by a second storage system node, the second storage system node copies information from a first storage location to a second storage location. The first storage location points to an active file system of the first storage system node, and the second storage location is assigned to the second storage system node for the takeover operation. The second storage system node quarantines storage space likely to be used by the first storage system node for a write operation, while the second storage system node attempts to take over the storage of the first storage system node. The second storage system node utilizes information stored at the second storage location during the takeover operation to give back control of the storage to the first storage system node.

Failover methods and system in a networked storage environment

A data management system can include a set of storage media configured to implement a storage space and a set of controllers. The set of controllers can be configured to write to the storage space and to implement a set of nodes. The set of controllers can include a first controller that implements a first node and includes a first persistent memory, a second controller that implements a second node and includes a second persistent memory and a third controller that implements a third node and includes a third persistent memory. The third node can be configured to write third node journal data to the first persistent memory. The first node can be configured to generate first node journal data based on a first request received from a backend, write the first node journal data to the first persistent memory, and replicate the journal data to the second persistent memory.

Systems and methods for data management using controllers

Techniques are provided for metadata management for enabling automated switchover. An initial quorum vote may be performed before a node executes an operation associated with metadata comprising operational information and switchover information. After the initial quorum vote is performed, the node executes the operation upon one or more mailbox storage devices. Once the operation has executed, a final quorum vote is performed. The final quorum vote and the initial quorum vote are compared to determine whether the operation is to be designated as successful or failed, and whether any additional actions are to be performed.

Mediator assisted switchover between clusters

Techniques are provided for metadata management for enabling automated switchover in accordance with a configuration of storage solution that expresses a preference for either maintaining availability (e.g., a non-zero RPO mode) of the storage solution or avoiding data loss (e.g., a zero RPO mode). In one example, responsive to detecting a switchover trigger event, a node of a local cluster of a cross-site storage solution determines whether performance of an automated switchover from a failed cluster to a surviving cluster of the cross-site storage solution is enabled. Responsive to an affirmative determination, the node selectively proceeds with the automated switchover based on the configuration.

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

One or more techniques and/or computing devices are provided for preserving coredump data. A first storage controller, of a first storage cluster, may have a disaster recovery relationship with a second storage controller of a second storage cluster. When the first storage controller fails, the first storage controller performs a coredump process to dump memory contents of the first storage controller into a storage device. During implementation of the coredump process, the first storage controller stores a storage device identifier of the storage device into a disk mailbox. Upon detecting the failure, the second storage controller reads the storage device identifier from the disk mailbox. The second storage controller performs a switchover operation to change ownership of storage devices, but excluding the storage device used by the coredump process, from the first storage controller to the second storage controller for providing clients with failover access to the storage devices.

Preserving coredump data during switchover operation

A method, non-transitory computer readable medium and storage node computing device that reserves one of a plurality of data storage devices that is designated as a coordinator data storage device. A section of the storage cluster that is unowned is identified. Ownership of a subset of the data storage devices that is in the section of the storage cluster is obtained. A determination is made when the subset of the data storage devices includes the coordinator data storage device. The reservation of the coordinator data storage device is released, when the determining indicates that the subset of the data storage devices does not include the coordinator data storage device.

Methods for automatic data storage device assignment during system initialization and devices thereof

A method, non-transitory computer readable medium, and device that assists with dynamically determining and readjusting failover targets includes identifying an existing failover target from a plurality of failover targets for backing up an updated object. The identified existing failover target is determined for eligibility for backing up the updated object. One or more new failover targets from the plurality of failover targets are dynamically identified based on a plurality of storage parameters when the identified existing failover target is determined not to be eligible for backing up the updated object. The updated object is backed up in one of the dynamically identified one or more new failover targets.

Methods for dynamically determining and readjusting failover targets and devices thereof

A method and system for providing a shared data resource coordinator within a storage virtualizing data processing system is disclosed. According to one embodiment of the present invention, a first node of a plurality of nodes is configured to process requests to access a shared data resource on behalf of the plurality of nodes, where the plurality of nodes includes a logical volume configuration server configured to present a logical volume to one or more logical volume configuration clients. A second node is then selected from the plurality of nodes and configured to process requests to access the shared data resource on behalf of the plurality of nodes.

Method and system for providing a shared data resource coordinator within a storage virtualizing data processing system

A system employing asymmetric distributed block virtualization includes a volume server, a plurality of volume clients, and one or more physical block devices. The volume server aggregates storage in the physical block devices into a logical volume and makes the logical volume accessible to the volume clients for input/output (I/O) operations. In order to manage different I/O access requirements (such as read-only access versus read-write access) of the volume clients, the volume server maintains a different I/O access policy for each volume client to control the kinds of input/output operations that the volume client is allowed to perform on the logical volume.

System and method for managing I/O access policies in a storage environment employing asymmetric distributed block virtualization

Growing community of inventors

Sunnyvale, CA, United States of America

Kalaivani Arumugham