Potential Problem with ESX 3.0.x and VirtualCenter 2.5
We are still running ESX 3.0.x and VC 2.0.x. I thought about upgrading vcenter first and then just upgrading the servers has time permits. But if there’s going to be odd issues like this, even if its only when you install some patches. I think I’ll try to put together a much shorter timeline to move to 3.5
Heads up—I’ve been alerted to a potential problem when using ESX Server 3.0.x with VirtualCenter 2.5. Quoting from this VMware KB article:
ESX Server 3.0.x hosts managed by VirtualCenter 2.5 must have their Host Agent (hostd) specially configured to work with VirtualCenter 2.5. This configuration is done automatically during the initial installation of the VirtualCenter Agent (vpxa). If an ESX Server patch is subsequently applied that includes the esx-hostd RPM package, like ESX Server patch 1002435, the patch replaces the existing Host Agent (hostd) configuration file (/etc/vmware/hostd/config.xml) and undoes vpxa’s changes. This reverting of the Host Agent configuration file breaks connectivity with VirtualCenter 2.5.
Popularity: 4% [?]
Tags: AD, blog, esx, IE, IM, IT, lan, search, servers, site, storage, tags, vcenter, vmware, workRelated posts
April 5, 2008 No Comments
VirtualCenter 2.5 upgrade issue with SQL 2000
I allows find it good to wait at least a few weeks before I do any major upgrades. I’ll let other people shake out the bugs. Its a good thing because we are running our vcenter on SQL 2000. Follow the link for the fix before you try the upgrade or if you already tried and failed. Big note from the KB, if you don’t follow the steps in the KB, it will over write your database, you do backup your database before you do any upgrade, right?
I’ve not yet got my hands really dirty on ESX 3.0.x to ESX 3.5 and VirtualCenter 2.0.x to 2.5 upgrades. Although crudely “play” with the process under the Release Candate. Initially, I had a permissions problem with the VirtualCenter upgrade and my SQL 2000 server. There’s been a length forum thread on this which I have been involved with. It’s become clear that if you have a SQL 2000 server additional permissions are required for an upgrade, which were not previously required in previous upgrades from VC 1>2 or the intra-upgrades from say 2.0.0>2.0.1>2.0.2
A KB article from VMware outlines this issue. As far as I know its not an issue for SQL 2005…
Link: ID: 1003346
VirtualCenter 2.5 upgrade issue with SQL 2000
mikelaverick
Tue, 18 Dec 2007 22:09:15 GMT
Popularity: 5% [?]
Tags: database, sql, upgrade, vcenter, vmwareRelated posts
December 26, 2007 1 Comment
Twitter Updates for 2007-07-15
- another long night on our mantanance weekend
# - Trying to move SQL from Vmware 2 to VI3, can’t use vcenter because its database is on that sql server. #
- sitting on a boat in spring lake #
Powered by Twitter Tools.
Popularity: 3% [?]
Tags: database, IT, RDP, sql, twitter, twitter tools, updates, vcenter, vmware, word, WordPressRelated posts
July 15, 2007 No Comments
Busy week, not many posts
Let’s see Monday started by having the drive our exchange logs on fill up. Yeah….who would have thought we could have 3GB of changes to the database over a weekend…..exeutil is your friend…
The rest of the week, we’ve had an onsite vmware workshop. We installed 3 Dell blades with ESX onto our SAN and we now have VCenter and Vmotion. This stuff ROCKS!!! VCenter is SO MUCH better than the MUI you get when you only have ESX. The workshop runs one more day. Only a few more things to clear up and then it’s time to move about 15 machines to the new virtual server farm.
This Saturday we have family coming for a Christmas party and if the weather is good enough we are heading to Detroit Sunday for the Lions game. You can’t beat free tickets!!!!
later,jb
Popularity: 2% [?]
Tags: AD, database, dell, esx, exchange, free, IE, IM, IT, lions, mac, site, vcenter, vmotion, vmware, workRelated posts
December 14, 2005 No Comments
