Interrupted synchronization cycle caused the client peer database into Suspect Mode RRS feed

  • Question

  • We've recently met a problem and I'm not sure if anybody else has seen it. The situation is: there are three peers in the sync system and one of the acts as the master with the other two being the slaves. All of the three terminals are installed with SQL Server 2008 R2 Express. While the three was in a sync cycle, we started the system shutdown process on the master. After a while, the master is restarted and reestablished the connection with the slaves and started to sync again. Then one of the salve was brough down for installing some tools. After finished installing the tool, we tried to bring up the slave but the system was failed to log into the database. When using DBCC checkdb command, it's indicating the DB was in Suspect Mode.

    We think most likely the problem was due to the sync cycle was interrupted but no direct proof. How do we prevent this scenarios happen again?


    Thursday, October 4, 2012 8:04 PM