• Locked Locked
  • Replies 3 replies
  • Subscribers 12 subscribers
  • Views 6094 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Automated Restore - what is it?

Alexander
over 6 years ago

Check out this blog post from 

https://www.quest.com/community/b/en/posts/i-have-trust-issues-with-my-sql-server-backups

Parents
  • over 6 years ago
    Why run into a problem with automated restore when we try to test full, differentials and log backups. The problem is that if a differential takes longer to complete than our log backup interval, automated restore isn't smart enough to look forward into the available log backups and instead causes an "LSN too early" error to be thrown. We have discussed this with Litespeed support and their recommendation was to stop log file backups during full/diff backup jobs. We find that to be a less than ideal solution as it introduces a potential data loss gap. What are some suggestions to improve Automated Restore's intelligence in these cases?
Reply
  • over 6 years ago
    Why run into a problem with automated restore when we try to test full, differentials and log backups. The problem is that if a differential takes longer to complete than our log backup interval, automated restore isn't smart enough to look forward into the available log backups and instead causes an "LSN too early" error to be thrown. We have discussed this with Litespeed support and their recommendation was to stop log file backups during full/diff backup jobs. We find that to be a less than ideal solution as it introduces a potential data loss gap. What are some suggestions to improve Automated Restore's intelligence in these cases?
Children
No Data