VMWare vCenter Server Upgrade from 4.0.1 to 4.1.0

Hi All,

I am in the process of trying to migrate a VMWare vCenter Server 4.0.1 on a Windows 2003 32bit server to VMWare vCenter Server 4.1.0 on a Windows 2008 R2 64bit Server.

I have used the Data Migration tool.

The steps I have performed are:

Stopped VMware VirtualCenter Server and VMware Virtual Center Mnagement WebServices Services
Extracted the datamigration.zip
Run the backup.bat (which passed all tests and appeared to be successfull)
Copied the datamigration folder to the new server and run install.bat

The VMware vCenter Server install Completes along with the SQL Express Installation.  Once I click finish and the install.bat continues with the following errors.


[06-01-2011 13:44:59:44S ''  INFO]  [restore]  Backup of existing VMware vCenter Server DB succeeded
[06-01-2011 13:44:59:44S ''  INFO]  [restore]  Restoring DB...  Please do not stop this program.
[06-01-2011 13:44:59:44S ''  INFO]  [restore]  DB log: Msg 8114, Level 16, State 1, Server TEWK-VMWAREVC02\SQLEXP_VIM, Line 1

Error converting data type bigint to int.

Msg 3013, Level 16, State 1, Server TEWK-VMWAREVC02\SQLEXP_VIM, Line 1

RESTORE FILELIST is terminating abnormally.


[06-01-2011 13:44:59:44S ''  INFO]  [restore]  Some exception occurred during restoring from backup.Restoring the Original DB
[06-01-2011 13:45:01:45S ''  INFO]  [restore]  DB log: Processed 416 pages for database 'VIM_VCDB', file 'VIM_VCDB_dat' on file 1.

Processed 2 pages for database 'VIM_VCDB', file 'VIM_VCDB_log' on file 1.

RESTORE DATABASE successfully processed 418 pages in 0.415 seconds (8.233 MB/sec).


[06-01-2011 13:45:01:45S ''  INFO]  [restore]  VMware vCenter Server DB Restoring to original DB succeeded
[06-01-2011 13:45:01:45S ''  INFO]  [restore]  Restoring LDAP information...
[06-01-2011 13:45:01:45S ''  INFO]  [restore]  Removing existing LDAP instance commandline is: "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\jointool.bat"   remove --statusFile "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\status.txt"
[06-01-2011 13:45:06:45S ''  INFO]  [restore]  Restoring LDAP from database commandline is: "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\jointool.bat"   recover --statusFile "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\status.txt" --name TEWK-VMWAREVC02.tewknet.local --ldapPort 389 --dsn "VMware VirtualCenter"  --vimURL https://TEWK-VMWAREVC02.tewknet.local:443/sdk --webServiceURL https://TEWK-VMWAREVC02.tewknet.local:8443/vws
[06-01-2011 13:45:07:45S ''  INFO]  [restore]  

   vCenter Server LDAP recovery operation failed. Fix the errors in C:\Program Files\VMware\Infrastructure\VirtualCenter Server\status.txt and then execute C:\Downloads\VMware-VIMSetup-all-4.1.0-345042\datamigration\datamigration\data\vc\recover.bat in order to restore LDAP from database


[06-01-2011 13:45:07:45S ''  ERROR]  [restore]  Error: vCenter Server LDAP recovery operation failed
[06-01-2011 13:45:07:45S ''  ERROR]  [restore]  Exiting...

Open in new window

LVL 74
Glen KnightAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization ConsultantCommented:
Hi demazter, that's an Expert I recognize, what version of VMWare vCenter Server 4.0.1 are you running, is it Update 2?

Do we have any entries in the Data Migration Tool logs (restore.log) ?
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization ConsultantCommented:
also what does this file C:\Program Files\VMware\Infrastructure\VirtualCenter Server\status.txt state?
Glen KnightAuthor Commented:
hey hanccocka, yes, you don't normally find me on this side of the fence :)

Those entries in the code box from the question are from the restore.log file, the only other non sucessful entry is:

[06-01-2011 13:33:12:33S ''  WARNING]  [restore]  Patch store data is missing.

The original version is VMWare 4.0.0.10021

In the status.txt I have the following:

 
-----------------
Operation "Recover" failed: 
Action: Recover LDAP instance
Action: Get Recovery info from DB
Problem: No records in the database for recovery policy : "MOST_RECENT"


-----------------
Recovering from failed Operation "Recover"

-----------------
Recovery successful

-----------------
Execution error.

Open in new window

Ensure Business Longevity with As-A-Service

Using the as-a-service approach for your business model allows you to grow your revenue stream with new practice areas, without forcing you to part ways with existing clients just because they don’t fit the mold of your new service offerings.

Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization ConsultantCommented:
To be honest, I've not seen many upgrades succeed with the Data Migration scripts from early versions of vCenter 4.0. I know this doesn't help your current situation or question.

