Perform logical database backups as they extract data and logical definitions from the database to a file.
执行逻辑数据库备份，将数据和逻辑定义从数据库提取到一个文件。
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).
备份逻辑日志一直是一个好主意，如果计划执行并行备份或想要执行指定到某一点的还原请参阅备份的类型，那么备份日志非常重要。
However, in the case of a restore, you won't be able to get your data back because the logical logs are needed to reach a point of consistency for backups performed in parallel mode.
不过，在进行这种情况的还原时，无法使数据还原，因为需要逻辑日志来达到并行模式下执行的备份的某个一致点。
It is essential that you ensure your logical logs will be backed up regularly if you plan to do parallel backups or want be able to perform point-in-time restores.
如果计划执行并行备份或者希望能够执行指定到某一时间点的还原，则确保定期备份逻辑日志就非常重要。
This feature allows performing continuous restore of logical log backups using the ontape and ON-Bar utilities.
该特性允许使用ontape和on - Bar实用程序执行逻辑日志备份的连续恢复。
Informix versions before IDS V10 did not prevent you from doing parallel backups without saving your logical logs.
Informix的IDSV10之前的版本不允许在没有保存逻辑日志的情况下进行并行备份。
The exclude-entry ensures that logical logs are not backed up under the dedicated nodename, as this would cause trouble during a restore operation of your daily backups.
exclude 条目确保逻辑日志不会备份在专用节点名之下，否则在恢复每日的备份时将出现麻烦。
For logical log backups, it is the logical log ID.
对于logicallog备份，使用的则是逻辑日志id。
Whole-system backups are performed sequentially (dbspace after dbspace) and they can be restored without applying any logical logs.
全系统备份是连续执行的(一个dbspace备份完成后接着另一个dbspace备份)，并且可以不使用任何逻辑日志来还原它们。
Having a logical, specific naming convention for your backups is also important.
为备份建立富有逻辑性的特定命名约定也非常重要。
Having a logical, specific naming convention for your backups is also important.
为备份建立富有逻辑性的特定命名约定也非常重要。
应用推荐