SQL Server Performance Forum – Threads Archive
Log Ship – attempting to load same log over againHello, I thought log shipping was supposed to be so strait forward and easy! It does not appear to be a reliable fail-over or "warm standby" solution. Anyway….After setting up log shipping I have four plans that continue to try to load the first_file_000000000000.trn log, created when the plan is first initialized, over and over again. It happens even though the backup/copy/loads are functioning successfully and according to the plan schedule, and this initial file doesn’t even exist in the designated share because it’s been deleted according to the log retention schedule. What else should I have expected from Bill and the bunch…..Anyway, here is the error: I’m thinking…tell me something I don’t know, like why is this happening! [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4305: [Microsoft][ODBC SQL Server Driver][SQL Server]The log in this backup set begins at LSN 33000000022600001, which is too late to apply to the database. An earlier log backup that includes LSN 33000000011800001 can be restored.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally.
Any help anyone can give would be greatly appreciated. Thank you much! Fonkberry [8D]
When the full database backup was restored, one that was too old was restored. The transaction logs must be applied sequentially, so if the full backup is out of date, log shipping will fail. Ensure those 4 plans are referring to the same database and if so delete 3 of them.
For a while, stop the LS process and restore full database from primary to the secondary server and then re-enable the Log shipping which should take care of the load on standby server. Ensure there are no network bottlenecks between the servers. For information on error 4305 refer to this KBAhttp://support.microsoft.com/default.aspx?scid=kb;EN-US;295371 to resolve.
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.