incremental backup
增量备份
2025-10-08 23:51 浏览次数 7
增量备份
incremental backup is a backup of all of the data that has changed since the last full database backup.
增量备份就是对最近一次数据库全备份以来所有修改了的数据进行备份。
keep in mind however that when you use nightly deltas, you require all deltas since the last full or incremental backup for recovery.
记住,如果使用夜间增量备份,那么执行恢复时需要使用在最后一次完整或增量备份之后的所有增量备份。
to restore without losing data, you will restore from the first sunday backup, followed by incremental backup taken on saturday and roll forward.
要进行恢复,而又不丢失数据,那么您需要从第一个星期天备份恢复,然后恢复星期六取得的增量备份并进行前滚。
this is not intended for enterprise use—an incremental backup with history would make more sense there. the concept remains the same, though.
这个脚本并不适合企业环境;在企业环境中,带历史记录的增量备份更合适,但概念是相同的。
from this figure you can see that an incremental backup is really based on the last full backup.
从这个图中可以看到,增量备份实际上是以上一次的完全备份为基础。
in the case of a failure, for example on saturday after the incremental backup is taken, you can just restore the first sunday full backup and apply the incremental on saturday.
在发生故障时,例如在星期六进行增量备份之后发生了故障,那么只能恢复上个星期日的全备份并应用星期六的增量备份。
this is because as the days progress the incremental backup contains more changed pages.
这是因为随着时间的推移,增量备份包含越来越多的更改页。
in the case of a failure for example on saturday after the incremental backup is taken, you can just restore the first sunday full backup and apply the incremental on saturday.
在备份失败的情况下,例如,在执行了增量备份后的星期六,您只可以恢复第一个星期天的完全备份,并应用星期六的增量备份。
note that in this scenario each incremental backup gets bigger until the next full backup.
注意,在这些场景中,每个增量备份都会不断增长,直到构成一个完整的备份。
this is how incremental backup works.
这就是增量备份的工作原理。
incremental backup is a good way to protect a database that is largely read-only but has some occasional insert, update, or delete activity performed against it.
增量备份能够为以只读为主、偶尔执行insert、update或delete活动的数据库提供很好的保护。
note that you can restore either a full backup manually, apply the saturday incremental backup image and roll forward.
注意,您可以手动恢复完全备份,应用星期六的增量备份映像并进行前滚。
daos enables a large reduction in incremental backup costs because the daos repository isolates large blocks of data into separate, unchanging files.
daos可显着降低增量备份成本,因为daos储存库将较大的数据块放在单独的、稳定的文件中。
if nothing changes on the page, the incremental backup skips it.
如果一个页面未发生任何更改,增量备份就会跳过它。
be aware that before an incremental backup can be taken on a particular table space, a full backup of that table space is necessary (more details on this follow the example below).
注意,在增量备份对特定表空间执行备份之前,必须对该表空间进行一个完整的备份(下面的例子提供详细解析)。
incremental backup allows you to back up only index and data pages that have changed since a previous backup.
增量备份允许只备份自上一次备份以来发生变化的索引和数据页。
for tuesday to saturday, repeat the incremental backup process.
从星期二到星期六,可以重复增量备份过程。
if a delta is preceded by one or more deltas, you need all deltas until you reach an incremental backup or a full backup image.
如果一个增量备份之前执行了一个或多个其他增量备份,那么您需要在执行增量备份或完整备份映像之后执行的所有增量备份。
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.
例如,您可能希望每天做一次联机增量备份,然后每周在维护期间执行脱机完整备份。
to specify whether incremental backup is enabled for a database, you use the trackmod configuration parameter.
要指定是否对数据库启用增量备份,需要使用trackmod配置参数。
if a delta is preceded by an incremental backup image, you need the delta, the incremental backup, and the full backup image on which the incremental is based.
如果在增量备份之前执行了增量备份,则需要增量备份、增量备份以及增量备份所依赖的完整备份映像。