SQL setup question

I have 2 SQL servers, both are 2014, that were setup by another person and I need a little help with understanding the setup.
They are set up with Failover Cluster Manager and both servers appear as nodes and are up.
The storage disks are currently owned by one of the servers and all are online (Data, Witness & DTC).
Both are VM's in a VMware setup.
I have 3 MD3000i storage drives (2 old and 1 new).  I am retiring one of the old drives and putting the new one in service.
Everything is working fine but I need to move both of the SQL Servers from datastore 1 to datastore 2.  I am concerned about data loss and vCenter going down as it is also running on these SQL servers.
I am getting the error "Device SCSI controller 1 is a SCSI controller engaged in bus-sharing" when I try to migrate with them turned on.  So I need to turn one off, migrate it, turn it on, check that it is the owner of the data drives then turn off the other and migrate it.
Both SQL VM's are on datastore 1 and SQL data is on datastore 2.
I started looking at the two VM's to see if any settings were different that might throw a wrench in this plan and noticed a couple of oddities:
1) SQL server 2 is current Owner but when reviewing the VM info in Datastore 1 SQL server 2 is not using any drive space, SQL server 1 is using 41GB.  SQL server 2 also appears in Datastore 2 and is using 41GB.
Is this normal?  I know the data is sitting on Datastore 2.
2) The mapped drives appear in SQL server 2 windows explorer but not in SQL server 1 windows explorer.  Since SQL server 2 is current owner this is correct.  But if SQL server 2 goes down SQL server 1 will become owner and the mapped drives will move.  Correct?
3) When I view the summary of the VM through the Hosts and Cluster view, both SQL servers show they are using datastore 1 (the one I am retiring) and SQL 2 also shows using datastore 2.  But when I browse the datastore 1 from there I only see SQL server 1, no SQL server 2.  When I browse the datastore 1 from "Datastores and Datastores Clusters" both SQL 1 & 2 appear in Datastore 1.  And SQL 2 also appears in Datastore 2.  Normal?
So it looks like vCenter holds space on datastore 1 for the SQL server that is the current owner but also moves it to the datastore with the datadrives.  So if I shut down SQL 2 everything should flip.  SQL 1 will become owner and will move to datastore 2 as the owner.
Anything else I should check before doing the shutdown and migration?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Firstly, vCenter Server is just a management server, it will not affect running VMs if it is off, or unavailable.

What really concerns me is how your Failover Clustering is setup, are both Cluster Nodes running on the same host ?

You mention bus sharing, which makes me wonder if Clustering has been setup in what we call "Cluster in a box" using Virtual Machine disks.

This method of setting up Failover Clustering is not really supported by Microsoft, and is usually just used for demonstrations or labs, not production.

see this document


Failover Clustering should use RDMs, share storage.

As for your final questions with Failover Clustering, only a single node, can own the resources at one time, so the resources will move depending on which is the Active Node which will own the resources, on failure or failover of the Active Node, the resources will be owned by the Passive Node, which now becomes the Active node, and wlll own he resources.

This is an Active/Passive cluster, failover cluster. (so one VM, sits in standby!).

Although your arrangement could be good for for patching, running both on a single ESXi node, does not protect you from host failure. As both nodes will be down.

The issue you have experience with Migration is normal for Cluster in a Box.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
BojikAuthor Commented:
So if I loose both SQL servers I can still connect to each host I just loose the convenience of vCenter, right?  So in a total loss of SQL data I can just create a new vCenter and move on.
Both SQL servers are on separate hosts.
I will look into RMS, thx.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
So if I loose both SQL servers I can still connect to each host I just loose the convenience of vCenter, right?  So in a total loss of SQL data I can just create a new vCenter and move on.
Yes, Yes and Yes.

vCenter Server needs an SQL Server to function.

vCenter Server is just a management server, which allows you to manage all ESXi hosts from a single interface, and username and password account.

If vCenter Server is not available for what ever reason, SQL server down, vCenter Server (Windows down), you can still login and connect directly to each ESXi server.
BojikAuthor Commented:
great, thx
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.