Failed to assign scsi shared storage to windows cluster 2012 standard edition


i new server 2012 and  trying create cluster sql 2008 enterprise on windows server 2012. in order achieve have configured dc , 2 cluster nodes. servers running server 2012 standard edition. windows vms running on kvm hypervisor. have created iscsi virtual disks on dc in order share storage cluster. have created separate virtual disks sqllogs , data etc. had mounted shared storage same drive letters on both cluster nodes. cluster node on m running cluster manager can see , mount shared storage mounted partitions on second node disappear reasons. can see partitions in disk management , tried online disks error appears" specified disk or volume managed microsoft failover clustering component. disk must in cluster maintenance mode , cluster resource status must b e online perform operation". there 3 consecutive event id's saw in events (10, 70, 1) source : iscisprt : login request failed. "the login response packet given in dump data".  "error occured when processing iscsi logon request. request not retried" initiator failed connect target. target ip address , tcp port number given in dump data".

before creating cluster both nodes able persistent mount partitions. if manually shutdwon node 1 cluster manager, node 2  becomes active node , partitions visible , persistent mounted, mounted partitions no longer visible on node 1. has experienced same issue or know solution this? comments welcome , highly appreciated. thanks

sounds normal.  shared storage 'owned' single node in cluster.  if node1 owns storage, node2 write storage, must communicate through node1.  opposite true.  now, possible have 2 luns , each owned different node of cluster.  in general, sql, best keep luns aligned failover cluster instance (fci) that working data on lun.  if running multiple fcis, should have separate luns each fci.

it possible configure shared storage cluster shared volumes (csv).  in configuration, each node has full read/write access csv, still must working on specific files, i.e. shared access @ volume level, not file/database level.

one other point configuration.  placing iscsi target on dc, have created single point of failure in cluster.  dc goes down , cluster.  might okay needs, should recognize not have true failover cluster because have single point of failure in configuration.


. : | : . : | : . tim




Windows Server  >  High Availability (Clustering)



Comments

Popular posts from this blog

Error: 0x80073701 when trying to add Print Services Role in Windows 2012 Standard

Disconnecting from a Windows Server 2012 R2 file sharing session on a Windows 7,8,10 machine

Windows 2016 RDS event 1306 Connection Broker Client failed to redirect the user... Error: NULL