VMware Cloud Community
ralphh936
Contributor
Contributor
Jump to solution

SQL database issue with moving from VC 2.0 to 2.5

we've bought new hardware to host a new VirtualCenter app and I can't seem to find in KB or upgrade notes is about the remote SQL database upgrading or moving,

We're currently on VC 2.0.1 on older hardware. I want to build VC 2.5 on the new hardware but how do upgrade the remote SQL database...

So the Questions are:

Can we install VC 2.5 on the new hardware, and tell the install to connect to the remote SQL db and the install will upgrade the DB in place (the new hardware would have a different DNS/Nebios server name then the old VC)?

or do we have to just build a new DB and if so, is there a VMware import or move tool to pull the info from the old db to the new db?

Reply
0 Kudos
1 Solution

Accepted Solutions
scerazy
Enthusiast
Enthusiast
Jump to solution

Stop VC 2.x service, so it does not write any more to the existing DB, install VC 2.5 on new harware & when asked for the DB just poin it to your existing DB (you will have an option to adjust the DNS name there & then)

All that is to it

Seb

View solution in original post

Reply
0 Kudos
3 Replies
scerazy
Enthusiast
Enthusiast
Jump to solution

Stop VC 2.x service, so it does not write any more to the existing DB, install VC 2.5 on new harware & when asked for the DB just poin it to your existing DB (you will have an option to adjust the DNS name there & then)

All that is to it

Seb

Reply
0 Kudos
HyperSprite
Enthusiast
Enthusiast
Jump to solution

Before you start, read all of the kbs listed in the release notes under known issues, all the gotchas are in there.

If you have a lot of Host servers, the easiest way would be to move the IP to the new VC box.

Shut down the old VC server service and do a backup of your DB.

Backup the SSL directory at c:\documents and settings\all users\application data\vmware\vmware virtualcenter\ssl

On the new server setup your system dsn to point to your DB (this is different depending on sql 2000 or 2005)

Install 2.5 on your new server, (if you get to the licensing screen and it has a checkbox for evaluation, your DB is not being recognized correctly for upgrade, hit the back button and check your dsn and db permissions until this disappears).

Restore your ssl files to the same location on the new VC server.

Start your VC server service.

Reply
0 Kudos
scerazy
Enthusiast
Enthusiast
Jump to solution

"move the IP to the new VC box"

It might make things easier, but not absolutely crucial (VC is refernced by DNS, unless one input the IP in ESX host file as per recommendations)

Other than that the IP of VC itself is not that important

SSL certificate can be re-created easily

Seb

Reply
0 Kudos