Manual Failover of Quorum disk failed to another node

hi all,

i have 2-node cluster(active-passive) environment vm's. when manually failover i.e. go

fcm->application , cluster group-> sql server engine-> right click on it-> choose node-2 failover.

so sql rdm shared disk failover viz. data disk, log file disk backup shared disk. quorum disk q rdm disk not failover node-2 , remains in node-1.

my quorum configuration node , disk majority recommended microsoft.

is in manual failover have forcefully move quorum disk , not move automatically?

or if not true possible reason of quorum disk not moving automatically along other rdm disk?

kindly me on understanding..

some of logs generated , in cluster.log files.

000009dc.00003750::2017/04/13-20:59:45.327 info  [res] physical disk: attempt add admin share q$ to/from netname snimfisbomclus1, returned 0
000009dc.00003750::2017/04/13-20:59:45.405 info  [res] physical disk: path \\?\volume{8e522dcc-3b84-11e5-8825-005056950e3d}\cluster can on disk
00000634.000033e8::2017/04/13-20:59:45.405 info  [qm] setquorum resource gum handler. resource id ac213e9e-354c-4c0c-b1e6-d169d91c2948, path \\?\volume{8e522dcc-3b84-11e5-8825-005056950e3d}\cluster\, flag 1024, arb timeout 20, storage-capable true
00000634.000033e8::2017/04/13-20:59:45.415 info  [quorum] node 1: postarbitrate => 0 ac213e9e-354c-4c0c-b1e6-d169d91c2948
00000634.000033e8::2017/04/13-20:59:45.415 info  [quorum] node 1: quorum arbitrated node 1
00000634.000033e8::2017/04/13-20:59:45.415 info  ignoring evalutequorum request quorum resource being changed.
00000634.000033e8::2017/04/13-20:59:45.415 info  [quorum] node 1: postonline ac213e9e-354c-4c0c-b1e6-d169d91c2948
00000634.000033e8::2017/04/13-20:59:45.415 info  [dm] node 1: attachwitness
00000634.000033e8::2017/04/13-20:59:45.637 info  [dm] key \registry\machine\cluster not appear loaded (status status_object_name_not_found(c0000034))
00000634.000033e8::2017/04/13-20:59:45.637 info  [dm] loading hive, key cluster, filepath c:\windows\cluster\clusdb
00000634.000033e8::2017/04/13-20:59:45.749 info  [dm] paxos tag read hive: 124:124:893802
00000634.000033e8::2017/04/13-20:59:45.840 info  [clfs] initializing clfs logger.
00000634.000033e8::2017/04/13-20:59:45.841 info  [dm] key \registry\machine\0.cluster not appear loaded (status status_object_name_not_found(c0000034))
00000634.000033e8::2017/04/13-20:59:45.842 info  [dm] loading hive, key 0.cluster, filepath \\?\volume{8e522dcc-3b84-11e5-8825-005056950e3d}\cluster\0.hive
00000634.000033e8::2017/04/13-20:59:45.982 info  [dm] paxos tag read hive: 124:124:893802
00000634.00002e64::2017/04/13-20:59:46.055 info  [api] s_apigetquorumresource final status 0.
00000634.00000c68::2017/04/13-23:49:16.512 info  [nm] received request client address snihostname.
00000634.000035b0::2017/04/14-00:16:57.143 info  [nm] received request client address snihostname.
00000634.000035b0::2017/04/14-00:16:57.211 info  [api] s_apigetquorumresource final status 0.
00000634.000031bc::2017/04/14-00:38:21.587 info  [nm] received request client address snihostname.
00000634.00000d58::2017/04/14-00:38:28.424 info  [vss] onidentify - version x-1.4 component name cluster database
00000634.00000d58::2017/04/14-00:38:28.424 info  [vss] onidentify - add files file group target path %windir%\cluster\
00000634.00000d58::2017/04/14-00:38:28.424 info  [vss] onidentify returned true
00000634.000030c4::2017/04/14-00:38:52.687 info  [nm] received request client address snihostname.
00000634.000026d4::2017/04/14-03:49:26.288 info  [nm] received request client address snihostname.
00000634.0000269c::2017/04/14-04:19:57.220 info  [nm] received request client address 169.254.x.x
00000634.00003550::2017/04/14-04:19:57.473 info  [nm] received request client address 169.254.x.x
00000634.00003550::2017/04/14-04:19:57.877 info  [nm] received request client address 169.254.x.x
00000634.00003550::2017/04/14-04:19:58.028 info  [nm] received request client address 10.192.x.x.
00000634.000037b8::2017/04/14-04:19:58.034 info  [nm] received request client address  10.192.x.x.
00000634.00000a50::2017/04/14-04:19:58.057 info  [api] s_apigetquorumresource final status 0.
00000634.00002c40::2017/04/14-04:19:58.059 info  [nm] received request client address  10.192.x.x..
00000634.0000364c::2017/04/14-04:19:58.224 info  [api] s_apigetquorumresource final status 0.
00000634.00003614::2017/04/14-06:12:10.037 info  [api] s_apigetquorumresource final status 0.
00000634.00003184::2017/04/14-07:49:35.581 info  [nm] received request client address snihostname.
00000634.00002038::2017/04/14-10:44:22.416 info  [nm] received request client address 169.254.x.x.
00000634.00002038::2017/04/14-10:44:22.610 info  [nm] received request client address 169.254.x.x.
00000634.00002038::2017/04/14-10:44:22.852 info  [nm] received request client address 169.254.x.x.
00000634.00002038::2017/04/14-10:44:22.893 info  [nm] received request client address 10.192.x.x.
00000634.00003130::2017/04/14-10:44:22.899 info  [nm] received request client address 10.192.x.x.
00000634.00000308::2017/04/14-10:44:22.922 info  [nm] received request client address 10.192.x.x.
00000634.0000379c::2017/04/14-10:44:23.552 info  [api] s_apigetquorumresource final status 0.
00000634.00001480::2017/04/14-10:44:23.560 info  [api] s_apigetquorumresource final status 0.
00000634.00001480::2017/04/14-10:45:58.627 info  [api] s_apigetquorumresource final status 0.
00000634.0000379c::2017/04/14-10:45:58.653 info  [nm] received request client address 10.192.x.x.
00000634.0000324c::2017/04/14-11:42:27.971 info  [nm] received request client address 10.192.x.x.
00000634.00003588::2017/04/14-11:42:28.158 info  [nm] received request client address 10.192.x.x.
00000634.00000ae8::2017/04/14-11:49:46.245 info  [nm] received request client address snihostname. 

to move quorum disk (and other cluster resources associates it, right click on cluster node (under fcm), more actions - move core cluster resources.

this move quorum ip, name , disk other node.

hth

---

this posting provided without warranty of kind

Windows Server  >  High Availability (Clustering)