| 1. | For more information about tail - log backups , see
有关尾日志备份的详细信息，请参阅 |
| 2. | If a tail - log backup has incomplete metadata , in the
如果尾日志备份包含不完整的元数据， |
| 3. | This occurs again for the 9 : 45 p . m . transaction tail - log backup
对晚上9 : 45的事务尾日志备份再执行一次上述操作。 |
| 4. | If the tail - log backup succeeds , removing mirroring may be your best alternative
如果尾日志备份成功，停止会话可能是最佳选择。 |
| 5. | Create a tail - log backup of the currently active transaction log as of the point of failure
失败时创建当前活动事务日志的尾日志备份。 |
| 6. | Use norecovery whenever you intend to continue with a restore operation on the database
创建尾日志备份时，也可以同时使数据库变为还原状态。 |
| 7. | Typically , before you restore a database , you should try to back up the tail of the log
进行尾日志备份与进行日常的日志备份不同。有关详细信息，请参阅 |
| 8. | If the database is damaged , use either with continue after error or with no truncate . backup log
尾日志备份可使用copy _ only选项独立于定期日志备份进行创建。 |
| 9. | After that , the transaction log can be backed up during any backup , except another log backup
尾日志备份捕获那些尚未备份的日志记录（即活动记录） 。这称为“日志尾部” 。 |
| 10. | Tail log backups capture the tail of the log even if the database is offline , damaged , or missing data files
尾日志备份可捕获日志尾部，即使数据库离线、损坏或缺少数据文件。 |
