Restore Windows vCenter Server with existing Virtual Distributed Switch

-

Recently, assisted one of my customer to troubleshoot a failed Windows vCenter Server resulted from an upgrade failure.

What you would need is all the credential accounts such as vCenter SSO, Windows Administrator and your MS SQL account. Also a copy of your existing vCenter Server database.

We logged a case with VMware support and gone through the logs. Refer to the logs location here. The one major log would be the vmdird.log. This was showing error 49. The VMware Service Lifecycle Manager service remain freeze at Starting status. This will run a vmon process in your task manager. Check out the all services name here. For those not aware, starting from vCenter Server 6.5, the vCenter Server Services are no longer a standalone services.

We spend a lot of time trying to reinstall, and running through kb fixes but it did not help. We decided to do a uninstall and encounter error 1603. We were not able to get over this error.

 Instead, we did another vCenter Server installation on another clean Windows Server virtual machine and configure the ODBC (version 10 or 11 you got to test this out depending on the version of MS SQL) before running the installation.

Once installation was completed, the vCenter Server was up and running using the existing database.

 

 

We get to see all the ESXi hosts showing in disconnected state. 

 When you try Connect the host,

 

You will get the below warning message.

This is because the original vCenter Server and the new vCenter Server are not same machine. To work around this, we have to make some changes.

Let refer to this KB. By SSH to each host and browsing to /etc/vmware/vpxa/ we need to edit the vCenter Server IP in vpxa.cfg.

Look for ServerIp and edit the IP address to the same as your current vCenter Server.

 

 

Once that is done, you will need to restart the management services. This will not affect any virtual machines running on the host. This will just update the ESXi host services to reflect the new vCenter Server which is managing it. Just type services.sh restart and wait for it to complete.

Once that is done, you can reconnect without any of that warning message. You will also be able to manage back the VDS.

If you are still running a Windows vCenter Server, I would strongly encourage you to plan a time to migrate to a vCenter Server Appliance (VCSA). It is much robust and less inherit of any Windows related issues you will encounter.


Source: All screenshot were taken using VMware HOLs. Register for an account and learn VMware solutions from VMware HOLs.

Comments

Post a Comment

Popular posts from this blog

Why VMware or Why Not after Broadcom?

-
The Truth Yes, the news of VMware acquired by Broadcom has come to a realization. We cannot denied the truth since 22nd Nov 2023. Prior the acquisition, if you have made a multi-year purchase before that, you will have whatever you can consume after the acquisition. VMware after the acquisition has release new bundle of all their offerings and end the perpetual licensing offer to the market. The individual products are not make available and cannot be purchase as a standalone. But are offered via two bundle namely; VMware vSphere Foundation (VVF), VMware Cloud Foundation (VCF). Both of which are all subscription licenses. It also ends all sales and renewal of any perpetual licenses. Honestly, VMware has been trying to end its perpetual license and into subscription for the longest time. With the Broadcom acquisition, VMware has been one of the last major player that has moved to subscription license. Customer who are on VMware, has been enjoying the great pricing with no limit of cores
Read more

VMware by Broadcom, A New Chapter Forward

-
With Broadcom acquisition of VMware completing in 22nd Nov, there have been lots of assumption made by many sources what will become of the business direction. Here are some of the updates that are publicly announced if you have not catch up on the news. To start with, VMware is now known as VMware by Broadcom and all originally VMware software will remain to be branded under VMware. The first announcement 27th November, Carbon Black is  now  an autonomous unit within Broadcom. In my opinion this is good news. I have seen not much integration on Carbon Black ever since acquired by VMware so with that move, it allows Carbon Black to innovate and do what they do best in Cyber security landscape. Next from the acquisition completion, there are many speculation on after the acquisition what will end up of End User Computing? With the  announcement  on 8th December, The End User Computing (EUC) division will be a diverse business. With that understanding, EUC division will operate on their
Read more

VMware vExpert 2024 Application is Now Open!

-
I believe many would have wonder if the vExpert Program will continue since VMware has been acquired by Broadcom recently. I am glad to announce that Corey Romero the program manager for VMware vExpert is continuing the support for the program and this is also Broadcom is supportive of it community recognition. Just for information, VMware User Group is here to stay! For those who are not aware, the VMware vExpert 2024 application is now open. You can follow the post here . There are calls and multiple resources to help you out with your applications and explanation to the different path. Do take note you can fill in the form and save it and submit before 15 Dec 2023 closing date. So take your time to collect your thoughts on your contribution to the VMware community. There is no rush to fill it up at one go. If you need any advice or help, and need to talk to someone, go to the vExpert Pro directory and find someone near you. I am honoured to be part of this directory. Personally I
Read more