Solved

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

Posted on 2011-03-18
3
639 Views
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.

http://vmzare.wordpress.com/2007/02/19/vmware-raw-device-mappingrdm/

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1002661

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

asuring
Capture.PNG
0
Comment
Question by:asuring
3 Comments
 
LVL 16

Accepted Solution

by:
danm66 earned 500 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
0
 
LVL 5

Expert Comment

by:Stappmeyer
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.
0
 

Author Closing Comment

by:asuring
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.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If we need to check who deleted a Virtual Machine from our vCenter. Looking this task in logs can be painful and spend lot of time, so the best way to check this is in the vCenter DB. Just connect to vCenter DB(default DB should be VCDB and using…
Last article we focus in how to VMware: How to create and use VMs TAGs – Part 1 so before follow this article and perform the next tasks, you should read the first article how to create the TAG before using them in Veeam Backup Jobs.
Teach the user how to install vSphere Update Manager  Console to Windows system:  Install vSphere Update Manager: Configure vSphere Update Manager plug-in in vSphere Client: Verify vSphere Update Manager settings in vSphere Client:
Teach the user how to install log collectors and how to configure ESXi 5.5 for remote logging Open console session and mount vCenter Server installer: Install vSphere Core Dump Collector: Install vSphere Syslog Collector: Open vSphere Client: Config…

809 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