Mirroring goes to suspended state after a while.. RRS feed

  • Question


    I have 5 databases mirrored. One of them is moderatively active. After I configured mirroring (high performance) , the next day, it goes to suspended state. If I try to resume mirroring, it is in syncronizing state for couple of mins and again goes to suspended state. While this is happenning, the log file on the prindipal databases is continuing to grow, log backups are going on though. Also, the mirror server creates stack dumps everytime I try to "Resume" mirroring from principal.


    Any solution ? The only option I have is to remove mirroring so the log file of the database stops growing.


    Version:9.00.3159.00 (X64) - Both mirror and principal servers.




    Tuesday, October 21, 2008 6:33 PM

All replies

  • It looks like principal server is not able to connect to the mirror server. Can you check endpoint status?

    When you pause mirroring which is synchronous mode, log file in the principal server database will grow huge dependent on the transactions on the mirrored database since it need to take these transactions to the mirror server to maintain consistency once it resumed.

    If the tlog size if too high,then re-configure mirroring.

    Wednesday, October 22, 2008 6:36 AM