Upgrading vCenter server 2.5 u4 to Virtual Center 4.1
This article provides steps to upgrade an instance of vCenter Server 2.5
and its updates to a more recent update or to vCenter Server 4.1
1. Deploy a new vCenter Server.
a. Deploy a new Virtual Machine (name has 15 or fewer characters) (eg. MX093EVCIP01)
b. Verify Virtual machine/Server hosting vCenter4.1 meets minimum requirements (2 CPUs, 64-bit 2008 R2 O/S)
2. Make sure your hardware requirements are compliant:
i) Processor – 2 CPUs 2.0GHz or higher Intel or AMD x86 processors. Processor requirements may be higher if the database runs on the same machine.
ii) Memory – 3GB RAM. RAM requirements may be higher if your database runs on the same machine.
iii) Disk storage – 2GB. Disk requirements may be higher if your database runs on the same machine.
iv) Networking – 1Gbit recommended.
Verify that your existing database is supported with vCenter Server 4.0. If it is not, upgrade your existing database to a supported type
3. Supported Microsoft SQL Server Databases:
Microsoft SQL Server 2005 ExpressNote: Microsoft SQL Server 2005 Express is intended to be used for small deployments of up to 5 hosts and/or 50 virtual machines.
Microsoft SQL Server 2005 Standard edition (SP1, SP2, SP3)
Microsoft SQL Server 2005 Standard edition (SP2, SP3) 64bit
Microsoft SQL Server 2005 Enterprise edition (SP1, SP2, SP3)
Microsoft SQL Server 2005 Enterprise edition (SP2, SP3) 64bit
Microsoft SQL Server 2008 Standard Edition
Microsoft SQL Server 2008 Standard Edition 64bit
Microsoft SQL Server 2008 Enterprise Edition
Microsoft SQL Server 2008 Enterprise Edition 64bit
4. Oracle Database Support:
Oracle 10g Standard edition (Release 1 [10.1.0.3.0])
Oracle 10g Enterprise edition (Release 1 [10.1.0.3.0])
Oracle 10g Standard edition (Release 2 [10.2.0.1.0])
Oracle 10g Enterprise edition (Release 2 [10.2.0.1.0])
Oracle 10g Enterprise edition (Release 2 [10.2.0.1.0]) x64
Oracle 11g Standard edition
Oracle 11g Enterprise edition
Snapshot source vCenter server and make sure there is a full backup of the vCenter database.
Log on as Administrator on the source vCenter server and confirm VMware Virtual Center Server and the Update Manager service is stopped.
Insert the VMware vCenter Server Installation DVD and double-click
autorun.exe.
autorun.exe.
Click Explore media.
Open the datamigration folder and extract the datamigration.zip archive to a writable local drive (eg. C drive or D drive) where you have sufficient space on the source Virtual Center server.
Backup Virtual Center Server Configuration with Data Migration tool
i. Confirm Virtual Center service is stopped
ii. Confirm the “\datamigration\data\” folder does not exist on the Virtual Center server. If it does then rename or remove folder
iii. Explore media on the vCenter Server installation media
iv. Open the “datamigration” folder and extract the “datamigration.zip” to a local file system on the Virtual Center machine
v. Open a command line, change to the datamigration folder and type backup.bat to start the tool
vi. Follow the prompts
vii. The script checks the vCenter Server version, database type, vCenter Update Manager configuration (if installed), and vCenter Orchestrator configuration (if installed) to determine whether they are compatible
with the data migration tool.
with the data migration tool.
viii. If VMware vCenter Update Manager is not installed, enter y when prompted to continue the backup. The Virtual Center or vCenter Server configuration data and the SQL Server Express database (if applicable) are copied to the \data folder in the extracted folder. The Virtual Center or vCenter Server database instance is upgraded to be compatible with vCenter Server 4.1.
ix. Check \logs\backup.log in the datamigration folder for errors and If you find no errors, the data backup was successful. If you find errors, correct the source of the error and rerun backup.bat before proceeding.
On the new vCenter server create a 64-Bit DSN
x. Install 64-bit ODBC drivers to “c:\program files\vmware\infrastructure\virtualcenter server”
xi. Go to control panel > Administrative Tools > Data Sources (ODBC)
xii. Create a system DSN and then test connectivity to vCenter Database. Use new DSN during vCenter Server installation
Restore VirtualCenter config and install vCenter
xiii. Copy the datamigration folder from the VirtualCenter server to the new vCenter server
xiv. Connect the installation media to the new server
xv. From a command prompt, change to the copied datamigration folder (there is also one on the installation media – do not use) and run Install.bat
xvi. Enter path to installation media
xvii. Respond to installation prompts – until database prompts
xviii. if you’re restoring this onto a server with a different name, you’ll see an info message:
xix. “The name of this machine is different than backup system name ULVCS01
Do you want to continue install ...? yn: y “
xx. Answering yes will launch the install of vCenter:
xxi. Click use an existing supported database (page 44 – erase when caught up)
xxii. Select DSN
Upgrade ESX host 3.5 to ESXi4.1 through update manager.
a. VMware Update Manager
i. Update all existing ESX hosts to the latest patch levels prior to upgrading to vSphere 4.1
ii. Create vSphere 4.1 host baseline in Update Manager
iii. Perform update of each ESX host by applying baseline to Production View ESX hosts
6. VM upgrade (15min/VM servers - Update VMTools on all VM servers on new vSphere hosts
Comments
Post a Comment