The steps below show you how to do an incremental backup and restore.
下面的步骤向您展示了如何执行增量备份和恢复。
This is how incremental backup works.
这就是增量备份的工作原理。
增量备份。
There are two types of incremental backup.
有两种类型的增量备份。
For Monday, do an incremental backup. Issue the command.
在星期一，需要执行增量备份。
For Tuesday to Saturday, repeat the incremental backup process.
从星期二到星期六，可以重复增量备份过程。
If nothing changes on the page, the incremental backup skips it.
如果一个页面未发生任何更改，增量备份就会跳过它。
Figure 65 illustrates the concept of cumulative incremental backup.
图65阐述了累积增量备份的概念。
To recover from the incremental backup, there are only two steps to follow.
要从递增式备份中还原，只需完成以下两步。
The diagram below illustrates the concept of differential incremental backup.
下图阐述了差异增量备份的概念。
An interesting feature of dump is its built-in incremental backup functionality.
dump的一个有趣特性是其内置的增量备份功能。
No problem, all you need to do is grab the version from last night from the incremental backup.
这很容易解决，您只需要从增量备份中提取昨晚的版本即可。
An incremental backup is a backup of all changes since the most recent successful, full backup.
增量备份是最近一次成功的全备份以来的所有修改的备份。
From this figure you can see that an incremental backup is really based on the last full backup.
从这个图中可以看到，增量备份实际上是以上一次的完全备份为基础。
An incremental backup is a backup of all changes since the most recent, successful, full backup.
增量备份是自最近成功的完全备份以来所有更改的备份。
To use incremental backup or automate the online backup, Oracle recommends Recovery Manager to be used.
要使用增量备份或自动化联机备份，Oracle建议使用RecoveryManager。
This article discusses one of the most powerful backup improvements for data warehouses - incremental backup.
本文讨论对数据仓库的最大备份改进之一——增量备份。
An incremental backup grabs all changes since the last full backup image (sometimes called a level 1 backup).
增量备份捕捉自上一次完全备份以来的所有变化(有时候也称1级备份)。
To specify whether incremental backup is enabled for a database, you use the TRACKMOD configuration parameter.
要指定是否对数据库启用增量备份，需要使用TRACKMOD配置参数。
The tracking feature used to support incremental backup is entirely internal and doesn't require any storage considerations.
用于支持增量备份的跟踪特性完全是内部的，不需要考虑任何存储方面的因素。
During an incremental backup, IDS has to read every used page in order to decide if this page is a candidate for backup or not.
在增量备份过程中，IDS需要读取每个被使用过的页面，以便决定该页面是否适合做备份。
Cumulative incremental backup on the other hand, backs up all the blocks used since the most recent backup at level n-1 or lower.
另一方面，累积增量备份将备份自最近在级别n - 1或更低级别上进行备份以后使用的所有数据块。
Keep in mind however that when you use nightly deltas, you require all deltas since the last full or incremental backup for recovery.
记住，如果使用夜间增量备份，那么执行恢复时需要使用在最后一次完整或增量备份之后的所有增量备份。
To recover from the incremental backup, there are only two steps to follow, Restore the incremental database and roll forward to completion.
要恢复增量备份，只需要两步，恢复增量数据库并前滚。
This is not intended for enterprise use-an incremental backup with history would make more sense there. The concept remains the same, though.
这个脚本并不适合企业环境；在企业环境中，带历史记录的增量备份更合适，但概念是相同的。
Full incremental backup. An image of all pages changed since the last complete backup (whether the backup is a full or table space backup image).
完整增量备份：最后一次完整备份(不管该备份是完整的还是表空间备份映像)之后更改的所有页的映像。
DAOS enables a large reduction in incremental backup costs because the DAOS repository isolates large blocks of data into separate, unchanging files.
DAOS可显著降低增量备份成本，因为DAOS储存库将较大的数据块放在单独的、稳定的文件中。
For example, you might want to do an online incremental backup once per day, and then do an offline full backup once per week during a maintenance window.
例如，您可能希望每天做一次联机增量备份，然后每周在维护期间执行脱机完整备份。
For both types of backups (whole system and parallel) you will be able to specify the backup level, for instance, if this should be a full or an incremental backup.
对于这两种类型的备份(全系统备份和并行备份)，都可以指定备份级别，例如，如果此备份应该是一个完全备份或增量备份。
For both types of backups (whole system and parallel) you will be able to specify the backup level, for instance, if this should be a full or an incremental backup.
对于这两种类型的备份(全系统备份和并行备份)，都可以指定备份级别，例如，如果此备份应该是一个完全备份或增量备份。
应用推荐