yep, that's what we did here, too. >>> John Cook <[email protected]> 1/5/2011 9:13 AM >>> I created a new 64 bit guest, put Vcenter 4.1 on it, migrated the hosts, killed the old Vcenter (after moving the licensing info) and used the Update Manager to upgrade the hosts to 4.1.
-----Original Message----- From: N Parr [mailto:[email protected]] Sent: Wednesday, January 05, 2011 12:08 PM To: NT System Admin Issues Subject: RE: Upgrading VMware ESX 3.5 to 4.1 advice needed Why do you have to keep the same host that's running vcenter? Is your DB SQL Express or separate server? Asking because according to Vmware best practice is now to virtualize your vcenter server. We just did our migration from vsphere 4 to esxi 4.1 and I found it was easier to just start over from scratch with vcenter since there's no upgrade path from 32 to 64 bit. And our DB on running SQL Express. I couldn't find a good white paper to lay out a simple way to migrate the vcenter data to a new server. Even with View in use in our environment it was easier to start over from scratch with a new vcenter server. Although we don't have 10 hosts like you do. But yes you are right, add the old hosts to the new vcenter, migrate the machines off to the new hosts and remove. In my case I was re-using the same host hardware so I vmotioned the guests off a host, wiped it, added it to the new vcenter and moved the guests back. -----Original Message----- From: Mike Leone [mailto:[email protected]] Sent: Wednesday, January 05, 2011 10:47 AM To: NT System Admin Issues Subject: Upgrading VMware ESX 3.5 to 4.1 advice needed I have a VMware ESX 3.5 cluster (10 hosts, HA and DRS). We're planning on upgrading to 4.1 by migrating all ESX hosts to new hardware, in the process installing ESX vSphere 4.1. Will have to keep the same host that is running my vCenter, however. I've read that my first step is upgrading vCenter, then the ESX hosts. In my case, I imagine that to mean that - once vCenter is upgraded - I can just add the new ESX hosts to the cluster (or to a different cluster), and then just migrate the VMs from the old ESX 3.5 hosts to the new ESX 4.1 hosts. Then remove the ESX 3.5 hosts. But the new vCenter is 64bit only, and my current vCenter is 32bit. So my first hurdle will be to backup up all pertinent info on my vCenter server; wipe out Windows 32bit and install Win 2008 R2, then get vCenter 4.1 on there and restored. 1. Should I install vCenter 2.5, and restore all the info? And THEN upgrade to vCenter 4.1? 2. Do I just install vCenter 4.1 and restore my 2.5 info, and in the process have it upgrade the data to v4.1 format/schema? #1 seems a bit problematical to me, unless I can install a 64bit vCenter 2.5. Doesn't make much sense to install a 32bit vCenter 2.5, just to have to then upgrade to 64bit vCenter 4.1. I'm reading the vSphere 4.1 Upgrade Guide (<http://www.vmware.com/pdf/vsphere4/r41/vsp_41_upgrade_guide.pdf>), but I'm not getting the guidance as to which process to do, and what specific steps to take to accomplish it. (I may just be extra stupid today and not getting it) Advice? Anyone done this? And have a link to a set of steps? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
