Maximo is continuously available on the spare node.
Maximo将一直可在空闲节点上使用。
For the second failure, case 1: If a fails, it is placed on the spare node.
对于第二次故障，情形1：如果A出现故障，它将被转移到空闲节点上。
The example we used here is a three-application, three-node system with one spare node.
我们在此处使用的示例是一个包含3个应用程序、3个节点的系统，其中包含一个空闲节点。
All of the stated conditions are true if we cannot have applications coexist on the spare node.
如果空闲节点上不能同时存在多个应用程序，那么所有指定的条件都为真。
In the event of a malfunction, the VCS fails over the components from the malfunctioning node to the spare node.
发生故障时，VCS会将组件从发生故障的节点故障切换至备用节点。
For the second failure, case 2: If eCMDB is on the spare node, then the subsequent failure of ITIC will not change the status quo; however, Maximo will bump eCMDB from the spare node.
对于第二次故障，情形2：如果eCMD b位于空闲节点上，那么ITIC随后出现故障时将不会更改现状，但是Maximo将从空闲节点上转储ecmdb。
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节点集群：一个节点对应一个应用程序，剩下的一个节点充当故障转移节点。
If no node but the spare is available in the cluster, Maximo will be the only application running.
如果集群中只有空闲节点可用，那么Maximo将是惟一运行的应用程序。
Four-node cluster with one passive spare.
节点集群中有一个被动空闲节点。
Four-node cluster with one passive spare.
节点集群中有一个被动空闲节点。
应用推荐