locked
Database mirroring goes into suspended mode RRS feed

  • Question

  • Hi

    I am using sql server 2008 with sp3 and I have configured 5 databases in mirroring. one of database is showing in suspended mode while others are synchronized.

    I am getting following error message -

    'TCP://SQLName.ABCD.nic.in:5023',
    the remote mirroring partner for database 'ABCD', encountered error 824, status 2, severity 24.
    Database mirroring has been suspended. 
    Resolve the error on the remote server and resume mirroring, or remove mirroring and re-establish the mirror server instance.

    I have run DBCC CheckDB but did not get any error and even I am not able to resume mirroring.


    Mark As Answer If My Reply Is Helpful
    Thanks
    Neeraj Bhandari (MCTS - Sql Server 2008)

    Tuesday, September 24, 2013 5:44 AM

Answers

    • Proposed as answer by Candy_Zhou Thursday, September 26, 2013 7:39 AM
    • Marked as answer by Candy_Zhou Friday, October 4, 2013 8:19 AM
    Tuesday, September 24, 2013 1:28 PM
  • Well, he could using a snapshot.

    Anyways, I just realized, that automatic page-repair is also in standard edition:

    "If the page is corrupt in the mirror (which is discovered when the page is read as part of the continual recovery of the log), the mirroring session is suspended. The mirror keeps track of all corrupt pages that need to be repaired with copies from the principal. Once all corrupt pages have been repaired, the mirroring session will be resumed automatically. This means that if a page is corrupt in both the mirror and the principal, manual intervention will be required to resolve the issue."

    You may want to read through this: http://www.sqlskills.com/blogs/paul/sql-server-2008-automatic-page-repair-with-database-mirroring/

    If this doesn't help you, we need detailed information on the steps taken and results..

    good luck


    Andreas Wolter | Microsoft Certified Master SQL Server
    Blog: www.insidesql.org/blogs/andreaswolter
    Web: www.andreas-wolter.com

    • Proposed as answer by Candy_Zhou Thursday, September 26, 2013 7:39 AM
    • Marked as answer by Candy_Zhou Friday, October 4, 2013 8:19 AM
    Tuesday, September 24, 2013 1:59 PM
  • also see-http://support.microsoft.com/kb/2015756

    Also please look out the sqlerrorlog and eventlogs as well.


    Thanks, Rama Udaya.K (http://rama38udaya.wordpress.com) ---------------------------------------- Please remember to mark the replies as answers if they help and UN-mark them if they provide no help,Vote if they gives you information.

    • Proposed as answer by Candy_Zhou Thursday, September 26, 2013 7:40 AM
    • Marked as answer by Candy_Zhou Friday, October 4, 2013 8:19 AM
    Wednesday, September 25, 2013 5:46 AM

All replies

  • On which server did you run CHECKDB?

    It says its the remote / inactive node.

    Also: which SQL Server Edition are you on? I presume standard and not enterprise?


    Andreas Wolter | Microsoft Certified Master SQL Server
    Blog: www.insidesql.org/blogs/andreaswolter
    Web: www.andreas-wolter.com

    Tuesday, September 24, 2013 1:08 PM
  • Andreas

    how can he run check db when the  database which is in no recovery mode


    Ramesh Babu Vavilla MCTS,MSBI

    Tuesday, September 24, 2013 1:26 PM
    • Proposed as answer by Candy_Zhou Thursday, September 26, 2013 7:39 AM
    • Marked as answer by Candy_Zhou Friday, October 4, 2013 8:19 AM
    Tuesday, September 24, 2013 1:28 PM
  • Well, he could using a snapshot.

    Anyways, I just realized, that automatic page-repair is also in standard edition:

    "If the page is corrupt in the mirror (which is discovered when the page is read as part of the continual recovery of the log), the mirroring session is suspended. The mirror keeps track of all corrupt pages that need to be repaired with copies from the principal. Once all corrupt pages have been repaired, the mirroring session will be resumed automatically. This means that if a page is corrupt in both the mirror and the principal, manual intervention will be required to resolve the issue."

    You may want to read through this: http://www.sqlskills.com/blogs/paul/sql-server-2008-automatic-page-repair-with-database-mirroring/

    If this doesn't help you, we need detailed information on the steps taken and results..

    good luck


    Andreas Wolter | Microsoft Certified Master SQL Server
    Blog: www.insidesql.org/blogs/andreaswolter
    Web: www.andreas-wolter.com

    • Proposed as answer by Candy_Zhou Thursday, September 26, 2013 7:39 AM
    • Marked as answer by Candy_Zhou Friday, October 4, 2013 8:19 AM
    Tuesday, September 24, 2013 1:59 PM
  • PS: Please check both instances with this command:

    SELECT * FROM msdb.dbo.suspect_pages


    Andreas Wolter | Microsoft Certified Master SQL Server
    Blog: www.insidesql.org/blogs/andreaswolter
    Web: www.andreas-wolter.com

    Tuesday, September 24, 2013 2:06 PM
  • also see-http://support.microsoft.com/kb/2015756

    Also please look out the sqlerrorlog and eventlogs as well.


    Thanks, Rama Udaya.K (http://rama38udaya.wordpress.com) ---------------------------------------- Please remember to mark the replies as answers if they help and UN-mark them if they provide no help,Vote if they gives you information.

    • Proposed as answer by Candy_Zhou Thursday, September 26, 2013 7:40 AM
    • Marked as answer by Candy_Zhou Friday, October 4, 2013 8:19 AM
    Wednesday, September 25, 2013 5:46 AM