Link to home
Start Free TrialLog in
Avatar of epmmis
epmmis

asked on

vmware upgrade to v5 - looking for comment

Background - Two site v4 u2 vsphere environment.
SRM is used to protect the production site.  
Prod site has 3 ESX host servers.  
DR site has 3 ESXi host servers.  
There are two physical vCenter servers using Windows 2003 32b and SQL 2005 express.  
SQL 2005 express is loaded on the vCenter servers.
2005 SQL express needs to be upgraded to full SQL Server.  We have exceeded SQL express's capacity.
The hardware is on the v5 compatibility list.

Here is the upgrade path I am considering.
1.       P2V both physical vCenter servers; PROD_SERVER & DR_SERVER.
2.       Ensure vCenter & SRM is stable on the virutal consoles before continuing.
3.       Use the vmware procedure for doing an inplace SQL server upgrade on virtual vCenter servers.
4.       Ensure vCenter & SRM is stable before continuing.
5.       Rebuild physical PROD_SERVER & DR_SERVER.
      a.     OS – Windows 2008 R2 64b
      b.    Add 32 GB RAM
      c.    SQL 2008 R2 Standard 64b
6.       Install vCenter, Update Manager and SRM on physical consoles.
7.       Install ESXi 5 u1 on esx hosts
8.       Upgrade VM hardware and VM tools on all VM

What do you think of the P2V of the physical vCenter servers?  The virtual vCenter servers are temporary and will be used a "bridge" for the upgrade..

Our prod_cluster has outgrown SQL express.  My thought is to do an inplace upgrade on the virutal vCenter servers.  This way we can snapshot to rollback the upgrade, if needed.
ASKER CERTIFIED SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of epmmis
epmmis

ASKER

Tested the DR Site vCenter p2v.  Here are lessons learned when P2Ving a virtual center server .  But first some background.

Networking consist of only a distributed vSwitch, with an isolated and a connected port groups. The isolated port groups isolates VMs from the network. It is a good place for duplicated VMs.
.  
1.  When configuring the P2V do not select the isolated port group.  As the connected port group is not avaiable when editing settings on an ESX host.  

2.  After the P2V, change the virtual vCenter's PC name and IP address.  Bring the physcial vCenter on line.  It is the easiest way to change the virtual nic from flexible to VNNET 3 adapter and connect to the online port group.  

3.  After step 1 & 2, delete all the hidden drivers to clean out the virtual vCenter.
Avatar of epmmis

ASKER

hanccocka - I booked marked your article and will use it when we upgrade to v5.  All of our P2v are Windows 2003 or XP PC.
just remember OEM licenses do not work after P2V, so P2V is for Retail or volume licenses only.
Avatar of epmmis

ASKER

Thanks for the license info.

We are using a volume license key and each esx hosts has data center licensing assigned to them.  so we are ok for licensing.