LEIRealTime活动的设计要求在LEI故障转移集群中对这些活动进行不同的处理。
The design of LEI RealTime activities requires that they be handled differently in the LEI failover cluster.
不过，如果集群中发生多个故障转移，RS节点可以防止您的数据库变得完全不可用。
Should multiple failures in a cluster occur, however, an RS node can prevent your database from being entirely unavailable.
为了转移负载，集群中的计算机必须彼此连接起来。
For passing loads, computers in a cluster must be connected to each other.
如果高可用性集群中的某一个服务器出现故障，那么集群软件将把出故障的服务器上的工作负载转移到集群中仍然正常的一个服务器上。
If one of the servers in the high availability cluster was to fail, then clustering software would transfer the failed server's workload to a surviving server in the cluster.
DB 2包含一组内置集群服务，它使您能够为两个服务器建立高可用性集群，甚至自动化HADR解决方案的故障转移。
DB2 includes a set of built-in clustering services that give you the ability to cluster together two servers for high availability and even automate the fail-over of an HADR solution.
集群管理器需要知道故障转移是在什么时候发生的，以便把相应节点的职责转移给集群中的其他节点。
The cluster manager needs to know when failover occurs to transfer that node's responsibilities to other nodes in the cluster.
集群提供了工作负载管理以及url和ejb请求故障转移。
Clustering provides workload management and failover of URL and EJB requests.
如果高可用性集群中某一个服务器出故障，那么集群软件就会将工作负载转移到idle备用数据库服务器。
If one of the servers in the high availability cluster fails, then the clustering software transfers the workload to the idle standby database server.
如果高可用性集群中某一个服务器出现故障，那么集群软件就会将工作负载转移到warm备用数据服务器。
If one of the servers in the high availability cluster fails, then the clustering software transfers the workload to the warm standby server.
为了优化机器的使用并维护HA，我们在每个站点设计了一个4节点集群：一个节点对应一个应用程序，剩下的一个节点充当故障转移节点。
To optimize the use of machines and to maintain ha, we designed for a four-node cluster at each site: one node per application and a spare node that will serve as the failover node.
如果其中一个服务器失败，消息传递和BusinessEvents事件处理将故障转移至集群中的另一个服务器。
If a server fails, both the messaging and Business Events event processing will fail over to another server within the cluster.
测试MQ集群中的故障转移场景。
其他集群解决方案，比如MicrosoftClusters (Wolfpack)，也提供数据库故障转移，但其转移目标是使用数据库的单个实例的集群成员。
Other clustering solutions, such as Microsoft Clusters (Wolfpack), provide failover of databases to other cluster members using only a single instance of the database.
MDP与通用的可伸缩性和可用性机制(集群、负载平衡、故障转移、缓存等)相兼容。
MDP is compatible with common scalability and availability mechanisms (clustering, load balancing, failover, caching, etc).
现在，您已经得到了一个可以正常工作的集群，接下来即可创建流量IP地址分组(并使之能够在集群中的一台机器发生故障时进行故障转移)。
Now that you have a working cluster, you can create Traffic IP address groups (and have them failover if one of the machines in the cluster fails).
这个协议为集群中的每个应用程序节点提供了精确的故障转移顺序。
This protocol provides the precise failover sequence for each of the application nodes in the cluster.
由于您只有两个节点，因此要为每个节点的每个集群分配一个成员，以确保执行故障转移。
Since you only have two nodes, you will assign a member of each cluster to each node to ensure failover.
如果没有在峰值负载下积极测试和验证集群，那么在真正发生故障时，故障转移的一端可能受到资源限制，响应时间较长，甚至出现故障。
If you do not actively test and validate your clustering during peak loads, during an actual failure the failover side can become constrained and deliver poor response times or even fail.
如果集群中的某一个服务器出现故障，那么集群软件将把出故障的服务器上的工作负载转移到集群中仍然正常的一个服务器上。
If one of the servers in the cluster was to fail, then clustering software would transfer that failed server's workload to a surviving server in the cluster.
仅使用两个集群成员，故障转移将无法实现，因为每个ME分配了自己的数据存储区，并且对于一个SIB，每个集群成员仅有一个ME能够是活动的。
With only two cluster members fail over is not possible, because each me has its own datastore assigned and only one me per cluster member can be active for one sib.
如果原始集群节点出现问题(故障转移情况)，则会话数据还必须复制到其他的集群节点。
The session data also needs to be replicated to other cluster nodes, in case the original cluster node goes down (failover scenario).
如果您选择返回您的原始集群配置，那么您可以计划适当的故障转移操作。
If you choose to get back to your original cluster configuration, you can suitably plan appropriate failover operations.
不过，为确保故障转移，您需要为每个消息传递引擎配置单独的集群。
To ensure failover, however, you need to configure separate clusters for each messaging engine.
如果您选择返回您的原始集群配置，那么您可以计划适当的故障转移操作。
If you choose to get back to your original cluster configuration, you can plan appropriate failover operations.
具有故障转移功能的可伸缩集群在数据仍然在运动的同时仍然能够高效地处理实时反馈，并且都在商业机器上完成。
Real-time feeds can be processed efficiently while the data is still in motion, running on scale-out clusters with fail-over capability, and all performed on commodity machines.
如果其他流量管理器在5秒钟内未看到一个流量管理器的心跳，则集群的其他部分将认为此流量管理器已经发生故障，并启动故障转移。
In the event that one traffic manager's heartbeats are not seen by the others for 5 seconds, the rest of the cluster assumes that it has failed and initiates a failover.
如果心跳被中断，集群可能会根据配置发起一次故障转移。
If the heartbeat is interrupted, the cluster may initiate a failover depending on the configuration.
您需要为负载平衡建立一个服务器集群，并测试其故障转移机制(请参阅参考资料)。
You need to set up a cluster of servers for load balancing and test the failover mechanism (see Resources).
发生故障转移的情况有两种：一是系统管理员指示集群中的节点执行故障转移；二是出现灾难性应用程序或服务器故障的情况迫使资源组转移。
Failover can occur when a systems administrator instructs the nodes in the cluster to do so or when circumstances like a catastrophic application or server failure forces the resource groups to move.
实际上，一些供应商通过为HA解决方案提供10天的故障转移使用就宣称会带来某种形式的优势；然而，使用DB2，对于相同类型的集群来说这种优势真的是无限的。
In fact, some vendors claim some sort of advantage by offering 10 days of failover use for an HA solution; however, with DB2, it's really unlimited for the same kind of clusters.
应用推荐