We've been trying to get the log shipping of one DB to work for a while now, but it seems like it always crashes between 2am and 2:30am...
It's a log shipping setup is straight forward.
Transaction logs backup happen every 15 minutes (we tried to a local drive and to a network drive - with same results)
on the secondary server the LS copy runs every 15 minutes but with a + 5 minute offset.
and the LS restore runs every 15 with another 5 minute offset.
Everything runs fine until aroud 2am when the message we receive is: Restore failed for Server 'XXX'. System.Data.SqlClient.SqlError: The log in this backup set begins at LSN 42118000000017100001, which is too recent to apply to the database. An earlier log backup that includes LSN 42118000000016900001 can be restored. (Microsoft.SqlServer.Smo)
When we manually restore the transaction log before the one that is in error, it restores without any problem.
we follow with the transaction log file that gave us the error... and still gives us the same error...
Logically, I see 2 possible issues:
1- the pointer on the db changes?
2- The file gets corrupted?
- We delete copied files over 2 hours.
- we're in standby mode
- we disconnect users when restoring.
If you need more info, feel free to ask.
I'm not sure what else to look at...
any help would be greatly appreciated.