Highly available transaction log recovery.
高度可用的事务日志恢复。
In the event of a system failure, transaction log recovery can apply or undo only those transactions not written to disk at the time of the failure.
在系统失败时，事务日志可以应用或取消失败时没有写入磁盘的那些事务。
We repeat the test suite for each of our storage layers. Again we rerun those test cases 2 times: once to test Transaction Log recovery and then to test Regular Shutdown.
我们会对每个存储层重复执行该测试套件，并且会重新运行这些测试用例2次：一次是测试事务日志恢复，然后测试常规的关闭。
Notice we are only looking at the recovery log — not database files.
注意我们仅仅着眼于恢复日志而不是数据库文件。
To maintain the integrity of a recovery log file, only a single client process can access the log at a time; this access can be assured using the exclusive network file locks discussed previously.
要保持恢复日志文件的完整性，一次只能允许单个客户端流程对其进行访问。 通过使用先前讨论到的排它网络文件锁定来确保访问的进行。
Safety of the recovery log is vital.
恢复日志的安全是至关重要的。
This process reads log files during rollback, restart recovery and roll forward.
此进程在回滚、重启恢复和前滚期间读取日志文件。
It writes records to a recovery log, plus transaction state information.
它把记录写入恢复日志，增加事务状态信息。
Although these conditions are rare, left unchecked they have the potential to cause recovery log collision and consequent loss of data integrity.
虽然这些情形不常见，但是却有导致恢复日志冲突且随之损失数据的完整性的潜在危险。
The second restores to the most recent state, using a combination of full backup plus rolling forward the transaction log, called rollforward recovery.
另一种机制通过使用全备份，并前滚事务日志，使数据库恢复到最近的状态，这种机制也叫前滚恢复。
In the case of the transaction service, the transaction HA policy provides the logic to determine which servers own a recovery log at any given time.
在事务服务场景中，事务ha策略提供逻辑以确定在规定时间内是哪台服务器拥有恢复日志。
Crash recovery is the processing of the log files, making sure all committed transactions are written to disk and uncommitted transactions are rolled back.
崩溃恢复是对日志文件进行处理，确保所有已提交的事务被写到磁盘，所有未提交的事务被回滚。
The recovery log size may also need to be increased depending on the current utilization.
根据当前的使用情况，恢复日志的大小可能也需要增加。
The recovery log is used insure data integrity during recovery processing, which we will illustrate later.
在恢复处理时，使用恢复日志保证数据的完整性，这一点稍后说明。
Primary log files establish a fixed amount of storage allocated to the recovery log files.
主日志文件建立了一个固定大小的存储空间，这是分配给恢复日志文件的。
If transactional high availability is not in use, no requirement exists to specify the transactions recovery log directory.
如果没有使用事务的高可用性，无需指定事务恢复日志目录。
This change was introduced to enable peer recovery of transaction log to complete in-doubt transactions when the machine hosting the transaction log crashes.
该变更的引入可以使得寄存事务日志的机器崩溃时，能够利用事务日志的同等恢复来完善不确定的事务。
Adding more than one server causes recovery log contention as both servers attempt to process recovery.
添加两个服务器将导致服务器争用恢复日志，因为两个服务器都试图处理恢复。
If transactional high availability is in use, the recovery log location must be provided to ensure that the recovery logs for a server are visible to all application servers in the cluster.
如果事务高可用性正在被使用，则必须提供恢复日志的位置，以确保服务器的恢复日志能被群中的所有应用服务器访问。
Access to a recovery log is only performed when the exclusive lock is held.
对恢复日志的访问只有在持有排它锁定时进行。
After the completion of the crash recovery, a new log chain will be started.
完成崩溃恢复之后，将启动一个新的日志链。
It described how this support enables recovery of the transaction log of a failed server by a running peer, and discussed scenarios under which manual and automated peer recovery are appropriate.
描述了该支持如何通过另一台对等服务器恢复故障服务器的事务日志。讨论了手动和自动对等恢复适用的场景。
The downside of a larger log buffer is that crash recovery can take slightly longer.
较大日志缓冲池的不利之处是，紧急事故恢复所花的时间可能要稍微长一点。
File locking is used to ensure exclusive access to the files that make up a recovery log.
使用文件锁定确保对组成恢复日志的文件的排它访问。
A requirement of a recovery log is that only one server has access to it (either for recovery processing or standard logging) at any time.
对于恢复日志来说，要求任何时间都只能有一台服务器对其进行访问(恢复处理或是标准的日志记录)。
Adding two servers causes recovery log contention as both servers attempt to own the associated recovery logs.
添加两台服务器将导致争用相关联的恢复日志。
The car scenario is very similar to the log analysis component of DB2 Recovery Expert.
这个汽车场景与DB 2Recovery Expert的日志分析组件非常类似。
This article describes a use case scenario for the log analysis component of DB2 Recovery Expert.
本文描述了DB 2RecoveryExpert的日志分析组件的一个用例场景。
Enable fail back to ensure that a failed server reclaims its recovery log when it restarts, and optionally enter a free-form description.
启用Failback确保发生故障的服务器在重启后能收回其恢复日志，并随意输入自由格式的描述。
Db2loggr: For manipulating log files to handle transaction processing and recovery.
db2loggr：该进程操作日志文件用于处理事务进程和恢复。
应用推荐