如果您喜欢，你能调整记录容量和决定停留或恢复记录。
You can adjust the record volume and decide to pause or resume to record as you like.
我们将象大多数物种那样恢复记录，记起在这个叫做地球的一致实相中我们的真正位置。
We like most species are recovering our records and remembering our true place in this consensus reality known as earth.
经历会被复述，但参与者通常会在不记录活动的情况下恢复他们的日常生活。
Experiences are retold, but participants typically resume their daily routines without ever recording their activities.
它把记录写入恢复日志，增加事务状态信息。
It writes records to a recovery log, plus transaction state information.
如果其他站点或服务器也必须把您的灾难恢复服务器输入它们的安全设置，有DNS记录会有帮助。
Having a DNS record can help when other sites or servers must also enter your disaster recovery server into their security Settings.
您将要删除一些记录，而能够把表恢复到默认状态对于稍后的测试将十分有用。
You will be deleting some records, and it will be helpful to be able to restore the tables to a default state for later testing.
现在应该实际运行一次完整的灾难恢复测试：仅仅记录数据并“认真考虑”这个步骤是不够的。
You should now focus on actually running a full disaster recovery exercise: Just recording data and "thinking seriously" about this step won't cut it.
如果一个服务删除一条记录，补偿则恢复这条记录。
If the service deletes a record, the compensation restores the record.
使用db代理的备份和恢复操作将被记录下来用于审计，并默认发送给安全服务器。
Backup and restore operations with the DB agent are logged for audit and sent to the security server by default.
我们必须恢复对孩子们的比赛结果加以记录，并只向那些获胜者颁发奖杯的做法。
We have to go back to keeping the scores of kids' games and giving trophies only to the ones who win.
在执行灾难恢复测试和发生实际灾难时要修改A记录。
You change the A record when a disaster recovery exercise is run and in an actual disaster.
如果记录了各个活动，就很容易进行调试和快速恢复环境。
If the activities are logged, it is easy to debug and restore the environment quickly.
一旦应用暂存的逻辑日志，只要从主要服务器接收到日志记录，就可以立即恢复应用日志记录。
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.
出于这个原因，常常会发现冗余gc记录中的永久自由内存下降并且不会恢复。
For this reason, it's normal to see the immortal free memory in the verbose GC log drop without ever recovering.
在数据库的恢复期间，该记录的使用具有排它性。
日志文件系统是使用日志来缓冲文件系统的修改(同时也可以应用于紧急故障恢复)的，但可以根据记录的时间与内容采取不同的策略。
Journaling file systems use a journal to buffer changes to the file system (which is also used in crash recovery) but can use different strategies for when and what is journaled.
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.
Database - 1使用恢复Rulea并且应用它的Undo记录。
Database-1、Database-2、和Coordinator 的直线同时表示时间（从左到右流逝）和一些已记录到恢复日志的重要记录。
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.
如果需要执行恢复，可以看一看ON - Bar备份的旧逻辑记录文件，以确定问题所在。
If you need to perform a restore, you can view the old logical-log files that were backed up by ON-Bar to find out the exact problem.
最后，exception包包含SOAException基类。它用于记录错误条件并触发事务重试和恢复逻辑。
Finally, the exception package contains the SOAException base class, which is used to log error conditions and trigger the transaction retry and recovery logic.
如果你只记录到秒，你就无法恢复原始时间顺序。
If you only log to the second, you cannot reestablish the chronology.
注意，如果决定使用循环日志记录和脱机恢复作为您的备份策略，那么最后一次脱机备份以后的所有事务都将丢失。
Be aware that if you decide to use circular logging and offline recovery as your backup strategy, all transactions after the last offline backup will be lost.
如果一个服务更新一条记录，补偿则恢复原始值。
If a service updates a record, the compensation restores the original value.
您至少应该拥有三种类型的文档：历史记录、过程和灾难恢复。
At a minimum, you should have three types of documentation: historical, procedures, and disaster recovery.
同样，更新和删除也会被记录，并保存足够数据用于恢复。
Similarly, updates and deletes are also logged with sufficient data needed for recovery purposes.
可恢复流程记录其操作，这样在发生故障时可以恢复到较早的状态。
Recoverable processes log their actions and thus can restore earlier states if a failure occurs.
因为能交换操作顺序而不影响最终结果，所以我们才能在网络或者硬件临时故障的时候记录下所有操作或者恢复几分钟甚至几小时之前丢失的数据。
We can process operations out of order and end up with the same result, so we can paper over temporary network and hardware failures, or even replay lost data from minutes or hours ago.
因为能交换操作顺序而不影响最终结果，所以我们才能在网络或者硬件临时故障的时候记录下所有操作或者恢复几分钟甚至几小时之前丢失的数据。
We can process operations out of order and end up with the same result, so we can paper over temporary network and hardware failures, or even replay lost data from minutes or hours ago.
应用推荐