moving vCenter 5 server on 2003 to new 5.1 server on 2008R2
Hello,
I need to move vCenter to a 2008 R2 server from a 2003 64-bit server. Would it be easier / is it feasible to just install a fresh vCenter server as opposed to migrating everything? I only have two hosts with 7 VMs on each (14 total) in this location.
Either way, any direction on the simplest way to either migrate the existing instance or configure a new one from scratch is appreciated.
Thanks
I need to move vCenter to a 2008 R2 server from a 2003 64-bit server. Would it be easier / is it feasible to just install a fresh vCenter server as opposed to migrating everything? I only have two hosts with 7 VMs on each (14 total) in this location.
Either way, any direction on the simplest way to either migrate the existing instance or configure a new one from scratch is appreciated.
Thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
To be honest with you, re-install vCenter Server from scratch. Unless you desperately want to keep older performance Summary data.
ASKER
thanks aravindsivaraman. I had seen that article earlier when I was looking into this. I have a local SQL instance and was hoping I could just start from scratch so-to-speak.
thanks hanccocka. Ha. No need to keep that old data. Would I need to shutdown the old vCenter server prior to putting the new one into production? Do I need to update the hosts or VMs in any way to point to the new vCenter server? I appreciate any direction on configuring a new vCenter server that won't conflict with the old one.
thanks hanccocka. Ha. No need to keep that old data. Would I need to shutdown the old vCenter server prior to putting the new one into production? Do I need to update the hosts or VMs in any way to point to the new vCenter server? I appreciate any direction on configuring a new vCenter server that won't conflict with the old one.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
awesome - thanks. Hate to nest a question but I am getting conflicting info regarding going to 5.1 or 5.5. I would like to be cautious at this site and generally don't like to install into production new software as soon as it is released. Again though, I am receiving conflicting info. May I get your opinion / ask what you have done (or will do)?
Thanks
Thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You would be a fool, to jump to 5.5 at this present time!
ASKER
thanks coolsport00. excellent info.
hanccocka - seemingly I am a fool for several reasons. the move to 5.5 at this time will not be able to be counted as one of those reasons.
Thanks fellas, much appreciated.
hanccocka - seemingly I am a fool for several reasons. the move to 5.5 at this time will not be able to be counted as one of those reasons.
Thanks fellas, much appreciated.
No problem; as an FYI... I *always* wait to at least an Update release to vSphere before I install. If my boss is impatient in doing so, I stall him :) No sense in spending a bunch of time troubleshooting 'bugs' that exist in a new GA release of software IMO.
Cheers!
~coolsport00
Cheers!
~coolsport00
We only deploy GA to New VMware vSphere Clients.....