Jump to content

Recommended Posts

Posted

I've got a two node cluster utilising a iSCSI SAN which has been working pretty well. However, last night I did a whole load of Updates to the VMs, and then turned my attention to one of the Host machines and allowed all the necessary updates to come down, restart etc. Before this, I shuffled all the VMs over to the other Host and let the update process begin; all seemed well. That is, until I started moving the VMs back over to their original host . (HOST A). Not all the servers would. So, dig deeper and on that updated Host the C:\ClusterStorage folder has two of the Volume Folders empty. The other Host (HOST B), can however see all the Volume folders no problem.

 

Bit out of my comfort zone this, as the server was setup by another company (I've put a call in and am waiting for a response), but unsure as to what to configure. On HOST A with the issue, it shows iSCSI entries for two of the volumes, but the other two show \\?\Volume{xxxxxx.... } , HOST B is showing four entries: C:\ClusterStorage\Volum... etc\'. What I did notice also is that within the Failover Cluster Manager, within Storage, the Disks that are working are on HOST A are down as the Owner Node, whereas the disks that aren't working on HOST A are set to HOST B as the Owner Node. I can't for the life remember if this is correct, or wether before the updates all the Cluster Disks were set to HOST A as the owner. A bit cautious to tweak anything at this point, but hoping someone could offer me some help. All servers at the moment are happily running on HOST B, so hoping that messing about with the config on HOST A won't upset things too much as we do have actice users onsite at the moment.

 

TIA

 

Pete

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...