Hi
I've got a customer who only has 1 ESX server. It's running ESX 2.5.3 and they've been advised to upgrade. For their DR - the VM's have a Shadow Protect image taken daily.
Since they don't have another host (or VC) - I can't vmotion the VM's off to another host and stage the upgrade/new install.
So from where I stand there are two options..... Upgrade their server from 2.5.3 to 3.5.x........ or take an image of each VM (they only have 4!) and rebuild the server with a fresh install of 3.5.x (maybe to update 2 if the license issue gets fixed soon!) - then restore the VM's from image.
Any opinions or experiences in regards to either of the above methods? I haven't done an upgrade from 2.5.x to 3.5
Any time estimates for an inplace upgrade? From what I've read there are a number of steps (3 reboots etc) for the upgrade as per the vmware guide.
With a single host, I'd see if you could get them to spring for a second box (for four VMs, it could be small!). Then, I'd do a rolling upgrade. They could then use the original system (upgraded to 3.5) as their DR box.
If you can't convince them of the benefit of a second box, then I'd go the backup/clean install/restore route if you can afford the downtime. If you have the available capacity on the existing host, I would do a test restore of the VMs prior to ANY migration approach
Ken Cline
Technical Director, Virtualization
VMware Communities User Moderator
With a single host, I'd see if you could get them to spring for a second box (for four VMs, it could be small!). Then, I'd do a rolling upgrade. They could then use the original system (upgraded to 3.5) as their DR box.
If you can't convince them of the benefit of a second box, then I'd go the backup/clean install/restore route if you can afford the downtime. If you have the available capacity on the existing host, I would do a test restore of the VMs prior to ANY migration approach
Ken Cline
Technical Director, Virtualization
VMware Communities User Moderator
Hello,
When I first went to v3 from v2.5.x I first did a backup of all my VMs (much less than I have now), then did a fresh install and did a reinstall.
This was by far the cleanest approach. It gave me a time to reallocate my local disks appropriately and fix any other differences that exist between the two releases. I would suggest a complete reinstall of the ESX host and a good clean backup of the VMs.
Best regards,
Edward L. Haletky
VMware Communities User Moderator
====
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354
As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization
Hi guys - thanks for your responses. I agree with you both - definitely prefer to go down the new install path. I can just imagine issues being experienced with such a major upgrade due to the differences in versions.
However the restores of the VM's will be a bit of a pain - no Virtual Center means no importing of Shadow Protect images...... it'll be the same method I used when I recovered them in a DR - Create a new VM - boot off the Shadow Protect CD and restore the image to the new VM...... to be repeated on all servers.
But still - better than a messy upgrade!
Hello,
Why not just use VMware Converter to create a copy on some other location? Then use VMware Converter to import the copy back into ESX? I never used shadow protect but I did use this method with quite a bit of success.
Best regards,
Edward L. Haletky
VMware Communities User Moderator
====
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354
As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization
With the free version of converter I could install it on a physical box and then import the shadow protect images couldn't I? I'm fairly certain the free version allows this? Or I could also do what you recommended by exporting and then importing. That way I'm covered with two methods. Definitely save the hassle of re-creating the VM..... booting off a CD/iso....... restoring the image etc as converter will take care of it all.....
Hi guys - well this has been put on the back burner for the past couple of months and now looks on the cards again.
I need to clarify something however.... from what this comparison chart displays (see below), my understanding of it is that I cannot use the free version of converter for this client as they are using ESX 2.5.3 without VirtualCenter.
Where it say's for remote conversion..... "If VMware ESX is the destination, VMware Converter Enterprise is required"
Is my understanding correct?
Or if I installed the free version of converter on each VM and then saved the image of the VM to a remote destination I would then be OK to re-import the VM's that were converted by converter into the new VI3 environment (without VC)?
I've still got points to allocate :smileygrin:
Hello,
I use the free version of VMware Converter all the time to and from ESX. You just have to do each system individually. Granted I did finally install the license....
Best regards,
Edward L. Haletky
VMware Communities User Moderator
====
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354
As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization
Thanks for your feedback Edward - I appreciate it.
When you say you use the free version all the time to and from ESX........ is this in environments where there is no VC?
In regards to my questions posted before....... would I have to install the free version on each VM or can I do it all from a remote box? To be honest I'm a bit confused with this - I've always used converter with VC or cold clones.
Hello,
Yes with and without VC. I install VC onto a desktop and use it from there. Just make sure the desktop has enough space to place the VMs.
Best regards,
Edward L. Haletky
VMware Communities User Moderator
====
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354
As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization
Thanks Edward