Logshipping - how to recover after failure

  • I have setup logshipping in sql 2005. i have a primary and secondary server only.

    Suppose for maintenace i bring primary down. . i have to manually bring the secondary server online. usnig restore databse with restore.

    1) so far so good. But what now. How can i re-sync the old primary with the new primary?

    2) can i return the original secondary back to standby mode so that the primary can resume its role and the log shipping process proceeds.

  • sorry, once you have recovered the secondary no more tran logs can be applied to it and it is out of synch. You have no choice but to a do another restore with norecovery or standby and restart log shipping jobs. clear out tran logs previous to the new backup from the logshipping shared before restarting.

  • i had a look at this.

    http://msdn2.microsoft.com/en-us/library/ms178117.aspx

    but when ever i try to do step 3. it fails.

    this is what i do .. enable log shipping on server A as primary and Server B as standby.

    log shipping works and i can see the changes going through.

    then i stop the jobs.

    i bring server B online.

    back to server A and i use the backup log option leaving the database in restoring state. norecovery.

    i configure Server B as primary andd server A as secondary. The jobs fails and no chagnes are going through.

    This document stays that its easy to switch roles.. but i am finding it almost impossible.Please if u have setup log sipping and have swapeed roles then let me konw..

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

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