It provides granular recovery beyond traditional database recovery.
提供传统数据库恢复之外的粒度恢复。
Database recovery is a important method to protect database security.
数据库恢复是保障数据库安全性的一个重要机制。
Log-based data capture reads data changes from proprietary database recovery logs.
基于日志的数据变化。通过读取数据库中日志的变化来捕捉变化的数据。
Similarly In the database recovery scenario, a user or application might accidentally delete a table.
同样，在数据库恢复场景中，用户或应用程序可能会意外地删除某个表格。
Torn pages are typically detected by database recovery if it is truly an incomplete write of a page.
如果页面写入确实不完整，则数据库恢复通常会检测到残缺页面。
A checkpoint has two purposes: (1) to establish data consistency, and (2) enable faster database recovery.
一个检查点有两个目的：(1)确保数据一致性，和(2)更快的数据库恢复。
Ability to restart interrupted recovery operations that can save precious time and effort in database recovery situations.
能够重新开始中断的恢复操作，这些操作能够在进行数据库恢复时节省宝贵的时间和工作。
Together, these tools give you a powerful recovery solution that enables smarter, simpler, cheaper, and faster database recovery.
总之，这些工具为您提供了一个支持更智能、更简单、更廉价、更快速的数据库恢复的强大解决方案。
It can also facilitate users to define and manipulate data, maintain the security and integrity of data, and the concurrency control and database recovery under multi-user circumstances.
它使用户能方便地进行定义和操纵数据，维护数据的安全性和完整性，以及多用户下的并发控制和恢复数据库等操作。
You could repeat this with all sorts of data and environments, and include database writing and recovery into that process.
您可以对所有类型的数据和环境重复该脚本，并在该过程中包括数据库写入和恢复。
Notice we are only looking at the recovery log — not database files.
注意我们仅仅着眼于恢复日志而不是数据库文件。
System management: data management, data warehouse security, system and database backup and recovery, and so on.
系统管理：数据管理、数据仓库安全性、系统和数据库的备份和恢复，等等。
My database is in the simple recovery mode.
我的数据库工作在简单的恢复模式。
After the physical restore completes, the database instance waits in fast recovery mode to restore logical logs.
在物理恢复完成之后，数据库实例处于快速恢复模式，等待恢复逻辑日志。
Complete recovery can be done at the database level or data file and tablespace level.
完全恢复可以在数据库级或数据文件和表空间级上完成。
Typically this recovery is achieved when database is running in ARCHIVELOG mode and backup online.
通常该恢复是当数据库运行在ARCHIVELOG模式下和联机备份时取得的。
This release extends support for large database environments and disaster recovery.
这个版本扩展了对大型数据库环境和灾难恢复的支持。
A split mirror initialized as mirror can be used as a system level backup, allowing the administrator to perform a quick file system level recovery of the database.
初始化为镜像的分割镜像可以用作系统级备份，从而使管理员可以执行快速的文件系统级数据库恢复。
Archive logs that are currently stored in the database log path directory are not moved to the new location if the database is configured for roll-forward recovery.
如果将数据库配置成进行前滚恢复，那么就不会将当前存储在数据库日志路径目录中的归档日志移到新的位置。
This is the feature that enables DBAs to sleep soundly as database backup and recovery can be fully automated.
这个特性使DBA可以高枕无忧，因为数据库备份和恢复可以完全自动地进行。
A database backup minimizes data loss and gives you the ability to reconstruct the failed database from the backup copy using the recovery process.
数据库备份可以最小化数据的损失并使您能够使用恢复进程从备份副本中重新构建错误的数据库。
You can use the volume group export and import to refresh a database or to perform a disaster recovery test.
您可以使用卷组导出和导入来更新数据库或执行灾难恢复测试。
Use more than one method to back up your database, and test all backup and recovery scenarios carefully.
使用多种方法备份数据库，并仔细测试所有备份和恢复场景。
For disaster recovery, standard database backup and restore procedures are advised.
对于灾难恢复，建议使用标准的数据库备份和存储过程。
The database configuration parameter LOGRETAIN must be set to RECOVERY prior to splitting the mirror if it is intended to be initialized as standby or mirror database.
如果打算将镜像初始化为备用数据库或镜像数据库，那么在分割镜像之前，必须将数据库配置参数LOGRETAIN设置为RECOVERY。
A split mirror of a DB2 UDB database can also be initialized as a warm standby database, providing a quick disaster recovery option if the primary database becomes unavailable.
DB 2UD b数据库的分割镜像可以被初始化为一个热备用数据库，当主数据库不可用时，可提供一个快速的灾难恢复选项。
If you are enabling an existing database for roll-forward recovery, change the number of primary logs to the sum of the number of primary and secondary logs you are currently using, plus 1.
如果您对现有数据库启用前滚恢复，将主日志的数量更改成当前正在使用的主日志和辅助日志的数量总和，再加1。
Refer to the steps above to do a database level recovery.
请参阅上面的步骤来执行数据库级恢复。
If both of these parameters are de-selected, roll-forward recovery becomes unavailable for the database because logs will no longer be retained.
如果取消选择这两个参数，就不能对数据库进行前滚恢复，因为将不再保留日志。
Enabling it by setting it to "recovery" allows the database manager to use the roll-forward recovery method.
通过将它设置成“RECOVERY”来启用它，从而允许数据库管理器使用前滚恢复方法。
应用推荐