Hi,
We have a LUN (contain VM image) that is attached to two ESX3.0 server. We will be buying 2 new vSphere 4.1 server.
Now what we want to do is to point the LUN that is currently connected to ESX3.0, dismount it and point it to vSphere 4.1. We will then bring the VM up in vSphere 4.1. We may be naive to think that we will just need to upgrade the vmtools in each VM and this will bring it in sync with vSphere 4.1.
May I know is this possible?
Thanks.
Am I correct to say is that the recommended way is still to create a new LUN, format it to the latest version of VMFS, then migrate all the vmdk over to the new LUN?
Also, is it possible that you tell me what are some of the features that requires the latest VMFS format?
It may make sense for you to migrate the VM's to a new datastore, if your current datastore is formatted with a VMFS version lower than 3.31.
We had a discussion about VMFS versions some time ago at http://communities.vmware.com/message/1587659
One point, which has not been mentioned so far, you should make sure your storage is supported for version 4.1. There were some changes which may require a storage upgrade or a firmware upgrade. (see http://www.vmware.com/resources/compatibility/search.php?deviceCategory=san)
Yes before the VMware tools, you will need to right click the VM name (assume you have register it) and upgrade virtual hardware
It's the other way around. FIRST update VMware tools and then upgrade the hardware. Otherwise you will end up with a VM which may not boot due to missing drivers!!!
André
Hi.
Yes before the vmware tools, you will need to right click the VM name (assume you have register it) and upgrade virtual hardware.
iDLE-jAM | VCP 2, VCP 3 & VCP 4
If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points.
Yes, it will work. In your example, you will have to re-register all the virtual servers. Try it this way to avoid the registration issue: http://itvirtuality.wordpress.com/2010/08/07/let-the-migrations-begin/
Here's another thing to consider..some of the newest disk related features in 4.1 require the latest version of VMFS. The only way to get there is to present a new LUN and have esx 4.1 format it. So once you get everything over to esx 4.1 using the above method of your choice, present a new LUN, create the new datastore, and then do a storage vmotion to the new datastore.
adam
Hi Adam,
Am I correct to say is that the recommended way is still to create a new LUN, format it to the latest version of VMFS, then migrate all the vmdk over to the new LUN?
Also, is it possible that you tell me what are some of the features that requires the latest VMFS format?
Thanks.
Am I correct to say is that the recommended way is still to create a new LUN, format it to the latest version of VMFS, then migrate all the vmdk over to the new LUN?
Also, is it possible that you tell me what are some of the features that requires the latest VMFS format?
It may make sense for you to migrate the VM's to a new datastore, if your current datastore is formatted with a VMFS version lower than 3.31.
We had a discussion about VMFS versions some time ago at http://communities.vmware.com/message/1587659
One point, which has not been mentioned so far, you should make sure your storage is supported for version 4.1. There were some changes which may require a storage upgrade or a firmware upgrade. (see http://www.vmware.com/resources/compatibility/search.php?deviceCategory=san)
Yes before the VMware tools, you will need to right click the VM name (assume you have register it) and upgrade virtual hardware
It's the other way around. FIRST update VMware tools and then upgrade the hardware. Otherwise you will end up with a VM which may not boot due to missing drivers!!!
André
Not the recommended way, just another alternative. As my wife would say, "Options are a good thing to have".
I am not 100% sure, but I think SIOC requires a certain level of VMFS. Possible a few other items. If you search the forums, people occassionaly post about it. Check out this post for more info too: http://www.vfrank.org/2010/01/31/vmfs-3-versions-maybe-you-should-upgrade-your-vmfs/
adam