恢复日志的安全是至关重要的。
它把记录写入恢复日志，增加事务状态信息。
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.
添加两台服务器将导致争用相关联的恢复日志。
Adding two servers causes recovery log contention as both servers attempt to own the associated recovery logs.
注意我们仅仅着眼于恢复日志而不是数据库文件。
Notice we are only looking at the recovery log — not database files.
使用文件锁定确保对组成恢复日志的文件的排它访问。
File locking is used to ensure exclusive access to the files that make up a recovery log.
根据当前的使用情况，恢复日志的大小可能也需要增加。
The recovery log size may also need to be increased depending on the current utilization.
如果没有使用事务的高可用性，无需指定事务恢复日志目录。
If transactional high availability is not in use, no requirement exists to specify the transactions recovery log directory.
服务器P在主机p上运行，且对其恢复日志文件持有排它文件锁定。
Server P is running on host P and holds an exclusive file lock for its own recovery log files.
在恢复处理时，使用恢复日志保证数据的完整性，这一点稍后说明。
The recovery log is used insure data integrity during recovery processing, which we will illustrate later.
该清单确定在同一时间内，试图拥有相关联的恢复日志的一组服务器。
This list identifies the set of servers that attempt to own the associated recovery logs at the same time.
要使服务器之间能执行对等恢复，服务器必须可对恢复日志进行修改。
For application servers to perform peer recovery for each other, it is necessary for them to access the recovery logs.
Database - 1查看它的恢复日志，发现有不完全的事务。
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.
通过还原脱机或联机备份并使用回滚操作来恢复日志，就可处理这些故障。
These failures are handled by restoring either offline or online backups and using roll-forward operations to recover the logs.
在静态组服务器清单上，列出的都是在同时间试图持有恢复日志的服务器。
The list of static group servers can be thought of as the set of servers that attempts to own the recovery logs at the same time.
主日志文件建立了一个固定大小的存储空间，这是分配给恢复日志文件的。
Primary log files establish a fixed amount of storage allocated to the recovery log files.
添加不同的服务器将阻碍主服务器收回恢复日志，且主服务器不能正确启动。
Adding a different server prevents the home server from owning its recovery logs and stops the home server from starting correctly.
添加两个服务器将导致服务器争用恢复日志，因为两个服务器都试图处理恢复。
Adding more than one server causes recovery log contention as both servers attempt to process recovery.
恢复日志文件选项恢复备份映像中保存的日志文件(适用于在线备份和恢复)。
Restore log file option restores the log files saved in the backup image (more applicable for online backup and restore).
虽然这些情形不常见，但是却有导致恢复日志冲突且随之损失数据的完整性的潜在危险。
Although these conditions are rare, left unchecked they have the potential to cause recovery log collision and consequent loss of data integrity.
在事务服务场景中，事务ha策略提供逻辑以确定在规定时间内是哪台服务器拥有恢复日志。
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.
该要求只运用于对等恢复处理；服务器恢复日志的标准恢复处理在服务器开启后，仍将自动运行。
This requirement applies to peer recovery processing only; standard recovery processing of server recovery logs, driven when the server starts, still occurs automatically.
对于恢复日志来说，要求任何时间都只能有一台服务器对其进行访问(恢复处理或是标准的日志记录)。
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.
启用Failback确保发生故障的服务器在重启后能收回其恢复日志，并随意输入自由格式的描述。
Enable fail back to ensure that a failed server reclaims its recovery log when it restarts, and optionally enter a free-form description.
故障发生后，如图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.
当操作者使用手动对等恢复引发对出现故障的服务器的对等恢复处理时，可对恢复日志进行强制访问。
When using manual peer recovery, this access is enforced by the operator who only triggers peer recovery processing for servers that are unavailable.
EBS存储卷是用来存储DB 2数据和DB 2恢复日志，目前是50gb，但要考虑RAID应对未来需要。
EBS volumes are used to store DB2 data and DB2 recovery logs, currently at 50gb, but RAID may be considered for future needs.
如果事务高可用性正在被使用，则必须提供恢复日志的位置，以确保服务器的恢复日志能被群中的所有应用服务器访问。
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.
Database - 2把Undo和do记录及状态写入它的恢复日志，再次像Database - 1做的一样。
Database-2 writes Undo and do records and state to its recovery log, again just as Database-1 did.
应用推荐