恢复日志的安全是至关重要的。
它把记录写入恢复日志，增加事务状态信息。
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.
注意我们仅仅着眼于恢复日志而不是数据库文件。
Notice we are only looking at the recovery log — not database files.
根据当前的使用情况，恢复日志的大小可能也需要增加。
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.
高度可用的事务日志恢复。
完成崩溃恢复之后，将启动一个新的日志链。
After the completion of the crash recovery, a new log chain will be started.
为了获得高可用性和进行故障恢复，我们推荐使用事务日志。
We recommend transaction logging for high availability and failure recovery.
一个关键的优点在于系统崩溃后的数据恢复，当使用日志结构方法时，这种恢复更简单。
One key advantage is recovery from system crashes, which is simpler using the log-structured approach.
下面是连续逻辑日志恢复的流程。
活跃日志是崩溃恢复需要的日志。
高可用灾难恢复(如hadr日志延迟；这一类别是DB 2“Stinger”中新增的)。
High Availability Disaster Recovery (for example, HADR log delay; this category is new to DB2 V8.2).
从未归档联机日志文件的丢失中恢复。
从惟一活动重做日志组的丢失中恢复。
从丢失的联机重做日志组的成员中进行恢复。
Recovering from the loss of one member of an online redo log group.
从当前重做日志组的丢失中恢复。
研究结果表明，利用事务日志可以实现无数据丢失的完全恢复。
The result shows that the complete recovery can be implemented by transaction log.
必须将数据库置于回避恢复模式下才能重建日志。
Database must be put in bypass recovery mode to rebuild the log.
必须将数据库置于回避恢复模式下才能重建日志。
Database must be put in bypass recovery mode to rebuild the log.
应用推荐