windows 2016 failover 2 node cluster shared disk data issue

%3CLINGO-SUB%20id%3D%22lingo-sub-787438%22%20slang%3D%22en-US%22%3Ewindows%202016%20failover%202%20node%20cluster%20shared%20disk%20data%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-787438%22%20slang%3D%22en-US%22%3E%3CDIV%3EDescription%20of%20the%20problem%3A%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EFailover%20cluster%20in%20%3CSPAN%20class%3D%22il%22%3Ewindows%3C%2FSPAN%3E%3CSPAN%20class%3D%22il%22%3E2016%3C%2FSPAN%3Eunder%20simplivity%20has%20issue%20with%20the%20shared%20disk%2C%20for%20example%20anything%20written%20on%20%22shared%20disk%20cluster%22%20owned%20under%20node01%20cannot%20be%20reflected%20on%20node02%20while%20takenover%20by%20the%20node02.%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EEngineer%20Response%3A%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%22%3C%2FDIV%3E%3CDIV%3ELooked%20into%20it%20thoroughly%20and%20tested%20all%20option%20to%20resolve%20the%20issue%2C%20looks%20to%20me%20now%20that%20HP%20cluster%20configuration%20itself%20have%20shared%20disk%20problem.%3C%2FDIV%3E%3CDIV%3E%3CP%3EHP%20need%20to%20see%20this%20issue%2C%20create%20any%20test%20file%20in%20cluster%20shared%20disk%20and%20write%20some%20files%20from%20node1%20and%20then%20for%20test%20purpose%20node1%20need%20to%20be%20switchover%20to%20node2%20and%20see%20if%20the%20file%20written%20by%20node1%20is%20visible%20through%20node2.%3C%2FP%3E%3CP%3E%22%3C%2FP%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-787438%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Efailover%20cluster%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eshared%20disk%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20server%202016%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-792458%22%20slang%3D%22en-US%22%3ERe%3A%20windows%202016%20failover%202%20node%20cluster%20shared%20disk%20data%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-792458%22%20slang%3D%22en-US%22%3EDoes%20the%20cluster%20validation%20give%20you%20All%20success%20green%20marks%3F%3CBR%20%2F%3Ealso%20is%20that%20shared%20disk%20a%20SAN%3F%20ISCSI%20or%20Fiber%3F%3CBR%20%2F%3E%3CBR%20%2F%3EI%20had%20setup%20a%20cluster%20fail%20over%20VM%2C%20when%20node%201%20is%20the%20owner%20of%20the%20VM%20and%20the%20disks%2C%20those%20disks%20will%20have%20%22reserved%22%20status%20for%20other%20nodes%2C%20so%20there%20won't%20be%20any%20file%20corruption%20and%20so%20if%20node%201%20writes%20to%20the%20disks%2C%20those%20changes%20should%20be%20visible%20to%20other%20disks.%3CBR%20%2F%3Ei%20was%20using%20a%20nested%20virtualization%20using%20ISCSI%20SAN%20(all%20virtual)%20on%20Windows%20Server%202019%20Hyper-V.%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor
Description of the problem:
 
Failover cluster in windows 2016 under simplivity has issue with the shared disk, for example anything written on "shared disk cluster" owned under node01 cannot be reflected on node02 while takenover by the node02.
 
Engineer Response:
 
"
Looked into it thoroughly and tested all option to resolve the issue, looks to me now that HP cluster configuration itself have shared disk problem.

HP need to see this issue, create any test file in cluster shared disk and write some files from node1 and then for test purpose node1 need to be switchover to node2 and see if the file written by node1 is visible through node2.

"

1 Reply
Highlighted
Does the cluster validation give you All success green marks?
also is that shared disk a SAN? ISCSI or Fiber?

I had setup a cluster fail over VM, when node 1 is the owner of the VM and the disks, those disks will have "reserved" status for other nodes, so there won't be any file corruption and so if node 1 writes to the disks, those changes should be visible to other disks.
i was using a nested virtualization using ISCSI SAN (all virtual) on Windows Server 2019 Hyper-V.