公开(公告)号：US20170091056A1

公开(公告)日：2017-03-30

申请号：US14864026

申请日：2015-09-24

Applicant: NetApp, Inc.

Inventor： Steven S. Watanabe ,  Stephen H. Strange ,  John Muth ,  Kimberly A. Malone ,  Kayuri H. Patel

IPC: G06F11/20

CPC classification number: G06F11/2069 ,  G06F11/1441 ,  G06F11/2033 ,  G06F11/2035 ,  G06F11/2046 ,  G06F11/2094 ,  G06F11/2097 ,  G06F2201/805

Abstract: A high availability (HA) failover manager maintains data availability of one or more input/output (I/O) resources in a cluster by ensuring that each I/O resource is available (e.g., mounted) on a hosting node of the cluster and that each I/O resource may be available on one or more partner nodes of the cluster if a node (i.e., a local node) were to fail. The HA failover manager (HA manager) processes inputs from various sources of the cluster to determine whether failover is enabled for a local node and each partner node in an HA group, and for triggering failover of the I/O resources to the partner node as necessary. For each I/O resource, the HA manager may track state information including (i) a state of the I/O resource (e.g., mounted or un-mounted); (ii) the partner node(s) ability to service the I/O resource; and (iii) whether a non-volatile log recording I/O requests is synchronized to the partner node(s). The HA manager interacts with various layers of a storage I/O stack to mount and un-mount the I/O resources on one or more nodes of the cluster through the use of well-defined interfaces, e.g., application programming interfaces.

公开(公告)号：US10360120B2

公开(公告)日：2019-07-23

申请号：US15687062

申请日：2017-08-25

Applicant: NetApp, Inc.

Inventor： Steven S. Watanabe ,  Stephen H. Strange ,  John Muth ,  Kimberly A. Malone ,  Kayuri H. Patel

IPC: G06F11/20 ,  G06F11/14

Abstract: A high availability (HA) failover manager maintains data availability of one or more input/output (I/O) resources in a cluster by ensuring that each I/O resource is available (e.g., mounted) on a hosting node of the cluster and that each I/O resource may be available on one or more partner nodes of the cluster if a node (i.e., a local node) were to fail. The HA failover manager (HA manager) processes inputs from various sources of the cluster to determine whether failover is enabled for a local node and each partner node in an HA group, and for triggering failover of the I/O resources to the partner node as necessary. For each I/O resource, the HA manager may track state information including (i) a state of the I/O resource (e.g., mounted or un-mounted); (ii) the partner node(s) ability to service the I/O resource; and (iii) whether a non-volatile log recording I/O requests is synchronized to the partner node(s). The HA manager interacts with various layers of a storage I/O stack to mount and un-mount the I/O resources on one or more nodes of the cluster through the use of well-defined interfaces, e.g., application programming interfaces.

公开(公告)号：US09785525B2

公开(公告)日：2017-10-10

申请号：US14864026

申请日：2015-09-24

Applicant: NetApp, Inc.

Inventor： Steven S. Watanabe ,  Stephen H. Strange ,  John Muth ,  Kimberly A. Malone ,  Kayuri H. Patel

IPC: G06F11/20

CPC classification number: G06F11/2069 ,  G06F11/1441 ,  G06F11/2033 ,  G06F11/2035 ,  G06F11/2046 ,  G06F11/2094 ,  G06F11/2097 ,  G06F2201/805

Abstract: A high availability (HA) failover manager maintains data availability of one or more input/output (I/O) resources in a cluster by ensuring that each I/O resource is available (e.g., mounted) on a hosting node of the cluster and that each I/O resource may be available on one or more partner nodes of the cluster if a node (i.e., a local node) were to fail. The HA failover manager (HA manager) processes inputs from various sources of the cluster to determine whether failover is enabled for a local node and each partner node in an HA group, and for triggering failover of the I/O resources to the partner node as necessary. For each I/O resource, the HA manager may track state information including (i) a state of the I/O resource (e.g., mounted or un-mounted); (ii) the partner node(s) ability to service the I/O resource; and (iii) whether a non-volatile log recording I/O requests is synchronized to the partner node(s). The HA manager interacts with various layers of a storage I/O stack to mount and un-mount the I/O resources on one or more nodes of the cluster through the use of well-defined interfaces, e.g., application programming interfaces.

