Failure and recovery tests should also be performed here so there should be at least two servers for each tier.
故障和恢复测试也应该在这里执行，以便每一层至少应该有两个服务器。
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.
这个日志对故障恢复也很有用：如果元数据服务器发生故障，它的日志就会被重放，保证元数据安全存储在磁盘上。
A useful transactional protocol requires that all the recovery cases for failure be covered in some way, either in the protocol or in the participants, and be enabled by the protocol.
有用的事务协议需要以某种方式隐藏故障的所有恢复案例，或者在协议中或者在参与者中，并且协议可以启用。
As described in this section, if you know the cause of an instance failure, a complete recovery may not be necessary.
正如本部分所描述的，如果导致实例故障的原因是已知的，就不必进行完全恢复。
However, the XA protocol does provide some additional integrity to this one-phase commit scenario in its provision of resynchronization and recovery logic for failure during commit processing.
不过，XA协议在提交进程失败时可以提供再同步和恢复逻辑，在这一点上确实比此单阶段提交场景多提供一些附加的完整性。
A TCS must be capable of organizing and controlling complex business operations including resource recruitment, business function management, concurrency control, and failure recovery.
TCS必须有能力组织并控制复杂业务运作，包括资源募集、业务功能管理、一致性控制，及失败恢复。
JTS also adds recovery after server failure, of course.
当然，在服务器失败后jts也添加恢复。
The recovery will be completed quickly so that data availability through a member failure will look similar to the hypothetical representation shown in Figure 22.
恢复将快速完成，这样经过成员故障的数据可用性看起来会与图 22 所示的假设性表示类似。
Active logs are logs that prevent lost of data during crash recovery such as power failure.
活跃日志防止在崩溃恢复(比如电源故障)期间的数据损失。
After the failure, the databases and the coordinator can eventually restart and use their recovery logs and recovery rules to insure data integrity as illustrated in Figure 3.
故障发生后，如图3所示，数据库和协调器最后可能会重新启动并使用恢复日志和恢复规则来确保数据完整性。
You can deploy a disaster recovery solution to allow customers to continue to run their businesses even in the unfortunate circumstance of a full site failure.
您可以部署一个灾难恢复解决方案以使客户在全站故障的不幸情况下仍能继续运行其业务。
Obviously, production may have many more than two so it can handle the intended load, but this staging environment need only have enough servers to adequately test the failure and recovery scenarios.
很明显，产品环境拥有的服务器可以远远多于两个，这样它可以处理预定的负载，而该临时环境只需要拥有足够的服务器来充分测试故障和恢复场景即可。
An administrator is not needed to solve a statement failure in terms of backup and recovery.
在备份和恢复方面，解决语句失败不需要管理员权限。
You can do this using a new configuration parameter, RTO_SERVER_RESTART which enables failure recovery by monitoring the workload and triggering checkpoints in a timely manner to meet the RTO policy.
可以使用新的配置参数rto_server_restart实现这一点，该参数允许监视工作负载，并及时触发检查点以满足rto策略，从而进行故障恢复。
The transaction manager also coordinates recovery activities of the resource managers when necessary, such as after a component failure.
在必要时(如组件失败后)，事务管理器还协调资源管理器的恢复活动。
In order to implement recovery from failure scenarios, the transaction manager and the resource manager must be able to recover from a failure at any point in the transactional flow.
为了执行从故障场景中恢复，事务管理器和资源管理器必须能够在事务流程的任何点从故障中恢复。
Distributing the failure recovery also allows the storage system to scale, because failure detection and recovery are distributed across the ecosystem.
分配故障恢复也允许存储系统扩展，因为故障检测和恢复跨生态系统分配。
Unlike a two-phase commit process, there is no recovery from a communication failure with a one-phase commit resource.
与两阶段提交进程不同，单阶段提交资源在通信失败时无法恢复。
There are many types of failure that cause a database to need recovery.
有多种类型的失败导致需要恢复数据库。
Note that this recovery time includes the failure detection times, which many vendors exclude when referring to recovery times.
注意，这个恢复时间包括故障检测时间，很多供应商在提到恢复时间时将这部分时间排除在外。
PPRC can be used to provide fast data recovery after failure of the primary site.
在主站点发生故障时，PPRC可用于提供快速数据恢复。
Unlike a two-phase commit resource, there is no recovery from a communication failure with a one-phase commit resource.
不像两阶段提交资源，单阶段提交资源不能从通信故障中恢复。
The recovery is completed quickly so that data availability through a member failure looks similar to the hypothetical representation in Figure 20.
这个恢复会很快完成，这样在出现成员错误期间的数据可用性会类似于图 20 所假定的情况。
We recommend transaction logging for high availability and failure recovery.
为了获得高可用性和进行故障恢复，我们推荐使用事务日志。
Failure and recovery of two followers.
两个follower同时失效和恢复。
Its thus much too early to tell whether the recovery will be rated a success or a failure.
因此，现在就来评定重建努力的成功或失败为时尚早。
Failure and recovery of a different follower.
不同的follower失效和恢复。
How the systems handle transaction failure and recovery?
系统如何处理事务失败与恢复？
How the systems handle transaction failure and recovery?
系统如何处理事务失败与恢复？
应用推荐