The design of LEI RealTime activities requires that they be handled differently in the LEI failover cluster.
LEIRealTime活动的设计要求在LEI故障转移集群中对这些活动进行不同的处理。
This protocol provides the precise failover sequence for each of the application nodes in the cluster.
这个协议为集群中的每个应用程序节点提供了精确的故障转移顺序。
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.
发生故障转移的情况有两种：一是系统管理员指示集群中的节点执行故障转移；二是出现灾难性应用程序或服务器故障的情况迫使资源组转移。
If you choose to get back to your original cluster configuration, you can suitably plan appropriate failover operations.
如果您选择返回您的原始集群配置，那么您可以计划适当的故障转移操作。
Failover is another feature of this, meaning that at any time, one of the nodes in the cluster could fail, and the state of a user's session would survive on another machine in the cluster.
故障转移是群集的另一个功能，表示在任何时候，如果群集中的某个节点发生故障，用户会话的状态会在群集中的另一台机器上保留。
If you choose to get back to your original cluster configuration, you can plan appropriate failover operations.
如果您选择返回您的原始集群配置，那么您可以计划适当的故障转移操作。
Since you only have two nodes, you will assign a member of each cluster to each node to ensure failover.
由于您只有两个节点，因此要为每个节点的每个集群分配一个成员，以确保执行故障转移。
The session data also needs to be replicated to other cluster nodes, in case the original cluster node goes down (failover scenario).
如果原始集群节点出现问题(故障转移情况)，则会话数据还必须复制到其他的集群节点。
You need to set up a cluster of servers for load balancing and test the failover mechanism (see Resources).
您需要为负载平衡建立一个服务器集群，并测试其故障转移机制(请参阅参考资料)。
The problem with this is that the disaster recovery site needs to hold the current state of the cluster in order to be immediately useful during a failover.
这种方法的问题在于灾难恢复站点需要储存集群的当前状态，以在故障转移期间立即可用。
NODE3: This machine is the HADR standby server for DB2 failover and does not fall under the TSA cluster domain setup.
NODE3：这台机器是用于DB 2故障恢复的HADR备用服务器，它不属于tsa集群域设置。
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.
如果其他流量管理器在5秒钟内未看到一个流量管理器的心跳，则集群的其他部分将认为此流量管理器已经发生故障，并启动故障转移。
However, without a cluster manager, this "failover" is not automatic.
尽管如此，没有集群管理，“切换”就不能自动完成。
Performance mode enables a cluster containing all Version 6 servers to execute workload balancing and failover more efficiently.
性能模式能使一个包含所有版本6服务器的集群更有效的执行负载均衡和灾难恢复。
The cluster manager needs to know when failover occurs to transfer that node's responsibilities to other nodes in the cluster.
集群管理器需要知道故障转移是在什么时候发生的，以便把相应节点的职责转移给集群中的其他节点。
Failover is where a cluster node fails.
故障转移是集群节点发生故障的地方。
However for a production environment, you need to install a Rational Asset Manager cluster for workload balancing and failover capabilities.
但是对于生产环境来说，需要安装RationalAssetManager集群来提供负载均衡和故障切换功能。
Figure 2 depicts a typical RAC physical topology in a WebSphere Application Server cluster environment, where both the failover and load balancing Qualities of Service are enabled.
图2描述了WebSphereApplicationServer集群环境中的典型rac物理拓扑，在此环境中，同时支持故障转移和负载平衡服务质量。
Starting the cluster and testing the failover.
启动群集测试自动修正。
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).
现在，您已经得到了一个可以正常工作的集群，接下来即可创建流量IP地址分组(并使之能够在集群中的一台机器发生故障时进行故障转移)。
If the heartbeat is interrupted, the cluster may initiate a failover depending on the configuration.
如果心跳被中断，集群可能会根据配置发起一次故障转移。
Stop all cluster members on a given node, enabling the application clients to failover to cluster members on other nodes.
在给定的节点上停止所有的集群成员，使应用程序客户端恢复到其他节点上的集群成员。
Although live migration was an important feature for load balancing over a cluster of servers, failover built on live migration opens new applications within the cloud for HA-dependent applications.
尽管动态迁移是在服务器群集上实现负载平衡的一项重要功能，基于动态迁移构建的故障恢复在针对依赖HA的应用程序的云中打开新的应用程序。
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.
为了优化机器的使用并维护HA，我们在每个站点设计了一个4节点集群：一个节点对应一个应用程序，剩下的一个节点充当故障转移节点。
Testing the failover scenarios in the MQ cluster.
测试MQ集群中的故障转移场景。
Other clustering solutions, such as Microsoft Clusters (Wolfpack), provide failover of databases to other cluster members using only a single instance of the database.
其他集群解决方案，比如MicrosoftClusters (Wolfpack)，也提供数据库故障转移，但其转移目标是使用数据库的单个实例的集群成员。
For example, you can also get connection load balancing and failover using the Oracle provided JDBC connection pool [14] along with Oracle Real Application Cluster [15].
举例来说，你也可以使用Oracle ReaApplicationCluster[15]提供的JDBC连接池[14]以获得连接的负载均衡和失败转移。
The cluster consisted of two active Domino servers replicating their mail files to one standby server for failover purposes only (no load balancing).
这个集群有两个活动Domino服务器，仅在出现故障时将它们的邮件文件复制到一个备用服务器（没有负载平衡）。
This article assumes that we have a two-node cluster with Node1 as the primary node and Node2 as the failover/fallover/takeover/stand-by/secondary node, as shown below in Figure 1.
本文假设集群中有两个节点，Node1是主节点，Node2 是故障转移/接管/备用/辅助节点，见图 1。
Tomcat-cluster: Web-tier clustering, load balancer, and failover sample for the embedded Apache tomcat Web container.
tomcat - cluster：嵌入式Apachetomcatweb容器的We b层集群、负载平衡和故障转移示例。
应用推荐