skip to content »

Updating virtualcenter

Download our latest guide to the top strategies solution providers can leverage for starting up and securing a cloud practice, successful approaches to selling and marketing cloud, and why it is urgent for partners to transition now.

If you are using the built-in database, you can select Use Virtual Center credentials. At the Select Mode screen, choose to scan all hosts or select custom mode to select the hosts; if you select custom mode, the next screen will let you choose the hosts. At the Run Test screen, click the “Run precheck” button to begin checking the hosts.Some quick googling led me to the VMware KB article I then noticed that the SQL Agent was not running on the old v Center Server.The SQL Agent Service had been disabled and because of this the v Center performance data roll up jobs were not being run.The database was detached from the original physical v Center Server, the db and log files were copied to the new v Center virtual machine, and the database was then attached to the the new SQL server.The v Center ODBC connection to the new database was created and tested, all looked fine.Solution provider’s takeaway: Knowing the best way to handle a v Sphere upgrade on all levels, v Center Server, ESX and ESXi hosts and virtual machines, will make life easier for you and your customers.

Learn about the upgrade tools available and get step-by-step instruction on using them, including the pre-check tool, licensing updates, Oracle database updates, the host update utility and more.

I created a backup of the original v Center database and for the size of the environment the database was ginormous, a little over 15GB.

I thought that was odd but for whatever reason I did not really dig into it much (until this would cause the upgrade to fail – keep reading).

The tool checks each host for some of the usual things that cause the agent installation to fail.

This includes making sure the host has sufficient disk space on the Service Console partitions, the host is reachable, the filesystem is intact, and any required patches are applied.

Recently I was given a project to upgrade a 4.0 ESX environment to 5.1 (actually I have had a couple few of these upgrades recently).