There are two areas of the script which are failing.

The other Experts may have seen this issue.
Danny McDanielClinical Systems AnalystCommented:
the new server isn't running as a domain controller, is it?
Glen KnightAuthor Commented:
OK, next question then, if it's possibly caused by the early versions of 4.0. then what do I need to upgrade it to to allow a successful migration?

I don't seem to be able to find any downloads for vCenter Server 4.0. other than for 4.1
Glen KnightAuthor Commented:
>>>>the new server isn't running as a domain controller, is it?

ABSOLUTELY NOT!

Domain Controllers are domain controllers, even in my lab they do no other task other than be Domain Controllers and DNS servers.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization ConsultantCommented:
Do you want to keep the existing database? (history, summary and statistics).

How's you SQL?

We normally, copy the database to new server, add database, (because the script is umm, troublesome) Re-mount the databases, re-create the DSNs and let VC 4.1 Upgrade the databases.
Glen KnightAuthor Commented:
I can do basic SQL stuff, detach and re-attach, create, dismount, backup restore databases etc.

However, I did try this and once the restore was completed the VMware Server service wouldn't start, perhaps I did something wrong.

The only thing I am really interested in is all the networking and the configuration, which is why I ideally want to keep the same database (unless I don't need the database for this?)

Any ideas how I can make the 32bit version up to date? I only seem to be able to download 4.1.  Will updating it help me?  Obviously in an ideal world I would just unstall 4.0.0.1 on the new server then do an inplace upgrade :(
Danny McDanielClinical Systems AnalystCommented:
I was thinking the same, hanccocka.  these ldap upgrade errors are really troublesome.

I was wondering if script left the copied database intact so that all you would have to do is install, point it to the db that it left sitting there, then enter your license info.
Glen KnightAuthor Commented:
>>>I was wondering if script left the copied database intact so that all you would have to do is install, point it to the db that it left sitting there, then enter your license info.

Explain?
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization ConsultantCommented:
ESX host Networking is stored in the configuration of the servers, no the db. (not doing Nexus or Disgtributed Switches?)

db stores, history, VC layout, template Customizations.

let me find the upgrade links.
Glen KnightAuthor Commented:
>>(not doing Nexus or Disgtributed Switches?)

No distributed switches and I am guessing because I don't know what a nexus switch is that this is a no too.

what about iSCSI targets, etc? is that stored on the host itself?
Danny McDanielClinical Systems AnalystCommented:
if you look and see that sql express is still installed and that there is a vim_something.mdb in the data folder, then it installed sql express and migrated the data.  next check to see if the system DSN's are there, if so now all you have to do is run the setup.exe from the 4.1 install media.  

the install will ask if you have an existing db, then you select the DSN and hit next.  
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization ConsultantCommented:
(if you are going to go to the trouble of Updating).

With your Advanced SQL Skills (he he :-) ). You could try the copy, move, detach, attach, create new DSNs, and let VC 4.1 attach to new db, and Update the db on new server. That's how we do it "professionally" (left it quotes!), because script can be pants!

VMware vCenter Server 4.0 Update 3 and modules
http://downloads.vmware.com/d/details/vc40u3/ZHcqYnR3ZWpiZGgqag==

VMware vCenter Update Manager 4 Update 1 Patch 2
http://downloads.vmware.com/d/details/vum40u1p2/ZHcqYmRwaCViZGUlaA==

You'll need to login with your VMware Id.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Glen KnightAuthor Commented:
Thanks, :)

Can you give me a step-by-step for "You could try the copy, move, detach, attach, create new DSNs, and let VC 4.1 attach to new db, and Update the db on new server."

I will do the update as well :)
Glen KnightAuthor Commented:
Right.....

database detached and re-attached to new server.

Do I need to uninstall the failed VMWare Server install or can I just re-install? Anything else I need to do before I do this?
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization ConsultantCommented:
Un-install the failed server attempt, and start again.

When installing, then select the DSN which points to your "migrated" database, it should ask to Upgrade/Update, and select Yes.
Glen KnightAuthor Commented:
OK, it says it's upgrading......watch this space :)
Glen KnightAuthor Commented:
Nice one hanccocka, nice easy solution, just the way I like them.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization ConsultantCommented:
Glad it worked for you, it's the easiest way, I've no idea, why VMware created a script, that doesn't work 100% of the time. I guess for the Admins, that don't know SQL.

Any thanks for the feedback, I've got an Exchange question for you, I'll maybe post sometime, small bug, had it for years!!
Glen KnightAuthor Commented:
Now Exchange, I can do!! :-)

Watch out for some more VMWare questions tomorrow :-)
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.