VMware Cloud Community

Upgrade vCenter to 4.1 update 1 failed.

We are trying to upgrade our vCenter from version 4.0 to ersion 4.1 update 1

For this purpose we installed a new server with Sindows Server 2008 R2 and MS SQL2008 Std. on it.

We follow the guide step by step. Everything was going normal until we started to restore the vCenter Server configuration and Install vCenter Server on the new Machine.

This is our restore log:

[02-23-2011 11:21:11:21S ''  INFO]  [restore]  Starting vSphere 4.1 migration installer script...
[02-23-2011 11:21:11:21S ''  INFO]  [restore]  Checking prerequisites...
[02-23-2011 11:21:11:21S ''  INFO]  [restore]    Migration data directory: C:\vcenterUpg\datamigration\data
[02-23-2011 11:21:11:21S ''  INFO]  [restore]  Checking vCenter Server migration data...
[02-23-2011 11:21:19:21S ''  INFO]  [restore]  vCenter Server DB migration data present: choose installer bundled DB for restore
[02-23-2011 11:24:27:24S ''  INFO]  [restore]  vCenter Server install media found
[02-23-2011 11:24:27:24S ''  INFO]  [restore]    vCenter Server migration data successfully verified
[02-23-2011 11:24:27:24S ''  INFO]  [restore]  Checking VMware vCenter Update Manager migration data...
[02-23-2011 11:24:27:24S ''  WARNING]  [restore]  VMware vCenter Update Manager migration configuration data is missing.
[02-23-2011 11:24:27:24S ''  WARNING]  [restore]    VMware Update Manager backup data or system does not meet prerequisite
[02-23-2011 11:24:27:24S ''  INFO]  [restore]  Checking vCenter Orchestrator prerequisites...
[02-23-2011 11:24:27:24S ''  DEBUG]  [restore]  Checking vCenter Orchestrator version and install path...
[02-23-2011 11:24:27:24S ''  DEBUG]  [restore]  vCenter Orchestrator is not installed or the InstallAnywhere registry cannot be found
[02-23-2011 11:24:27:24S ''  INFO]  [restore]    vCenter Orchestrator migration data successfully verified
[02-23-2011 11:24:27:24S ''  INFO]  [restore]  Installing vCenter...
[02-23-2011 11:24:27:24S ''  INFO]  [restore]  vCenter Server HTTP port: 80
[02-23-2011 11:24:27:24S ''  INFO]  [restore]  vCenter Server HTTPS port: 443
[02-23-2011 11:24:27:24S ''  INFO]  [restore]  vCenter Server heartbeat port: 902
[02-23-2011 11:24:27:24S ''  INFO]  [restore]  vCenter Server Tomcat HTTP port: 8080
[02-23-2011 11:24:27:24S ''  INFO]  [restore]  vCenter Server Tomcat HTTPS port: 8443
[02-23-2011 11:24:27:24S ''  INFO]  [restore]  vCenter Server LDAP port: 389
[02-23-2011 11:24:27:24S ''  INFO]  [restore]  vCenter Server LDAP SSL port: 636
[02-23-2011 11:24:27:24S ''  INFO]  [restore]  vCenter Server DB Server type: Bundled
[02-23-2011 11:24:27:24S ''  INFO]  [restore]  vCenter Server License path: 27000@localhost
[02-23-2011 11:24:27:24S ''  INFO]  [restore]  vCenter Server License edition: vc
[02-23-2011 11:24:27:24S ''  INFO]  [restore]  Launching installer with backed up install data configuration
[02-23-2011 11:37:06:37S ''  INFO]  [restore]  vCenter Server DB type: bundled
[02-23-2011 11:37:06:37S ''  INFO]  [restore]  Checking vCenter Server database...
[02-23-2011 11:37:06:37S ''  INFO]  [restore]  vCenter Server DB instance:
[02-23-2011 11:37:06:37S ''  ERROR]  [restore]  Error: unsupported operand type(s) for +: 'NoneType' and 'str'
[02-23-2011 11:37:06:37S ''  ERROR]  [restore]  Exiting...
0 Kudos
5 Replies

I have the same issue, any resolution?

Thank you

0 Kudos

You said you reinstalled Windows Server 2008 and SQL 2008 and then trying to restore data. What were you SQL version earlier?

0 Kudos

I want to go from SQL Express(Local instance) to a dedicated SQL 2005 (remote instance)  Is this possible with the migration tool?

0 Kudos

We are trying to upgrade SQL from SQL Express.

My  colleagues think that the problem you've described is due to the  different server name and IP address, but we dropped from subsequent  tests.
Actually we have already updated by simply re-install everything. This cluster is only 6 hosts and 30 virtual servers.
This is a major upgrade - from 32bit to 64bit and I think this is the right way if the cluster is not very large.
Unfortunately, in this way downtime of 10 minutes for each server.

0 Kudos

to be honest, In a small environment like that . . .and with the thoughts of upgrading 32bit to 64 bit, I'd build it from scratch.

there are various scripts available for capturing your VC envirinment (folders / resource groups / permissions etc) - so you'll be able to do it with only a loss of historical data.

Simple process for the VC.

Build new VC

Copy Clusters / Folders / Permissions etc

Disconnect ESX hosts from old VC

join to new VC

No need to shut down VMs etc, as these will continue to run even when disconnecting from the VC.

remeber to make sure DNS etc is OK everywhere.

Also, remember that your DSN (in ODBC config) will be visible only in the relevant versions of the ODBC tool (32 DSNs only show in the 32 bit tool . . 64 bit in the 64 bit tool)

good luck

One day I will virtualise myself . . .
0 Kudos