Post reply

Restore job is Failing in the secondary server after fail over and fail back

  • May 13, 2016 at 6:09 am

    #314026

    Hi, Can anybody why i'am getting the following error message.

    Everything was working fine when log shipping was setup. I started geettng this error only after doing fail over and then fail back.

    Message:

    The job failed. The Job was invoked by User ABC\def. The last step to run was step 1 (Log shipping restore log job step.).

    Message

    Executed as user: NT Service\SQLAgent$SERVER2_2014. The step failed.

    Message

    2016-05-13 16:12:04.51*** Error: The restore operation cannot proceed because the secondary database 'DB_logshipping' is not in NORECOVERY/STANDBY mode.(Microsoft.SqlServer.Management.LogShipping) ***

    2016-05-13 16:12:04.53Deleting old log backup files. Primary Database: 'DB_logshipping'

    2016-05-13 16:12:04.53The restore operation completed with errors. Secondary ID: '6e36239b-55b6-4157-bf50-13e41d299f61'

    2016-05-13 16:12:04.55----- END OF TRANSACTION LOG RESTORE -----

    Thanks in advance

  • May 13, 2016 at 6:20 am

    #1878875

    How did you fail back?

    What state is the secondary database in?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • May 19, 2016 at 1:41 am

    #1880106

    I did Fail back after the fail over. Let me expand it - Setup logshipping from A(Primary Server) to B(Secondary Server).

    Did Fail over and now my B is PS and A is SS. (Everything works fine). I tried doing fail back, A as PS and B as SS.( Enabled Back up job on A. Copy and restore job on B - All other jobs are Disabled). My restore job fails here.

    Seconday DB is on Standby read only mode.

    Thanks, in advance.

  • May 19, 2016 at 2:46 am

    #1880114

    sanjaydut26 (5/19/2016)

    Seconday DB is on Standby read only mode.

    Can you double-check that, because the restore error states otherwise.

    The restore operation cannot proceed because the secondary database 'DB_logshipping' is not in NORECOVERY/STANDBY mode.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • May 19, 2016 at 4:13 am

    #1880126

    I checked it, it's in standby mode - https://drive.google.com/open?id=0BwQesWwtB8meRXRNdkNXR3ZsRVU

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

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