Safety of the recovery log is vital.
恢复日志的安全是至关重要的。
Notice we are only looking at the recovery log — not database files.
注意我们仅仅着眼于恢复日志而不是数据库文件。
It writes records to a recovery log, plus transaction state information.
它把记录写入恢复日志，增加事务状态信息。
Access to a recovery log is only performed when the exclusive lock is held.
对恢复日志的访问只有在持有排它锁定时进行。
Database-1 looks at its recovery log and notices that it had an incomplete transaction.
Database - 1查看它的恢复日志，发现有不完全的事务。
Database-1 looks at its recovery log and notices that it has an incomplete transaction.
Database - 1查看它的恢复日志，发现有不完全的事务。
The recovery log size may also need to be increased depending on the current utilization.
根据当前的使用情况，恢复日志的大小可能也需要增加。
File locking is used to ensure exclusive access to the files that make up a recovery log.
使用文件锁定确保对组成恢复日志的文件的排它访问。
Primary log files establish a fixed amount of storage allocated to the recovery log files.
主日志文件建立了一个固定大小的存储空间，这是分配给恢复日志文件的。
Server P is running on host P and holds an exclusive file lock for its own recovery log files.
服务器P在主机p上运行，且对其恢复日志文件持有排它文件锁定。
Database-2 writes Undo and do records and state to its recovery log, again just as Database-1 did.
Database - 2把Undo和do记录及状态写入它的恢复日志，再次像Database - 1做的一样。
Adding more than one server causes recovery log contention as both servers attempt to process recovery.
添加两个服务器将导致服务器争用恢复日志，因为两个服务器都试图处理恢复。
The recovery log is used insure data integrity during recovery processing, which we will illustrate later.
在恢复处理时，使用恢复日志保证数据的完整性，这一点稍后说明。
Adding two servers causes recovery log contention as both servers attempt to own the associated recovery logs.
添加两台服务器将导致争用相关联的恢复日志。
If transactional high availability is not in use, no requirement exists to specify the transactions recovery log directory.
如果没有使用事务的高可用性，无需指定事务恢复日志目录。
Enable fail back to ensure that a failed server reclaims its recovery log when it restarts, and optionally enter a free-form description.
启用Failback确保发生故障的服务器在重启后能收回其恢复日志，并随意输入自由格式的描述。
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.
对于恢复日志来说，要求任何时间都只能有一台服务器对其进行访问(恢复处理或是标准的日志记录)。
Although these conditions are rare, left unchecked they have the potential to cause recovery log collision and consequent loss of data integrity.
虽然这些情形不常见，但是却有导致恢复日志冲突且随之损失数据的完整性的潜在危险。
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策略提供逻辑以确定在规定时间内是哪台服务器拥有恢复日志。
The lines for Database-1, Database-2, and Coordinator represent both time (flowing left to right) and also some key records recorded onto a recovery log.
Database-1、Database-2、和Coordinator 的直线同时表示时间（从左到右流逝）和一些已记录到恢复日志的重要记录。
Database-1 contacts the coordinator (how to do this is encoded in the state information on the recovery log for this transaction — or is otherwise known).
Database - 1联系协调器(关于如何进行联系，这在用于该事务的恢复日志的状态信息中编码表示——或者是已知的)。
To prevent such problems from occurring, WebSphere Application Server USES network file locking technology to ensure exclusive access to recovery log files.
要避免这样的危险发生，WebSphereApplicationServer使用网络文件锁定技术来确保对恢复日志文件的排它访问。
Log sequence-based recovery log sequence-based recovery is a recovery that recovers until the specified log sequence number (only available when using recovery Manager).
基于日志序列的恢复是恢复直到指定日志序列号(只有在使用RecoveryManager时才可用)的恢复。
Information on how to contact the coordinator is in the state saved on its recovery log; with web services it will be an end point reference (EPR — defined in WS-Addressing).
有关联系协调器方法的信息保存在恢复日志中；使用Web服务，会有一个结束点参考(epr——在WS - Addressing中定义)。
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.
如果事务高可用性正在被使用，则必须提供恢复日志的位置，以确保服务器的恢复日志能被群中的所有应用服务器访问。
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.
要保持恢复日志文件的完整性，一次只能允许单个客户端流程对其进行访问。 通过使用先前讨论到的排它网络文件锁定来确保访问的进行。
Apart from enabling high availability and configuring the recovery log location for each cluster member, no additional WebSphere Application Server configuration steps are required to use this model.
除了对每个群成员启用高可用性和设定恢复日志所处位置外，使用该模式无需额外的WebSphereApplicationServer配置步骤。
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次：一次是测试事务日志恢复，然后测试常规的关闭。
This process reads log files during rollback, restart recovery and roll forward.
此进程在回滚、重启恢复和前滚期间读取日志文件。
The second restores to the most recent state, using a combination of full backup plus rolling forward the transaction log, called rollforward recovery.
另一种机制通过使用全备份，并前滚事务日志，使数据库恢复到最近的状态，这种机制也叫前滚恢复。
应用推荐