I recently ran across an issue trying to restore a db and log files. DB restored without issues. About 10 log files in, I received a message stating the LSN was out of sync and could not finish. I used a tool that puts them in order, so that's not my issue. I have my log backups set to run in 15 minute intervals. This large database takes a couple of hours to perform a full backup. Could the log backups happening simultaneously during the full backup cause this situation?
The end result was not bad this time, but this is alarming. I am trying to maintain a RPO of 15 minutes.
This little test resulted in an 8 hr RPO…. unacceptable.
Regards,
Tim
Best Answer
No, simultaneous full and log backups have been possible since
SQL Server 2005
, as Paul Randal states here in a post on concurrent log / full backups.Also stated here regarding the many myths regardings backups.
If it is not the tool's wrong doing as you mention then I would try to look if there are any other log backups being taken in your backup history dmv's in the
MSDB
database.Double check the restore procedure as well so that you are certain that you have all the log files (for example different paths after failing over the Always On Availability Group if the database is participating in an Availability Group, however Ola's procedure should take care of that).