如果发生硬件故障，那么部署在故障硬件上的所有服务器都将不能使用。
If a hardware failure occurs, all the servers that are deployed on the failed hardware become unavailable.
现在，您已经得到了一个可以正常工作的集群，接下来即可创建流量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).
非IP网络：例如RS232（为了确保即使在发生网络故障的情况下 PowerHA 也能够区分网络故障和节点故障，需要非 IP 网络）
Non-IP networks: An example is RS232 (this is needed to make sure that even if the network goes down, PowerHA is capable of differentiating between network failure and node failure)
这个日志对故障恢复也很有用：如果元数据服务器发生故障，它的日志就会被重放，保证元数据安全存储在磁盘上。
The journal is also useful for failure recovery: if the metadata server fails, its journal can be replayed to ensure that metadata is safely stored on disk.
对于两个适配器同时发生故障的罕有情况，我们将需要两个额外的备用适配器，来处理所有潜在的单点故障。
For the very rare case when both adapters fail we would need to have two additional standby adapters to cover all potential single point of failure cases.
发生故障或者服务器从故障中恢复之后，它按需处理从一个系统到另一个的资源组的故障转移。
It handles the failing over of the resource groups from one system to the other as needed after a failure or after a coming back of a server from a failure.
磁盘是否会出现故障从来都不是考虑问题，要考虑的问题是故障会在何时发生。
It's never a matter of if a disk failure will occur but rather a question of when it will happen.
像航天飞机这样如此复杂的机器，发生的故障有时并没有那么严重，大多数故障都可以自行排除，或者影响很小。
The reverse side of failures in a machine as complex as the shuttle is that most of them can be worked around, or turn out to be small.
磁盘上的不可靠数据、电源故障、以及系统崩溃的等问题可能会导致调整过程发生灾难性故障。
Problems such as corrupt data on the disk, power failures, and system crashes can all cause catastrophic failure of the resizing process.
一个构建发生故障时，我希望能够立即知道这一情况，以便就能够采取适当的行动来解决这一问题——不论那是编译错误、测试故障甚或是整体复杂性的增加。
When a build is broken, I want to know immediately so I can take the proper action to fix it — whether that be a compilation error, test failure, or even an increase in overall complexity.
如果事件基础架构发生故障，那么可能导致客户端事务打上回滚标记(依赖于故障的种类)。
If the event infrastructure fails, then this may cause the client's transaction to be marked for rollback (depending on the nature of the failure).
如果没有在峰值负载下积极测试和验证集群，那么在真正发生故障时，故障转移的一端可能受到资源限制，响应时间较长，甚至出现故障。
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.
故障转移是群集的另一个功能，表示在任何时候，如果群集中的某个节点发生故障，用户会话的状态会在群集中的另一台机器上保留。
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.
当有故障发生时，只需暂停测试工作负载，让DB 2承担出故障的服务器的负载，这样就不必担心吞吐量降低。
In the event of a failure, you simply quiesce the test workload and let the DB2 standby assume the load of the failed server without consideration for throughput reduction.
通过将数据库的工作负载复制到单独的站点上，这些特性使服务在发生本地硬件故障或灾难性站点故障时不会中断。
By duplicating the workload of the database to a separate site, these features protect users from production downtime in the event of a local hardware failure or a catastrophic site failure.
如果发生数据库故障，则事务管理器将报告故障事务导致的不一致数据的可能性。
If a database failure occurs, the transaction manager reports the possibility of inconsistent data from failed transactions.
如果ha集群中的服务器之一发生故障，那么集群软件将重新把故障服务器的工作量分配到ha集群中的一台或多台幸存的服务器中。
If one of the servers in the HA cluster were to fail, then clustering software would redistribute the failed server's workload to one or more surviving servers in the HA cluster.
我们希望在发生火灾、洪水、电源故障、磁盘以及系统出现故障时，银行都能够保持正确的账户记录。
We expect Banks to correctly maintain account records in the face of fires, floods, power failures, disk failures, and system failures.
与环境相关的硬件故障发生的几率最小，而软件故障和计划停机占整个系统停机时间的70%。
The environmentally-related and hardware failures are the least likely to happen, whereas software failures and planned downtime contribute up to 70% of system downtime.
需要考虑的一个问题是，如果某个工作站上的一个软件片段发生故障，则其他工作站上的其他软件片段也可能发生故障。
One concern is that if one piece of the software on a workstation fails, other pieces of the software on other workstations may fail.
在发生故障时，例如在星期六进行增量备份之后发生了故障，那么只能恢复上个星期日的全备份并应用星期六的增量备份。
In the case of a failure, for example on Saturday after the incremental backup is taken, you can just restore the first Sunday full backup and apply the incremental on Saturday.
故障恢复/回退：这是在故障转移发生后将资源组移回其最初在其上运行的原始节点的操作。
Failback/fallback: This is the action of moving back resource groups to the nodes on which they were originally running after a failover has occurred.
如果其他流量管理器在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.
发生故障转移的情况有两种：一是系统管理员指示集群中的节点执行故障转移；二是出现灾难性应用程序或服务器故障的情况迫使资源组转移。
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.
当发生数据毁坏事故，例如软件故障、硬件故障、错误的应用程序逻辑和用户错误后，可以使用这些备份将数据库恢复到适当的状态。
These backups can be used to restore databases to their proper state after data corruption events, such as software failures, hardware failures, bad application logic, and user errors.
网络不断孕育着小的故障，以此来避免大故障的频繁发生。
A network nurtures small failures in order that large failures don't happen as often.
当故障在作用域中发生时，作用域中的正常处理被中断，发出的故障被传给捕获故障的处理程序。
When a fault occurs within a scope, the regular processing within the scope is interrupted and the signaled fault is passed to the catching fault handler.
服务器故障的发生可能有两种原因所致：软件故障或硬件故障。
Two types of potential server failure exist: software failure and hardware failure.
停止运行故障：与停机故障不同的是，这种故障发生的时候会通知其他组件。
Fail-stop: a halting failure with some kind of notification to other components.
故障转移是集群节点发生故障的地方。
应用推荐