英汉例句

• 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.

  在发生故障时，例如在星期六进行增量备份之后发生了故障，那么只能恢复上个星期日的全备份并应用星期六的增量备份。

• if you touch but a few files or perhaps a handful of directories each day, the additional space required for what is effectively a full backup is paltry.

  如果您每天只修改少量文件和目录，那么生成完整的备份实际上是没有意义的，这样做很浪费空间。

• if transaction logging is used for backups, use this switch only before the full backup schedule (once a week).

  如果事务日志用于备份，只在完全备份计划（每周一次）之前使用此开关。

• note that you can restore either a full backup manually, apply the saturday incremental backup image and roll forward.

  注意，您可以手动恢复完全备份，应用星期六的增量备份映像并进行前滚。

• if the last backup was a full backup image, it and the delta provide the most complete backup.

  如果最后的备份是一个完整的备份映像，那么它和增量备份将提供最完整的备份。

• a full backup of a file system may be restored and subsequent incremental backups layered on top of it.

  可以首先还原文件系统的完全备份，而后续的增量备份可以在已还原的完全备份之上覆盖。

• 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.

  在备份失败的情况下，例如，在执行了增量备份后的星期六，您只可以恢复第一个星期天的完全备份，并应用星期六的增量备份。

• 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.

  如果一个增量备份之前执行了一个或多个其他增量备份，那么您需要在执行增量备份或完整备份映像之后执行的所有增量备份。

• 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).

  注意，在增量备份对特定表空间执行备份之前，必须对该表空间进行一个完整的备份（下面的例子提供详细解析）。

• the second restores to the most recent state, using a combination of full backup plus rolling forward the transaction log, called rollforward recovery.

  另一种机制通过使用全备份，并前滚事务日志，使数据库恢复到最近的状态，这种机制也叫前滚恢复。

• this is the building block of any recovery strategy, without a full backup image, you can't start to restore.

  这是任何恢复策略的构建块，如果没有完整的备份映像，就不能开始恢复过程。

• backup type - only full backup is enabled.

  备份类型 ——只启用全备份。

• hard links are very cheap to create and maintain, so a full backup is simulated using only an incremental scheme.

  硬链接的创建和维护开销很低，所以只使用增量方案就可以模拟完整备份的效果。

• 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.

  例如，您可能希望每天做一次联机增量备份，然后每周在维护期间执行脱机完整备份。

• figure 3 shows how recovery requires a full backup image, the last incremental backup, all delta backups since the last incremental backup, and the logs.

  图3显示了恢复如何使用完整的备份映像、最后的增量备份、上一次增量备份之后的所有增量备份和日志。

• 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.

  如果在增量备份之前执行了增量备份，则需要增量备份、增量备份以及增量备份所依赖的完整备份映像。

• 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.

  初次上传之后——这可能要一会儿，因而在你睡觉前开着让它上传——你将拥有照片库的完整备份。

• availability - with circular logging mode, only offline full backup is possible.

  可用性 ——在使用循环日志模式时，只能进行离线全备份。

• take a full backup before any fundamental change such as a migration, fixpak installation, or a major application change.

  在进行基础性更改之前执行完整备份，比如迁移、安装修复包或大的应用程序修改。

• a full backup image.

  完整的备份映像。