DB goes into not sync / suspect after a manual failover

  • Syed_SQLDBA

    SSCertifiable

    Points: 6513

    After the patching, one of the database goes into Not synchronizing / suspect state. I resumed a data movement manually. It goes into recovery pending to suspect. This is from the log file 'DB has been suspended for the following reason: "system" (Source ID 2; Source string: 'SUSPEND_FROM_REDO'). To resume data movement on the database, you will need to resume the database manually."

    Any help is highly appreciated.

    "He who learns for the sake of haughtiness, dies ignorant. He who learns only to talk, rather than to act, dies a hyprocite. He who learns for the mere sake of debating, dies irreligious. He who learns only to accumulate wealth, dies an atheist. And he who learns for the sake of action, dies a mystic."[/i]

  • muthukkumaran Kaliyamoorthy

    SSCoach

    Points: 19003

    Check the error log , could be where you have apply a log backup in the sequence.

    Muthukkumaran Kaliyamoorthy
    https://www.sqlserverblogforum.com/

  • Syed_SQLDBA

    SSCertifiable

    Points: 6513

    I am restoring a DB with no recovery. I will then just join the DB.

    "He who learns for the sake of haughtiness, dies ignorant. He who learns only to talk, rather than to act, dies a hyprocite. He who learns for the mere sake of debating, dies irreligious. He who learns only to accumulate wealth, dies an atheist. And he who learns for the sake of action, dies a mystic."[/i]

  • Syed_SQLDBA

    SSCertifiable

    Points: 6513

    Its back online and in sync. Took the backup, paused the data movement, restore the DB, join the DB and that's it.

    "He who learns for the sake of haughtiness, dies ignorant. He who learns only to talk, rather than to act, dies a hyprocite. He who learns for the mere sake of debating, dies irreligious. He who learns only to accumulate wealth, dies an atheist. And he who learns for the sake of action, dies a mystic."[/i]

  • muthukkumaran Kaliyamoorthy

    SSCoach

    Points: 19003

    Syed_SQLDBA wrote:

    I am restoring a DB with no recovery. I will then just join the DB.

    If the DB is small, yes you can configure again.

    How to fix the LSN issue: https://www.sqlserverblogforum.com/alwayson/how-to-solve-the-lsn-mismatch-in-sql-server/

    Muthukkumaran Kaliyamoorthy
    https://www.sqlserverblogforum.com/

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

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