Post reply

Log shipping errors - standby vs norecovery

  • August 30, 2005 at 1:53 pm

    #94719

    Okay, I've read everything I can find on log shippinga and have found nothing useful that pertains to my specific error.  Maybe someone out there can help?

    I have a source server (A) - SQL 2000 enterprise, a destination server (B) - SQL 2000 enterprise, and a monitor server (C) - SQL 2000 enterprise.  The database on server B is set as read-only and we are only using it for reporting purposes.

    I walked through the wizard steps and all seemed to go well.

    Now, when I look at the monitor server; first, it says the copy job succeeded and the restore failed.  Please NOTE:  when I look in the share folder where the transaction logs should have copied to, they are not there.  I also tried copying them there manually to see if at least the restore would complete, but no.

    So the error on the monitor service is this:

    [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4306: [Microsoft][ODBC SQL Server Driver][SQL Server]The preceding restore operation did not specify WITH NORECOVERY or WITH STANDBY. Restart the restore sequence, specifying WITH NORECOVERY or WITH STANDBY for all but the final step.

    [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally.

    The problem is that I DO Have the server marked as STANDBY.  When I look up this error in Microsoft, the bugs are related to SQL 7.0, but I am using SQL 2000 enterprise on the source and destination server.  Not to mention, all they give for a workaround for the SQL 7.0 problem is this "Provide a valid filename and path for the STANDBY file. "  I don't see anywhere to do this and the properties of the log shipping job show that I have it set to "STANDBY".

    This is my first time, so I would appreciate any help if anyone has suffered this issue?

  • August 31, 2005 at 9:36 am

    #586529

    It seeems that when you restored the secondary database, you did not restore it with no recovery or standby.

    1. Did Server B had the database initially as read-only OR you created the database when you configured log shipping ????

    2. Try configuring it again and let the log shipping wizard take the backup of your server A and restore it on Server B as norecovery or standby (your choice).

    Let me know your progress.

    --Kishore

     

     

     

     

  • August 31, 2005 at 11:14 am

    #586578

    That seems to have taken care of that error.  It created the database, but the restore still failed with this error...

    [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4326: [Microsoft][ODBC SQL Server Driver][SQL Server]The log in this backup set terminates at LSN 26932000000541900001, which is too early to apply to the database. A more recent log backup that includes LSN 27052000002026000001 can be restored.

    [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally.

    I am looking into, but any ideas are appreciated

    Thanks for you help!

  • September 1, 2005 at 1:50 am

    #586738

    This error is indication that it is not following the Log backup chain. I mean, when we first restore a full backup, all other T-log backups should be restored in sequence. You get a LSN No error when the log backups are not in sequence when they are restored.

    However, I would recommend to recreate the Log shipping using the wizard and also see that the Log backups that are being created and copied to Secondary Server are on the shared drives that have domain access rights on both the servers.

    In what state is your Secondary database now ?

    --Kishore !!

     

  • December 22, 2006 at 4:34 am

    #679679

    Hello Folks,

     

    I'm having the same kind of issue, here(MS-SQL2K SP4)... As a DRP exercise, I restored a backup of my SAP database and tried to reapply the logs from the backup but I'm stuck with the same "The log in this backup set terminates..." error. The database is now showing a "Loading" status in the Ent. Mgr. Is there a way to bring it back online into its current state, without bothering about the TL at this time ?

    Further, I will of course have to investigate the TL issue (probably a timing issue in my DB/TL backup sequencing), but first, I would like to make sure I can bring my SAP server back online.  

    Any help highly appreciated,

    Christian

  • December 22, 2006 at 8:32 am

    #679739

    The error means that the log you are trying to restore was created earlier than the last file that was restored.

    Whenever your database says Loading, that normally means that the last restore was done using WITH NORECOVERY and it's waiting for additional restores. To return it to normal mode, without additional restores, just run this:

    RESTORE DATABASE dbname

    WITH RECOVERY

    -SQLBill

Viewing 6 posts - 1 through 5 (of 5 total)

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