Post reply

Log Shipping - The saga continues!

  • March 5, 2004 at 8:44 am

    #84711

    Hello,

    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" solotion.

    After setting up log shipping I have four databases that continue to try an load the first_file_000000000000.trn log, that is created when the plan is first initialized. 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: It's like...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!

    Ren Flot

  • March 8, 2004 at 8:00 am

    This was removed by the editor as SPAM

  • March 8, 2004 at 10:04 am

    #497833

    You're logs have gotten out of synch. Personally I implement my own log shipping (I'm cheap ), but I'd reset the log shipping. Someone else, hopefully, will help here or dig through Technet.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply