On 6/30/2010 11:48 AM, Garcia-Moran, Carlos had this to say:
Migration will be very straightforward, but will require downtime on the
guests since you are changing Hardware in the Hosts and ESX Versions, as
long as the cluster's share the same storage do the following at a high
level.
1) Load up the new hardware with ESX, Create your new cluster "B" , make
sure all your networks look the same config wise
OK .. you mean load the new hardware with vSphere v4, not ESX 3.5, right?
2) Shutdown a Guest, Move from Cluster A to Cluster B (migrate option in
VC)
And no problem migrating from ESX 3.5 to vSphere v4? No upgrade
prerequisites for the VMs? (I've migrated between hosts often, yes)
3) Turn on, upgrade VM Tools to latest
4) Shutdown, upgrade virtual hardware
"upgrade virtual hardware"? In what way and why? Is that something that
vSphere requires? I don't need to change the specs on my VMs, if that's
what you're referring to here.
5) Turn on, run windows update in case you need Stuff like "AMD Opteron"
/ "Intel" updates
6) Rinse and Repeat for all guests
Sounds manageable enough. Thanks!
Replication DR gets a little more complex since it's dependent on quite
a few things, you can use SRM, but to do so you need to be able to do
storage replication 1st with your SAN's. there's other backups / restore
product's out there like Vizioncore and PHDvirtual
Yeah, my current SAN here is an HP EVA; no idea what the SAN is going to
be at the hot site is; I haven't been involved in that, but hopefully
it's all the same module stuff from HP, for consistency sake.
Thanks
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
