All,
I am running log shipping between two SQL Server 2012 (11.0.6020), X64, and Enterprise instances.
My problem is periodically SQL Server will create a log backup that has two first and second log sequence numbers for the same log backup. When SQL Server attempts to apply said log file it throws the classic error in this case, "The log in this backup set begins at LSN <LSN NUMBER>, which is too recent to apply to the database. An earlier log backup that includes LSN <LSN NUMBER> can be restored." When I look in msdb..backupset and msdb..backupmedialfamily I can verify the other LSN it is referring to belongs to the very same file it has tried to restore. My workaround is to simply take a diff backup and restore to the standby database. Here is a screen shot of the multiple LSNs in a single backup log below. You can see there are even multiple backup_start_dates that are seconds apart.
My questions is has anyone seen this behavior before and if so is there a fix/patch? I have searched high and low and can't seem to find any information regarding this type of behavior.
Thanks in advance,
Coleman
TheColeman