Database mirroring is suspended after restarting the server used as mirror - by Javier Villegas

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 554618 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 4/27/2010 1:26:08 PM
Access Restriction Public


We have 6 databases in database mirroring mode (high performance - no witness) one database is ~260GB and the other ones are less than 5GB each. when we reboot the server used as mirror (due to windows patches, etc)  the biggest database stays suspended until we resume mirroring manually. the other ones get back in sync automatically when the mirror server comes online.  
Sign in to post a comment.
Posted by Microsoft on 5/25/2010 at 2:50 PM
I have closed this item based on the previous response. Please review the comments in the last response and reply to this item if you do not feel that explains what occured on your system so we can investigate further.
Posted by Microsoft on 4/29/2010 at 1:19 PM
Please check the ERRORLOG on the mirror too. A redo error on the mirror will cause the mirroring partnership to get suspended.

The only three actions that will transition a database mirroring database to the suspended state are FORCE_FAILOVER_ALLOW_DATA_LOSS, SUSPEND, and a redo error. When the server restarts it remains in previous RESUMED or SUSPENDED state. So a server restart will not transition through SUSPENDED(unless there is a redo error).

Once the partnership enters the suspended state, the system will not automatically resume as it waits for:
* Admin to confirm desired rollback of data if the admin issued a FORCE_FAILOVER_ALLOW_DATA_LOSS
* Admin to resume if the admin explicitly issues a SUSPEND action
* Admin to fix the redo error and resume if there was a redo error
Posted by Javier Villegas on 4/29/2010 at 10:41 AM
The only thing we do is just reboot the mirror server for maintenance, no SUSPEND neither FORCE_FAILOVER_ALLOW_DATA_LOSS command. when it comes back online I see the biggest database in SSMS as (PRINCIPAL, SUSPENDED) and the other ones as (PRINCIPAL, Synchronized)

On the Principal side, SQL Error log is just reporting below entries (one per database)
The mirroring connection to "TCP://" has timed out for database "MyDatabase" after 10 seconds without a response. Check the service and network connections.
Error: 1479, Severity: 16, State: 1.

So database mirroring this database is not resuming automatically ( I have to do it manually)

Posted by Microsoft on 4/28/2010 at 2:38 PM
There are only three ways that a DB enters suspended state:
1. Somebody issues SUSPEND command on either principal or mirror DB
2. After a FORCE_FAILOVER_ALLOW_DATA_LOSS command is issued
3. A redo error during recovery on either the principal or mirror DB

If nobody ran either SUSPEND or FORCE_FAILOVER_ALLOW_DATA_LOSS, it means there was a redo error on either the principal or mirror DB. Please check or upload the ERRORLOGs on both the principal and mirror instances to see if either have a redo error.