SQL Server 2005 备份失败对事务日志的影响
我有一个 SQL Server 2005 实例，其完整备份 (.BAK) 由于磁盘空间不足而失败。但是，每半小时事务日志备份将继续进行 (.TRN)。假设我有一个较旧的完整备份，这些连续事务日志可以用于恢复数据库吗？
即，事务日志备份是否仅从上次成功的备份运行并忽略任何中间失败的完整备份？
I have an SQL Server 2005 instance whose full backup (.BAK) failed due to low disk space. However half hourly transaction log backups continue (.TRN). Assuming I have an older full backup, could these continuing transaction logs be used to restore the database?
i.e. do the transaction log backups only run from the last successful backup and ingore any intermediate failed full backups?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我本以为失败的备份会被回滚，因此正在进行的事务日志备份加上之前的完整数据库恢复应该足以恢复数据库。
话虽如此，我会尽快解决这个问题，但这不是一个好的位置。
I would have thought the failed backup would be rolled back, so the ongoing transaction log backups plus a full database restore prior to these, should be sufficient to restore a database.
Having said that, I would fix this issue as soon as possible, it's not a good position to be in.
您将需要自上次完整备份以来获取的所有日志。
如果丢失了先前的日志，则无法前滚日志。
查看此处以确定失败备份的 LSN 和状态。
You will need ALL the logs taken since the last full Backup.
You cannot roll forward a log if you have lost a previous log.
Have a look here to determine the LSNs and status of your failed backup.