locked
Principal SQL have fail over to Mirror - where to start searching? RRS feed

  • Question

  • MS SQL 2014 with Mirroring

    It looks like the Principal SQL have failed over to the Mirror

    I´m not an SQL administrator, so I wonder where to start looking of what cause the problem.

    Eventid? when fail over occured? is probably a good start but I dont know what that is.

    -Disk not full

    -No process eating cpu

    The only eventid i did react on in my non experience of SQL server was:

    "The mirrored XXXX is to busy to answer.."

    But same on Mirror - plenty of disk, no process eating memory.

    Really appreciate your answers.

    :0)

    • Moved by Tom Phillips Wednesday, March 28, 2018 12:21 PM database mirroring question
    Wednesday, March 28, 2018 12:01 PM

All replies

  • The SQL Server log file will tell you why it failed over to the mirror.

    If the principal did not fail, this is almost always because of a network issue.  Mirroring uses network "heartbeat" to determine if the server is working or not.

    Wednesday, March 28, 2018 12:23 PM
  • I´ve found this
    Log Name:      System
    Source:        Service Control Manager
    Date:          4/19/2010 10:04:02 PM
    Event ID:      7011

    And I cant open any databases on the Principal SQL only Mirror SQL.

    Wednesday, March 28, 2018 12:32 PM
  • Maybe this is normal and I have to manual fail over to the first server that earlier was Principal, again?

    :0)


    • Edited by Bit-101 Wednesday, March 28, 2018 1:39 PM
    Wednesday, March 28, 2018 12:34 PM