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
646 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
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

Don't Miss ATEN at InfoComm 2017!

Visit booth #2167 to see the  new ATEN VM3200 32 x 32 Modular Matrix Switch. Other highlights include the VE8950 4K HDMI Over IP Extender, VS1912 12-Port DP Video Wall Media Player  and VK2100 ATEN Control System. Register now with Free Pass Code ATEN288!

Question has a verified solution.

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

This article will show you how to create an ISO CD-ROM/DVD-ROM image (*.iso), and MD5 checksum signature, for use with VMware vSphere Hypervisor 6.5 (ESXi 6.5). It's a good idea to compare checksums, because many installations fail because of a corr…
Ransomware is a malware that is again in the list of security  concerns. Not only for companies, but also for Government security and  even at personal use. IT departments should be aware and have the right  knowledge to how to fight it.
Teach the user how to rename, unmount, delete and upgrade VMFS datastores. Open vSphere Web Client: Rename VMFS and NFS datastores: Upgrade VMFS-3 volume to VMFS-5: Unmount VMFS datastore: Delete a VMFS datastore:
Teach the user how to convert virtaul disk file formats and how to rename virtual machine files on datastores. Open vSphere Web Client: Review VM disk settings: Migrate VM to new datastore with a thick provisioned (lazy zeroed) disk format: Rename a…

717 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