?
Solved

vCenter upgrade questions

Posted on 2010-09-15
23
Medium Priority
?
861 Views
Last Modified: 2012-05-10
I need to upgrade my ESX 3.5 environment.  First I am thinking vCenter.  I have 2.5 version with 147633 build.  Full blown SQL 2005.
What are the procedures doing that?  I cannot find the correct documentation on that.

Can I go directly from 3.5 to 4.1?  or 4.0 first?
Will it affect the hosts in any way?  Do I need to reboot?  I am thinking to make a SAN snapshot prior to upgrade.

Please advice.
Thanks!!
0
Comment
Question by:Tiras25
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 12
  • 7
  • 2
  • +2
23 Comments
 
LVL 3

Expert Comment

by:elmagoal
ID: 33684670
0
 
LVL 10

Expert Comment

by:BloodRed
ID: 33684709
Here is VMware's process for upgrading to vCenter 4.1 and ESXi 4.1:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1022104

It's a pretty straightforward process.  You are right that you will want to upgrade vCenter first, you cannot manage ESX 4.1 from an older version of vCenter/Virtual Center.
0
 
LVL 17

Author Comment

by:Tiras25
ID: 33684760
I will review these.  Also, has anyone done straight from 3.5 to 4.1?  
0
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

 
LVL 19

Expert Comment

by:vmwarun - Arun
ID: 33684841
A point worth remembering is vCenter 4.1 is x64 only, no more x86.

This is how I would do it

1.Backup the VirtualCenter DB first
2.Upgrade the vCenter version from 3.5 to 4.1 (check the physical server whether it is compatible for 64-Bit compatibility if vCenter is running as a physical box.)

I don't think the hosts need to be rebooted in anyway.

Make sure that you configure the licensing server information correctly since licensing model has been changed in vSphere where 25-digit alpha numeric product keys are being used instead of *.lic files
0
 
LVL 17

Author Comment

by:Tiras25
ID: 33685028
vCenter is a VM, no worries about the 64bit.

So go straight upgrade from 3.5 to 4.1 by executing the file?
0
 
LVL 4

Expert Comment

by:VMwareGuy
ID: 33691202
Back up DB, upgrade vCenter, it isn't a true upgrade but rather a re-install because of the your important data resides in the DB.  What you lose if you don't backup your DB and you fail is vcenter logical groups and permissions, and perf data that has been collected over time, as well as HA cluster stuff.  Then ugrade your VI client immediately.  If you don't upgrade your client to a matching version you won't be able to resiger or start VMs.  
0
 
LVL 17

Author Comment

by:Tiras25
ID: 33694114
Looks like I will go with 4.0 upgrade.  My OS is not 64bit.  

do I still need to backup SQL 2005 DB?   Never done that.
0
 
LVL 4

Accepted Solution

by:
VMwareGuy earned 2000 total points
ID: 33694269
only if you don't want to recreate your permissions,logical groups, etc..   In small environments where perf data and permissions aren't important I just do it without concern, haven't seen a DB failure yet.  Last time I saw DB failure was upgrading from ESX 2.5 to VI3 (ESX 3.01).  

Here is a short tutorial on the backup of SQL 2005, looks like they are doing it with MS SQL sesrver managemnt studio..

http://www.exforsys.com/tutorials/sql-server-2005/sql-server-database-backup.html

0
 
LVL 17

Author Comment

by:Tiras25
ID: 33694363
I can probably do a quick SAN snapshot so I know I am safe.

So will I have to recreate all the permissions,logical groups, etc?  Or its only in the event of the failure?
0
 
LVL 4

Expert Comment

by:VMwareGuy
ID: 33694546
Only in the event of failure.   The schema is vcenter 2.x DB is not compatible with 4.x, so if it fails, you lose your DB if you try to revert back.  Take a look at this file, it was hard to find, but it is for upgrading to vcetner 4.0.
Upgrade-Guide.pdf
0
 
LVL 17

Author Comment

by:Tiras25
ID: 33694676
Got it.  I have this document but not too much about the vCenter upgrade there.  

My vCenter server is physical btw.
0
 
LVL 4

Expert Comment

by:VMwareGuy
ID: 33694823
IT has what you need.  I  just looked it over, You should be fine, your DB is supported.  Here is what will happen:

The Database Upgrade wizard runs after you click Install in the vCenter Server installer. The Database
Upgrade wizard upgrades the database schema to make it compatible with vCenter Server 4.0. The schema
defines the tables, the fields in each table, and the relationships between fields and tables.
If you are upgrading from VirtualCenter 2.5, the Database Upgrade wizard runs in the background. If you are
upgrading from VirtualCenter 2.0.x, the Database Upgrade wizard appears and you must complete the wizard.  

0
 
LVL 17

Author Comment

by:Tiras25
ID: 33694900
OK thank you!  

Let me check again.  I am more worry about the DB backup/recovery.  Since its a physical server I cannot do a SAN snapshot.  
0
 
LVL 17

Author Comment

by:Tiras25
ID: 33695034
OK so I will go ahead with you DB backup instruction link.  

After that; should I then execute the upgrade autorun file?
0
 
LVL 4

Expert Comment

by:VMwareGuy
ID: 33695120
Yes - you will find there isn't much to it.  keep the doc handy during the process just in case you are uncertain about something.  it really is a straight forward process.  Very easy.  
0
 
LVL 17

Author Comment

by:Tiras25
ID: 33695210
Thank you again.  So far I am dealing with DB backup.  Not enough disk space for backup:-).....
0
 
LVL 17

Author Comment

by:Tiras25
ID: 33703235
Just went through the upgrade procedure.  All finished!
The SQL server goes insane now.  Uses almost all 4GB RAM.  Server almost non-responsive.  
Should I wait or reboot?
0
 
LVL 4

Expert Comment

by:VMwareGuy
ID: 33705716
boot.  
0
 
LVL 17

Author Comment

by:Tiras25
ID: 33705722
Helped thank you!!!
0
 
LVL 4

Expert Comment

by:VMwareGuy
ID: 33705727
it was a microsoft issue   :)
0
 
LVL 17

Author Comment

by:Tiras25
ID: 33705737
HA HA HA
Perferct!!!
0
 
LVL 17

Author Comment

by:Tiras25
ID: 33727709
Really slow after the upgrade.  sql server takes a lot of memory.  only 50MB free of 4GB total.  Reboot few times helpes first but then occupies all the RAM again and gets really slow..
0
 
LVL 19

Expert Comment

by:vmwarun - Arun
ID: 33727985
I believe that you can post this as a separate question since this would not be shown in the queue of VMware questions.
0

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Is your company's data protection keeping pace with virtualization? Here are 7 dynamic ways to adapt to rapid breakthroughs in technology.
A look into Log Analysis and Effective Critical Alerting.
This video shows you how to use a vSphere client to connect to your ESX host as the root user. Demonstrates the basic connection of bypassing certification set up. Demonstrates how to access the traditional view to begin managing your virtual mac…
This video shows you how easy it is to boot from ISO images for virtual machines with the ISO images stored on a local datastore on the ESXi host.
Suggested Courses

765 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question