在备用节点上安装db2。
在备用节点上停止mi代理IBMESBBRK。
在备用节点上，您将发现以下代理进程正在运行。
On the standby node, you will find following broker processes running.
在当前的设置中，这个节点是被动节点，它作为集群的备用节点。
In the current setup, this node is the passive node and ACTS like a standby node for the cluster.
发生故障时，VCS会将组件从发生故障的节点故障切换至备用节点。
In the event of a malfunction, the VCS fails over the components from the malfunctioning node to the spare node.
在备用节点上，可以访问共享的增强型并发卷组，但是只能采用被动只读模式。
On the standby node, it has access to the shared enhanced-concurrent volume group, but only in a passive, read-only mode.
由于SD备用节点利用了主服务器的磁盘并且可以轻松快速地启动，因而非常适合规模扩展场景。
Because SD secondary nodes leverage the primary's disks and can be brought up easily and quickly, they are well-suited for scale-out scenarios.
在执行故障转移之前，备用节点上的文件系统没有挂载，所以不可能意外地使用备用节点上的数据。
File systems on the standby nodes are not mounted until the point of failover, so accidental use of data on standby nodes is not possible.
故障转移是主系统在计划内或计划外的关闭，并包括完成将备用节点置于在线以接管处理负载的任务。
Failover is the planned or unplanned shutdown of the primary system and includes the accompanying task of bringing a standby node online to take over the processing load.
每个代理实例都嵌入到一个WebSphereMQ服务中，以便当队列管理器切换到备用系统时，代理自动在备用节点上启动。
Each broker instance is embedded into a WebSphere MQ service so that, when the queue manager switches over to the standby system, the broker is automatically started on the standby node.
在备用节点上使用mqsiremovebrokerinstanceIBMESBBRK命令移除代理实例IBMESBBRK。
Remove the broker instance IBMESBBRK on the standby node using the mqsiremovebrokerinstance IBMESBBRK command.
这个拓扑结构中的第三个节点(Node3)由远程位置上的灾难恢复站点组成，它托管前面提到的主数据库的备用数据库。
The third node (Node3) in this topology consists of the disaster recovery site existing in a remote location and hosting the standby database for the primary database mentioned earlier.
备用方法(不在这里研究)是结果只将SimpleNode节点提供给解析树，而不是它的子类。
The alternative (not explored here) is for productions to contribute only SimpleNode nodes to the parse tree and not subclasses thereof.
要故意地让活动节点失效，您可以要求该节点暂停，或将其设为备用模式，方法是使用 hb_gui（完全关闭）命令。
To deliberately fail the active node, you can issue a halt on that node, or set it to standby mode using the hb_gui (clean take down) command.
本文假设集群中有两个节点，Node1是主节点，Node2 是故障转移/接管/备用/辅助节点，见图1。
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.
存在一个构建时任务以创建备用环境，以及一个运行时任务以在主节点和辅助节点之间切换。
There is a build time task to create the standby environment and run time tasks to toggle between the primary and secondary nodes.
该算法利用网格中节点的地理信息进行路由，并且选择一条最稳定的不相交备用路由。
EASBRA utilizes the node's geographical information to route and selects the most stable disjoint backup route.
根据安全定价方法得到不同节点备用容量价值，为备用结算补偿机制提供理论依据。
The value of reserve capacity is derived from security pricing and provides a theoretical basis for the settlement of reserve compensation scheme.
在组播树建立之初，计算好组播节点之间的最小代价路径，以便于出现故障之后寻找最优备用链路；
Using STP algorithm, the least cost paths between nodes are computed when computing the working tree, so the best backup path can be found as soon as the failure occurs.
在组播树建立之初，计算好组播节点之间的最小代价路径，以便于出现故障之后寻找最优备用链路；
Using STP algorithm, the least cost paths between nodes are computed when computing the working tree, so the best backup path can be found as soon as the failure occurs.
应用推荐