这种恢复并不会导致系统或应用数据的丢失，也不会丢失设置，甚至连缓存都不会丢失。
This recovery is done without losing system or application data, without losing Settings and even without losing the cache.
IBMCE从以前的备份恢复管理的系统配置文件数据。
IBM CE to restore the managed systems profile data from the previous backup.
复制将在更新后的应用程序到达备用系统时立即开始排队更改后的数据，以备恢复主站点。
Replication will begin queuing changed data for return of the primary site as soon as the updated apps hit the standby system.
一个关键的优点在于系统崩溃后的数据恢复，当使用日志结构方法时，这种恢复更简单。
One key advantage is recovery from system crashes, which is simpler using the log-structured approach.
QCapture程序在源系统上运行，读取已修改的源数据的DB2恢复日志，并将之写入WebSphereMQ队列。
The Q Capture program runs on the source system, reading DB2 recovery logs for changed source data, and writing it to WebSphere MQ queues.
如果您需要恢复您的数据，那么您必须使用讨厌的fsck，在日记记录文件系统出现以后，几乎已经很少使用这个工具了。
If you need to recover your data, you have to use the dreaded FSCK, which has been pretty much banished from memory since journaling file systems.
为了尽可能提高可靠性，我们1希望确保数据库空间处于一致的状态，以便在目标系统上恢复它们。
To maximize reliability, we want to ensure that the database spaces are in a consistent state so their use can be resumed on the target.
大多数情况下，数据库系统本身将提供一种或多种备份与恢复机制，作为产品的组成部分。
In most cases, the database system itself will provide one or more backup and restore mechanisms as part of the product.
当删除实例时，实例将被停止，并且在临时文件系统中的数据也将被删除且不能恢复，因此，需要把重要的数据保存到其他的存储系统上。
When you delete the instance, the instance is halted and the data in the ephemeral file system is deleted and is not recoverable, so you have to keep important data on other storage systems.
系统管理：数据管理、数据仓库安全性、系统和数据库的备份和恢复，等等。
System management: data management, data warehouse security, system and database backup and recovery, and so on.
由于这些原因，理解数据库管理系统中备份和恢复功能的工作原理，并实施经过精心规划的备份策略，就显得至关重要了。
For these reasons, it is critical that you understand how backup and recovery features function for your database management system, and that you have a well-planned backup strategy implemented.
这样就可以保证系统恢复后数据和文件系统的一致性。
In this way, data and file system are guaranteed consistent after a recovery.
为了确保包含系统编目表的分区能够快速恢复，应避免将用户表也放在那个数据库分区上。
To ensure fast recovery of the partition containing system catalog tables, avoid placing user tables on the same database partition.
可以将从非自动存储数据库创建的备份镜像恢复到自动存储数据库系统，但是反之则不行。
You can restore a backup image taken from a non-automatic storage database into an automatic storage database system, but not the opposite.
在这种情况中，重定向操作通常就无用武之地了，因为我们通常都不能在一个操作系统上备份一个数据库，然后将其恢复到另外一个操作系统上。
In this case, a redirected restore operation won't do the trick, because you can't usually back up a database on one operating system, and restore it on another operating system.
当您同时查看或搜索活动数据和归档数据时，它就不太方便了，因为首先要将归档文件恢复到活动数据所在的系统。
When viewing and searching both active and archived data, it is inconvenient to have to first restore the archived files back into the system where the active data resides.
如果系统或媒体发生失败，您可以使用事务日志和第三方备份实用工具恢复数据库。
Then if a system or media failure occurs, you can use the transaction log and a third-party backup utility to recover your database.
NOLOG选项只是用于能轻松复制或恢复的数据，或是是包含不重要数据或是能很容易重新生成的数据的临时文件系统。
The NOLOG option is only intended for data you can easily copy or restore again or for temporary file systems with data that is not important or is easy to reproduce.
对于任何数据库管理系统来说，备份和恢复功能是确保数据可恢复性的关键。
Backup and restore capabilities are key to ensuring data recoverability for any database management system.
初始化为镜像的分割镜像可以用作系统级备份，从而使管理员可以执行快速的文件系统级数据库恢复。
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.
这将确保文件系统的正确性和恢复数据库备份中任何新的配置更改。
This will ensure the file system is correct and any new configuration changes are reverted in the database backup.
如果这样做将会破坏文件系统，导致数据无法恢复。
Doing so can damage the file system, rendering your data irretrievable.
一旦系统发生崩溃，日志文件就会起到一个检查点的作用，用于恢复未保存的信息，防止损坏文件系统元数据。
If a crash occurs, the journal can be used as a checkpoint to recover unsaved information and avoid corrupting file system metadata.
当您需要在不重新构建数据的测试或灾难恢复系统上刷新数据时，这种方法很方便。
This can be handy when you want to refresh data on a test or disaster recovery system that doesn't need to be built from scratch.
任何数据库管理系统都必须拥有确保数据一致性和可恢复性的机制。
Any database management system must have mechanisms for securing data consistency and recoverability.
多亏了日志，数百G的文件系统元数据几乎能在瞬间恢复到一致性的状态。
Thanks to the journal, hundreds of Gigabytes of filesystem meta-data can be brought to a consistent state almost instantaneously.
可以根据数据库位置(本地文件系统或ldap目录)备份和恢复它。
It can be backed up and restored according to the database location (either the local file system or the LDAP directory).
总之，日志文件系统就是一种具有故障恢复能力的文件系统，它利用日志来记录尚未提交到文件系统的修改，以防止元数据破坏(请参见图1)。
To sum up, journaling file systems are fault-resilient file systems that use a journal to log changes before they're committed to the file system to avoid metadata corruption (see Figure 1).
我们只好学会利用手工办法恢复信息块中的数据，从而使分布式通用地面系统不会崩溃。
We learned to manually do [data retrieval] in chunks of information so DCGS would not crash.
也就是说，恢复到快照的磁盘上的数据与操作系统崩溃前磁盘上的数据接近。
In other words, the data on a disk that is restored to a snapshot looks like the data on a disk after an operating system crash.
应用推荐