Post reply

reconfigure the log shipping, after log shipping configured database on primary was corrupted/dropped without disabling the log shipping?

  • April 1, 2010 at 4:45 pm

    #143901

    Hi

    We have configured log shipping for sql server 2005 EE 64 bit with SP3. We faced an issue with a SQL Server where Log shipping is not enabled as below:

    Due to some application update failure, all the databases went offline & we are unable to bring them online and fianlly we restored them fron last backup.

    In case, If same thing occures to the SQL server where log shipping is enabled and if we restore the databases from backup & reconfiure log shipping it will throw wired errors (I tested this on test server) because log shipping configuration documentation says that "we should disabled the log shipping before dropping the database"

    SO what will be best approach to reconfigure the log shipping, if log shipping configured database on primary was corrupted/dropped without disabling the log shipping?

    Thanks

  • April 5, 2010 at 9:55 am

    #1145814

    any ideas on this scenario? I appreciate your inputs

    thanks

  • April 5, 2010 at 10:40 am

    #1145853

    just disable all the logshipping jobs. Do your restore on primary and restore with norecovery on secondary.

    delete all tran log backups on the secondary. Move any log backups on primary which are pre the restore somewhere else (i.e.. keep them until you are sure you won't need them). Reenable logshipping jobs and let it pick up from where it left off.

    ---------------------------------------------------------------------

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

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