这里假设存在一个日志备份计划。
所有后续日志备份包含的信息都相同。
不过，有时事务日志备份要比完全备份还大。
However, sometimes a transaction log backup is larger than a full backup.
事务日志备份所使用的资源通常比完全备份少。
Transaction log backups generally use fewer resources than full backups.
在这种情况下，应更加频繁地创建事务日志备份。
In this situation, you should create transaction log backups more frequently.
ontape实用程序自动生成文件名，并执行物理和日志备份。
The ontape utility generates filenames automatically and performs physical and log backups.
如果你在上一步做了日志备份,那么你很可能会没有数据损失.
If you managed to backup log in above step, then you will most probably have zero dataloss.
事务日志备份——备份所有执行的事务日志(在上次完全备份之后执行的)。
Transaction log backup — Backs up all of the transactions performed against the database after the last successful full backup or transaction log backup is completed.
纯日志备份只包含某个时间段的事务日志记录，不包括任何批量更改。
A pure log backup contains only transaction log records for an interval, without any bulk changes.
然后还原最近的干净的数据库备份和随后的日志备份,包含上一步做的日志备份.
Then restore the latest clean database backup and the subsequent log backups, including the one taken in above step.
该特性允许使用ontape和on - Bar实用程序执行逻辑日志备份的连续恢复。
This feature allows performing continuous restore of logical log backups using the ontape and ON-Bar utilities.
该事务的起点记录在第一个事务日志备份中，终点记录在第二个事务日志备份中。
The start of the transaction is recorded in the first transaction log backup, but the end of the transaction is recorded in the second transaction log backup.
因此，创建事务日志备份可以比创建完全备份更加频繁，从而降低丢失数据的风险。
Therefore, you can create transaction log backups more frequently than full backups, which reduces your risk of losing data.
完全备份和增量备份只能空闲期间(offshift)运行，带有一天内的存档日志备份。
Full backups and incremental backups were only run "off shift," with archive logs backed up during the day.
在日志备份完成之后，日志头部才能移动。在这种情况下，释放空间可能需要再进行一次日志备份。
The log backup does not prevent truncation, but the head of the log cannot move until the log backup completes.
如果是SQLServer 2005，我们拥有页级别的还原，意味着我们能够只还原损坏的页面(代替完整的备份)然后是随后的日志备份。
As of SQL Server 2005, we have page level restore, meaning that we can restore only the damaged pages (instead of a full backup) and then the subsequent log backups.
在这个卷组上定义了DB 2数据库的所有存储组件，包括表空间、日志和备份。
All storage components of the DB2 database were defined on this volume group, including tablespaces, log, and backups.
如果事务日志用于备份，只在完全备份计划(每周一次)之前使用此开关。
If transaction logging is used for backups, use this switch only before the full backup schedule (once a week).
应该将日志包括在备份中。
安全和审计日志、备份、启动盘、档案副本、调试信息，以及很少访问的大对象。
Security and audit logs, backups, boot disks, archival copies, debugging information, rarely accessed large objects.
定期启用事务日志归档模式进行的在线备份，事务日志存储在一个容错磁盘上。
Online backups with transaction log archive mode enabled at regular intervals and the transaction logs are stored on a fault-tolerant disk.
前滚到日志的结束，然后完成备份。
日志是高度可配置的，为了安全和备份，日志甚至可以存储到单独的系统中。
Logging is highly configurable, and logs can even be stored on a separate system for security or backup purposes.
备份逻辑日志一直是一个好主意，如果计划执行并行备份或想要执行指定到某一点的还原请参阅备份的类型，那么备份日志非常重要。
Backing up your logical logs is always a good idea and it is essential if you plan to do parallel backups or want to be able to perform point-in-time restores (see Type of backups).
如果您正在使用循环日志记录，脱机备份是惟一受支持的备份类型。
If you are using circular logging, offline backup is the only type of backup supported.
结合事务日志的备份和归档优势，事务日志可以让服务器的运行达到前所未有的顺畅。
Coupling this with the backup and archiving benefits of transaction logging, transaction logging makes your server run like it never ran before.
如果使用在线备份，要知道除非具有在DB 2备份数据库时发生的所有事务的日志，否则备份映像没有任何作用。
If using online backup, recognize that the backup image will be useless without the logs of all transactions that occurred while DB2 was backing up the database.
对于这些情况，即使使用备份-日志策略也不够理想。
So in these cases, even using the backup-plus-log strategy is flawed.
如果达到某个阈值，考虑备份日志文件。
If a certain threshold is reached, consider backing up the logging files.
如果达到某个阈值，考虑备份日志文件。
If a certain threshold is reached, consider backing up the logging files.
应用推荐