Elapsed time since the last full backup.
上次全备份以来经过的时间。
Backup Type - Only full backup is enabled.
备份类型——只启用全备份。
完整的备份映像。
This includes all changes since the last full backup.
这包含最后完整备份之后的所有更改。
Select Full backup - back up all data for backup type (Figure 10).
选择Full backup—backupalldata作为backuptype(图10)。
Availability - With circular logging mode, only offline full backup is possible.
可用性——在使用循环日志模式时，只能进行离线全备份。
Full backup — Backs up the full database, including all file groups and transaction logs.
完全备份——备份整个数据库，包括所有的文件组合事务日志。
A full backup gives you a complete backup (sometimes it is referred to a level 0 backup).
完全备份使您得到完整的备份(有时候也称0级备份)。
Note that in this scenario each incremental backup gets bigger until the next full backup.
注意，在这些场景中，每个增量备份都会不断增长，直到构成一个完整的备份。
If the last backup was a full backup image, it and the delta provide the most complete 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.
增量备份是自最近成功的完全备份以来所有更改的备份。
Filesystems level backup for DB2 Content Manager system is similar to that of offline full backup.
DB 2ContentManager系统的文件系统级备份与脱机完整备份类似。
A full backup of a file system may be restored and subsequent incremental backups layered on top of it.
可以首先还原文件系统的完全备份，而后续的增量备份可以在已还原的完全备份之上覆盖。
Assuming we back up as depicted above - Sunday full backup, Monday to Saturday we do incremental backups.
假定我们像上面描述的那样执行了备份——星期天执行完全备份，星期一至星期六执行增量备份。
Restore a full backup, replay the logs of all transactions since the backup, and your recovery is complete.
要恢复完整的备份，重播备份之后的所有事务的日志，该过程结束之后恢复就完成了。
The following command does a full backup of Linux with all ext2 and ext3 file systems to a SCSI tape device.
下面的命令执行一个完全Linux备份，它把所有ext2和ext3文件系统备份到一个SCSI磁带设备。
This is the building block of any recovery strategy, without a full backup image, you can't start to restore.
这是任何恢复策略的构建块，如果没有完整的备份映像，就不能开始恢复过程。
An incremental backup grabs all changes since the last full backup image (sometimes called a level 1 backup).
增量备份捕捉自上一次完全备份以来的所有变化(有时候也称1级备份)。
If transaction logging is used for backups, use this switch only before the full backup schedule (once a week).
如果事务日志用于备份，只在完全备份计划(每周一次)之前使用此开关。
Hard links are very cheap to create and maintain, so a full backup is simulated using only an incremental scheme.
硬链接的创建和维护开销很低，所以只使用增量方案就可以模拟完整备份的效果。
The current Stack Overflow full backup is about 7 GB compressed, and the other databases are perhaps 2 GB compressed.
（当前的StackOverflow的全备份压缩之后有7GB左右，而另一个数据库压缩后大概有2GB）。
Note that you can restore either a full backup manually, apply the Saturday incremental backup image and roll forward.
注意，您可以手动恢复完全备份，应用星期六的增量备份映像并进行前滚。
Differential backup — Backs up all of the modified pages in a database after the last successful full backup is completed.
差异化备份——只对上次完全备份之后有过更改的页面进行备份。
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.
如果一个增量备份之前执行了一个或多个其他增量备份，那么您需要在执行增量备份或完整备份映像之后执行的所有增量备份。
In six months of using SuperMemo, I had to restore from a full backup three times, each time losing six to eight hours of work.
在六个月的使用期类，我做过三次完整恢复，每一次恢复都让我损失六到八个小时的工作。
This is different than the strategy shown in Figure 1, which requires you to have only one full backup, one incremental, and logs.
这与图1 所示的策略不同，它仅需要一个完整的备份、一个增量备份和日志。
For a delta backup, you need to maintain all the backups taken since the last full backup in order to be able to reconstruct the data.
对于差异备份，需要维护自上次完全备份以来采取的所有备份，以便能够重构数据。
After your initial upload - which may take a while, so set it up before you go to sleep - you will have a full backup of your photo library.
初次上传之后——这可能要一会儿，因而在你睡觉前开着让它上传——你将拥有照片库的完整备份。
应用推荐