MS Cluster hosted in ESXI3.5 local disk Move to ESX 4.1 with EVA 8100 FC SAN Backend

Posted on 2011-03-18
Medium Priority
Last Modified: 2012-05-11
Hi EE community

We have a MS SQL05 2 node cluster in an ESXI 3.5 Host running on a DL380 G5 hardware with about 1TB of local disk. All cluster Data and Quorum Disks are sitting inside their own individual VMDK's and not RDM mappings. I've included a screen shot of the current configuration.

We now have a enterprise licensed 7 host ESXi 4.1U1 clustered environment operating on a 200TB HP EVA 8100 with FC back-end.

We need to move the 2 node MS cluster into the 4.1U1 ESX/SAN environment. We've been reading through the following article for points of references for us.



What I'm asking is if anyone else has experiences with this type of migration and if so what caveats have you come across? Advice? suggestion? etc....

Thank EE community

Question by:asuring
LVL 16

Accepted Solution

Danny McDaniel earned 1500 total points
ID: 35170362
I don't have any experience with this... but I would recommend you familiarize yourself with the guide at: http://www.vmware.com/pdf/vsphere4/r41/vsp_41_mscs.pdf to make sure that you meet all of the requirements

Expert Comment

ID: 35171365
Reviewing the document that danm66 noted is likely the best place to start. You may want to build a new cluster to test and gain practice before you move it.  My other suggestion might be to build a new cluster with SQL and migrate the databases.  I would do this if your currently running Windows 2003 / SQL 2005 and are ready to move to Windows 2008/SQL 2008.

Author Closing Comment

ID: 35452767
We ended up having to call VMWARE support as I believed we had discovered a bug in 3.5 and after 9 hours the bug was confirmed. It ended up being a really really long process by which we had to share a new data store with both the 3.5 and 4.1 box, convert into the 4.1 data store then from the 4.1 box convert to rdm.

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
In this article, we will see two different methods to recover deleted data. The first option will be using the transaction log to identify the operation and restore it in a specified section of the transaction log. The second option is simpler and c…
Teach the user how to configure vSphere Replication and how to protect and recover VMs Open vSphere Web Client: Verify vsphere Replication is enabled: Enable vSphere Replication for a virtual machine: Verify replicated VM is created: Recover replica…
This Micro Tutorial steps you through the configuration steps to configure your ESXi host Management Network settings and test the management network, ensure the host is recognized by the DNS Server, configure a new password, and the troubleshooting…
Suggested Courses

624 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question