下面是连续逻辑日志恢复的流程。
高度可用的事务日志恢复。
当主系统出故障时，连续日志恢复特性使一个辅助系统可用，以替代主系统。
In case the primary system fails, the continuous log restore feature makes a secondary system available to replace the primary system.
首先是无需额外处理日至文件系统——你可以快照上简单地实现日志恢复。
First no extra handling is needed for journaling file systems - you can simply do journal recovery on snapshot.
如果主系统出故障，可以将剩下的可用逻辑日志恢复到辅助系统上，然后使后者上线，担任新的主系统。
If the primary system fails, the remaining available logical logs can be restored on the second system, which can then be brought online and function as the new primary system.
在完整恢复模式或大容量日志恢复模式下，如果最近尚未备份事务日志，则请立即进行备份以免发生日志截断。
Under the full recovery model or bulk-logged recovery model, if the transaction log has not been backed up recently, backup might be what is preventing log truncation.
我们会对每个存储层重复执行该测试套件，并且会重新运行这些测试用例2次：一次是测试事务日志恢复，然后测试常规的关闭。
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.
注意我们仅仅着眼于恢复日志而不是数据库文件。
Notice we are only looking at the recovery log — not database files.
恢复日志的安全是至关重要的。
它把记录写入恢复日志，增加事务状态信息。
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.
对于恢复，重做日志是必需的。
通过还原脱机或联机备份并使用回滚操作来恢复日志，就可处理这些故障。
These failures are handled by restoring either offline or online backups and using roll-forward operations to recover the logs.
根据当前的使用情况，恢复日志的大小可能也需要增加。
The recovery log size may also need to be increased depending on the current utilization.
日志包含可以恢复的最后一次备份之后的所有事务。
The logs contain all transactions since the last backup you were able to restore.
如果没有使用事务的高可用性，无需指定事务恢复日志目录。
If transactional high availability is not in use, no requirement exists to specify the transactions recovery log directory.
在联机恢复中，归档日志是必需的。
对恢复日志的访问只有在持有排它锁定时进行。
Access to a recovery log is only performed when the exclusive lock is held.
这个日志对故障恢复也很有用：如果元数据服务器发生故障，它的日志就会被重放，保证元数据安全存储在磁盘上。
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.
使用文件锁定确保对组成恢复日志的文件的排它访问。
File locking is used to ensure exclusive access to the files that make up a recovery log.
服务器P在主机p上运行，且对其恢复日志文件持有排它文件锁定。
Server P is running on host P and holds an exclusive file lock for its own recovery log files.
故障发生后，如图3所示，数据库和协调器最后可能会重新启动并使用恢复日志和恢复规则来确保数据完整性。
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.
循环日志只能支持版本恢复。
在检查点之间的事务被写入到一个事务日志中，并且，如果系统发生崩溃，事务将从事务日志中恢复。
Between checkpoints, transactions are written to a transaction log and, if the system crashes, transactions are recovered from the transaction log.
在恢复处理时，使用恢复日志保证数据的完整性，这一点稍后说明。
The recovery log is used insure data integrity during recovery processing, which we will illustrate later.
当ROLLFORWARD实用程序需要使用日志文件来恢复数据库时，就会检索它们。
They are retrieved when the ROLLFORWARD utility needs to use them to restore a database.
如果事务高可用性正在被使用，则必须提供恢复日志的位置，以确保服务器的恢复日志能被群中的所有应用服务器访问。
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.
一旦应用暂存的逻辑日志，只要从主要服务器接收到日志记录，就可以立即恢复应用日志记录。
Once the staged logical log records are applied, it continues to resume applying the log records as soon as they are received from the primary.
添加两个服务器将导致服务器争用恢复日志，因为两个服务器都试图处理恢复。
Adding more than one server causes recovery log contention as both servers attempt to process recovery.
主日志文件建立了一个固定大小的存储空间，这是分配给恢复日志文件的。
Primary log files establish a fixed amount of storage allocated to the recovery log files.
应用推荐