公开(公告)号：WO2010033335A2

公开(公告)日：2010-03-25

申请号：PCT/US2009/054304

申请日：2009-08-19

Applicant: MICROSOFT CORPORATION

Inventor： DAS, Rajsekhar ,  DION, David A .

IPC: G06F15/16 ,  H04L9/14 ,  G06F9/06

CPC classification number: H04L67/1097 ,  G06F3/0622 ,  G06F3/0631 ,  G06F3/0659 ,  G06F3/067 ,  G06F3/0689 ,  G06F11/2033 ,  G06F11/2046 ,  G06F2209/5014

Abstract: Described is a technology by which an owner node in a server cluster maintains ownership of a storage mechanism through a persistent reservation mechanism, while allowing non-owning nodes read and write access to the storage mechanism. An owner node writes a reservation key to a registration table associated with the storage mechanism. Non-owning nodes write a shared key that gives them read and write access. The owner node validates the shared keys against cluster membership data, and preempts (e.g., removes) any key deemed not valid. The owner node also defends ownership against challenges to ownership made by other nodes, so that another node can take over ownership if a (formerly) owning node is unable to defend, e.g., because of a failure.

Abstract translation: 描述了一种技术，通过该技术，服务器集群中的所有者节点通过永久保留机制来维护存储机制的所有权，同时允许非拥有节点对存储机制进行读写访问。 所有者节点将预留密钥写入与存储机制相关联的注册表。 非拥有节点编写一个共享密钥，为其提供读写访问权限。 所有者节点根据集群成员数据验证共享密钥，并抢占（例如，删除）任何被认为无效的密钥。 所有者节点还保护所有权，以抵御由其他节点所有权产生的挑战，从而如果（以前拥有）节点无法保护，例如由于故障，另一个节点可以占有所有权。

公开(公告)号：EP2350849A2

公开(公告)日：2011-08-03

申请号：EP09814963.6

申请日：2009-08-19

Applicant: Microsoft Corporation

Inventor： DAS, Rajsekhar ,  DION, David A .

IPC: G06F15/16 ,  H04L9/14 ,  G06F9/06

CPC classification number: H04L67/1097 ,  G06F3/0622 ,  G06F3/0631 ,  G06F3/0659 ,  G06F3/067 ,  G06F3/0689 ,  G06F11/2033 ,  G06F11/2046 ,  G06F2209/5014

Abstract: Described is a technology by which an owner node in a server cluster maintains ownership of a storage mechanism through a persistent reservation mechanism, while allowing non-owning nodes read and write access to the storage mechanism. An owner node writes a reservation key to a registration table associated with the storage mechanism. Non-owning nodes write a shared key that gives them read and write access. The owner node validates the shared keys against cluster membership data, and preempts (e.g., removes) any key deemed not valid. The owner node also defends ownership against challenges to ownership made by other nodes, so that another node can take over ownership if a (formerly) owning node is unable to defend, e.g., because of a failure.