Post reply

How Do I check The "Always On Auto Failover" - In Which scenario ?

  • June 7, 2015 at 12:15 am

    #304722

    Hi

    I Config Ha-Alwayson on 2 test servers .

    In addition, was defined a listener for them.

    I can connect to them from the listener and in directly.

    I did manual Failover and it worked.However all connection to all servers (primary and secondary and listener) was breaked. I expected my connection To

    The listener, be stable.

    But How can I test the Auto failover mechanism?

    -----------------------------------------------------------

    😀

    I run this scenario :

    Scenario 1 :

    1- I filled all free space from the primary server else a bit.

    2- And run on it a Huge Update to fill remain free space.

    3- MeanWhile I Run an insert command into listener IP. (in a while Loop)

    I expected :

    >>> After run update or in middle of it , The primary server face to a problem. (Full Log file). And This was happened.

    >>> After I expected The Failover act and change Primary And Secondary.And My insert commands Continues without Break Or Continue On new server After some Seconds

    But It didn't Happend.

    Both Of 2 Command are stoped !!!!! And auto failover didnt act.

    Scenario 2 :

    I tryed To create a manual fail on primary server . I Tried to Offline the main database in primary server.

    But It didnt allow .

    -----------------------------

    :angry::crazy:

    Then

    1- What is the meaning Of fail that Auto failover act about it ?

    2- In which scenario I can Test It ?

    Please Help me 😛

  • June 7, 2015 at 10:42 pm

    #1803574

    We want move to new servers and need to check this technology.

    I must present befor run this.

    Please say me the way.

  • June 8, 2015 at 11:40 am

    #1803759

    Once you think Always On was configured and you want to test the Automatic Fail over, you can just reboot the primary server and you SQL server should have been failed over.

    Regards,

    [font="Tahoma"]
    --SQLFRNDZ[/url]
    [/font]

  • June 9, 2015 at 12:26 am

    #1803872

    Hi

    I stoped the sql server service in primary.

    But After some seconds, My connection to Listener was Broken. with this message :

    "The connection is broken and recovery is not possible. The client driver attempted to recover the connection one or more times and all attempts failed. Increase the value of ConnectRetryCount to increase the number of recovery attempts."

    And in "Failover Cluster manager" , I see that the "Role" was failed.

    But as soon as I restart that server (The server that is stoped sql service on it) , The "role" go back to running mode and Listener Connection be ok. (even befor that server go up completely)

    What is the reason ? And I expect that with any problem on the primary , I have Listener Connetion. What Can I do ?

  • June 9, 2015 at 5:32 am

    #1803905

    When the alwayson availability group fails over the listener will be interrupted. It is a cluster resource and will be stopped on one node then started on another

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • June 10, 2015 at 12:30 am

    #1804212

    Sorry

    I didnot get it. I must do some thing manualy?

  • June 10, 2015 at 5:35 am

    #1804278

    read my stairway to AlwaysOn starting at this link

    http://www.sqlservercentral.com/articles/FCI/107536/[/url]

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • June 16, 2015 at 2:28 am

    #1805654

    Hi Thank You

    But I Have A detail Problem And I Guess This Problem (Auto Failover Does not Work. But Manualy Works) Related To Storage Config :

    I Run the Cluster validation . And Attach For you 5 Pics .

    Please tell me what is the Problem :

    Pci1 : Storage Validation Result

    ------------------------------------------

    Pic2 : List Disk Validation Result

    -------------------------------------------------

    Pic3 : My Server Configuration : computer Management - Storage

    ------------------------------------------

    Pic4 : My Server Configuration : computer Management - Storage - Try to Online Disk

    --------------------------------------------

    Pic 5 : Some events :

    Please Help me about this.

  • June 16, 2015 at 3:54 am

    #1805674

    please post the results of the following powershell query

    Get-ClusterResource | FL name,state,resourcetype,ownergroup,restartthreshold,restartdelay,restartperiod

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • June 16, 2015 at 5:18 am

    #1805699

    Hi Thank you For your attention .

    Command 1: Get-ClusterResource

    Command 2:Get-ClusterResource | FL name,state,resourcetype,ownergroup,restartthreshold,restartdelay,restartperiod

  • June 17, 2015 at 1:27 am

    #1805948

    Has Cause of The Problem been Recognized ?

  • June 18, 2015 at 4:51 am

    #1806308

    so what have you done about cluster disk 1 and cluster disk 2?

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • June 19, 2015 at 10:19 pm

    #1806859

    I didnt Do special Thing about disks.

    I Only run the steps to create cluster Which in validation Step, I get Disk warning , But I continue to create cluster. Just this.

    But Now I Dont have AutoFailover and the cause of it , is this configure of disks .

    I Dont Know what do i do ?

  • June 21, 2015 at 2:28 am

    #1806894

    Any Thing?

    :crying:

  • June 23, 2015 at 6:28 am

    #1807323

    I with my coworker, addressed this Problem.

    this thing had not any relation with storage.

    We only change a config : in cluster manager - in roles - in failover tab >>

    we change maximum failover in the specified period and period. 50 and 1

    after that :

    we disable NiC on primary server and auto failover changed it immediately !!!

    And then stop a sql server serive , and again It worked true.

    Thank you all :-P:-P

Viewing 15 posts - 1 through 14 (of 14 total)

You must be logged in to reply to this topic. Login to reply