公开(公告)号：US09411514B2

公开(公告)日：2016-08-09

申请号：US14137084

申请日：2013-12-20

Applicant: NetApp, Inc.

Inventor： James Leong ,  Rajesh Sundaram ,  Douglas P. Doucette ,  Scott Schoenthal ,  Stephen H. Strange ,  Srinivasan Viswanathan

IPC: G06F3/06 ,  G06F9/48 ,  G06F11/20

CPC classification number: G06F3/0601 ,  G06F3/061 ,  G06F3/0611 ,  G06F3/0655 ,  G06F3/0659 ,  G06F3/0689 ,  G06F9/4881 ,  G06F11/2087

Abstract: A data access request to a file system is decomposed into a plurality of lower-level I/O tasks. A logical combination of physical storage components is represented as a hierarchical set of objects. A parent I/O task is generated from a first object in response to the data access request. A child I/O task is generated from a second object to implement a portion of the parent I/O task. The parent I/O task is suspended until the child I/O task completes. The child I/O task is executed in response to an occurrence of an event that a resource required by the child I/O task is available. The parent I/O task is resumed upon an event indicating completion of the child I/O task. Scheduling of any child I/O task is not conditional on execution of the parent I/O task, and a state diagram regulates the child I/O tasks.

公开(公告)号：US20160117113A1

公开(公告)日：2016-04-28

申请号：US14832410

申请日：2015-08-21

Applicant: NETAPP, INC.

Inventor： Dongfeng Li ,  Edward R. Zayas ,  Randal Thelen ,  Stephen H. Strange ,  Susan M. Coatney

IPC: G06F3/06

CPC classification number: G06F3/067 ,  G06F3/0604 ,  G06F3/0629 ,  G06F3/0632

Abstract: 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.

Abstract translation: 本发明在具有分层存储域的全局存储环境中唯一地命名存储设备。 具体地，根据本发明的一个或多个实施例，存储设备（例如，磁盘）连接在全局存储环境中的特定位置。 该特定位置与存储设备所在的一个或多个分级存储域中的每一个的路径相关联。 因此，将名称分配给作为存储装置所在的分层存储域的路径的存储装置。

公开(公告)号：US20150046745A1

公开(公告)日：2015-02-12

申请号：US13961086

申请日：2013-08-07

Applicant: NETAPP, INC.

Inventor： Poonam P. Dhavale ,  Stephen H. Strange

IPC: G06F11/20

CPC classification number: G06F17/30575 ,  G06F3/0647 ,  G06F7/00 ,  G06F11/2005 ,  G06F11/2033 ,  G06F11/2046 ,  G06F11/2092 ,  G06F17/30 ,  G06F17/30067 ,  G06F17/30079 ,  G06F17/30091 ,  G06F17/30194 ,  G06F17/30203 ,  G06F17/30221 ,  G06F17/30607 ,  G06F17/30864

Abstract: Method and system for replacing a first node and a second of a clustered storage system by a third node and a fourth node are provided. The method includes migrating all storage objects managed by the first node to the second node; replacing the first node by the third node and migrating all the storage objects managed by the first node and the second node to the third node; and replacing the second node by the fourth node and then migrating the storage objects previously managed by the second node but currently managed by the third node to the fourth node. The nodes may also be replaced by operationally connecting the third node and the fourth node to storage managed by the first node and the second node; joining the third node and the fourth node to a same cluster as the first node and the second node.

Abstract translation: 提供了用于由第三节点和第四节点替换集群存储系统的第一节点和第二节点的方法和系统。 该方法包括将由第一节点管理的所有存储对象迁移到第二节点; 由第三节点替换第一节点并将由第一节点和第二节点管理的所有存储对象迁移到第三节点; 并且由第四节点替换第二节点，然后将先前由第二节点管理但是当前由第三节点管理的存储对象迁移到第四节点。 也可以通过将第三节点和第四节点可操作地连接到由第一节点和第二节点管理的存储来替换节点; 将第三节点和第四节点加入与第一节点和第二节点相同的簇。