-
公开(公告)号：US20100138384A1
公开(公告)日：2010-06-03
申请号：US12697375
申请日：2010-02-01
IPC分类号： G06F17/00
CPC分类号： G06F17/30289 , G06F11/1469 , G06F17/30073 , G06F17/30082 , G06F17/30117 , G06F17/30188 , G06F17/30197 , G06F17/30221 , Y10S707/99932 , Y10S707/99944 , Y10S707/99956
摘要： An archive cluster application runs in a distributed manner across a redundant array of independent nodes. Each node preferably runs a complete archive cluster application instance. A given nodes provides a data repository, which stores up to a large amount (e.g., a terabyte) of data, while also acting as a portal that enables access to archive files. Each symmetric node has a set of software processes, e.g., a request manager, a storage manager, a metadata manager, and a policy manager. The request manager manages requests to the node for data (i.e., file data), the storage manager manages data read/write functions from a disk associated with the node, and the metadata manager facilitates metadata transactions and recovery across the distributed database. The policy manager implements one or more policies, which are operations that determine the behavior of an “archive object” within the cluster. The archive cluster application provides object-based storage. Preferably, the application permanently associates metadata and policies with the raw archived data, which together comprise an archive object. Object policies govern the object's behavior in the archive. As a result, the archive manages itself independently of client applications, acting automatically to ensure that all object policies are valid.
摘要翻译： 归档集群应用程序通过独立节点的冗余阵列以分布式方式运行。 每个节点最好运行一个完整的归档集群应用实例。 给定的节点提供了一个数据存储库，它可以存储大量数据（例如，一千兆字节）的数据，同时还充当允许访问存档文件的门户。 每个对称节点具有一组软件过程，例如请求管理器，存储管理器，元数据管理器和策略管理器。 请求管理器管理对节点的数据（即文件数据）的请求，存储管理器从与该节点相关联的盘管理数据读/写功能，并且元数据管理器便于跨分布式数据库的元数据事务和恢复。 策略管理器实现一个或多个策略，这些策略是确定集群中“归档对象”的行为的操作。 归档集群应用程序提供基于对象的存储。 优选地，应用程序将元数据和策略永久地关联到原始归档数据，其一起构成归档对象。 对象策略管理对象在归档中的行为。 因此，归档管理自身独立于客户端应用程序，自动执行以确保所有对象策略都有效。
-
公开(公告)号：US20120246126A1
公开(公告)日：2012-09-27
申请号：US13449368
申请日：2012-04-18
IPC分类号： G06F17/30
CPC分类号： G06F17/30289 , G06F11/1469 , G06F17/30073 , G06F17/30082 , G06F17/30117 , G06F17/30188 , G06F17/30197 , G06F17/30221 , Y10S707/99932 , Y10S707/99944 , Y10S707/99956
摘要： An archive cluster application runs across a redundant array of independent nodes. Each node runs an archive cluster application instance comprising a set of software processes: a request manager, a storage manager, a metadata manager, and a policy manager. The request manager manages requests for data, the storage manager manages data read/write functions, and the metadata manager facilitates metadata transactions and recovery. The policy manager implements policies, which are operations that determine the behavior of an “archive object” within the cluster. The archive cluster application provides object-based storage. It associates metadata and policies with the raw archived data, which together comprise an archive object. Object policies govern the object's behavior in the archive. The archive manages itself independently of client applications, acting automatically to ensure that object policies are valid.
摘要翻译： 归档集群应用程序跨独立节点的冗余阵列运行。 每个节点运行包含一组软件过程的归档集群应用程序实例：请求管理器，存储管理器，元数据管理器和策略管理器。 请求管理器管理数据请求，存储管理器管理数据读/写功能，元数据管理器便于元数据事务和恢复。 策略管理器实现策略，这些策略是确定集群中“归档对象”的行为的操作。 归档集群应用程序提供基于对象的存储。 它将元数据和策略与原始归档数据相关联，这些数据共同构成归档对象。 对象策略管理对象在归档中的行为。 归档管理自身独立于客户端应用程序，自动执行以确保对象策略有效。
-
公开(公告)号：US20090006888A1
公开(公告)日：2009-01-01
申请号：US11936317
申请日：2007-11-07
IPC分类号： G06F11/20
CPC分类号： G06F11/08 , G06F11/1662 , G06F11/2028 , G06F11/2094 , G06F11/2097
摘要： A cluster recovery process is implemented across a set of distributed archives, where each individual archive is a storage cluster of preferably symmetric nodes. Each node of a cluster typically executes an instance of an application that provides object-based storage of fixed content data and associated metadata. According to the storage method, an association or “link” between a first cluster and a second cluster is first established to facilitate replication. The first cluster is sometimes referred to as a “primary” whereas the “second” cluster is sometimes referred to as a “replica.” Once the link is made, the first cluster's fixed content data and metadata are then replicated from the first cluster to the second cluster, preferably in a continuous manner. Upon a failure of the first cluster, however, a failover operation occurs, and clients of the first cluster are redirected to the second cluster. Upon repair or replacement of the first cluster (a “restore”), the repaired or replaced first cluster resumes authority for servicing the clients of the first cluster. This restore operation preferably occurs in two stages: a “fast recovery” stage that involves preferably “bulk” transfer of the first cluster metadata, following by a “fail back” stage that involves the transfer of the fixed content data. Upon receipt of the metadata from the second cluster, the repaired or replaced first cluster resumes authority for the clients irrespective of whether the fail back stage has completed or even begun.
摘要翻译： 在一组分布式归档中实现集群恢复过程，其中每个单独的归档是优选对称节点的存储集群。 集群的每个节点通常执行提供固定内容数据和关联元数据的基于对象的存储的应用的实例。 根据存储方法，首先建立第一集群和第二集群之间的关联或“链接”以便于复制。 第一个集群有时被称为“主”，而“第二”集合有时被称为“副本”。 一旦建立了链接，则第一集群的固定内容数据和元数据然后从第一集群复制到第二集群，优选地以连续的方式。 但是，在第一个集群发生故障时，会发生故障转移操作，并将第一个集群的客户端重定向到第二个集群。 在修复或更换第一个集群（“恢复”）后，已修复或更换的第一个集群将恢复为第一个集群的客户端提供服务的权限。 该恢复操作优选地分为两个阶段：“快速恢复”阶段，其优选地涉及第一集群元数据的“批量”传送，之后是涉及传输固定内容数据的“故障恢复”阶段。 在从第二集群接收到元数据后，修复或更换的第一个集群将恢复客户端的权限，而不管故障后台是否已经完成甚至开始。
-
公开(公告)号：US20110178983A1
公开(公告)日：2011-07-21
申请号：US13072921
申请日：2011-03-28
IPC分类号： G06F17/30
CPC分类号： G06F11/08 , G06F11/1662 , G06F11/2028 , G06F11/2094 , G06F11/2097
摘要： A cluster recovery process is implemented across a set of distributed archives, where each individual archive is a storage cluster of preferably symmetric nodes. Each node of a cluster typically executes an instance of an application that provides object-based storage of fixed content data and associated metadata. According to the storage method, an association or “link” between a first cluster and a second cluster is first established to facilitate replication. The first cluster is sometimes referred to as a “primary” whereas the “second” cluster is sometimes referred to as a “replica.” Once the link is made, the first cluster's fixed content data and metadata are then replicated from the first cluster to the second cluster, preferably in a continuous manner. Upon a failure of the first cluster, however, a failover operation occurs, and clients of the first cluster are redirected to the second cluster. Upon repair or replacement of the first cluster (a “restore”), the repaired or replaced first cluster resumes authority for servicing the clients of the first cluster. This restore operation preferably occurs in two stages: a “fast recovery” stage that involves preferably “bulk” transfer of the first cluster metadata, following by a “fail back” stage that involves the transfer of the fixed content data. Upon receipt of the metadata from the second cluster, the repaired or replaced first cluster resumes authority for the clients irrespective of whether the fail back stage has completed or even begun.
摘要翻译： 在一组分布式归档中实现集群恢复过程，其中每个单独的归档是优选对称节点的存储集群。 集群的每个节点通常执行提供固定内容数据和关联元数据的基于对象的存储的应用的实例。 根据存储方法，首先建立第一集群和第二集群之间的关联或“链接”以便于复制。 第一个集群有时被称为“主要”，而“第二个”集群有时被称为“副本”。一旦建立了链接，第一个集群的固定内容数据和元数据将从第一个集群复制到 第二簇，优选以连续方式。 但是，在第一个集群发生故障时，会发生故障转移操作，并将第一个集群的客户端重定向到第二个集群。 在修复或更换第一个集群（“恢复”）后，已修复或更换的第一个集群将恢复为第一个集群的客户端提供服务的权限。 该恢复操作优选地分为两个阶段：“快速恢复”阶段，其优选地涉及第一集群元数据的“批量”传送，之后是涉及传输固定内容数据的“故障恢复”阶段。 在从第二集群接收到元数据后，修复或更换的第一个集群将恢复客户端的权限，而不管故障后台是否已经完成甚至开始。
-
-
-
搜索结果
4 条记录 (耗时 0.022 秒)
