vCenter Server linked Mode. Error 28039. Setup cannot join vCenter Server to the linked mode group

vSphere Virtual Center Linked Mode Prerequisites:

Well, yes this article has two headers or titles. Guess what they are almost identical.

I have seen “Error 28039. Setup cannot join vCenter Server to the linked mode group” all over the net & without any one posting resolution for it. hmmmm, how did I find out about this error and what made me looking for resolutions, well I had faced this same ugly error in my own lab. The resolution for it was nothing more than following the pre-requisite to vSphere Virtual Center Linked Mode which most people ignore. Below is the pre-requisite that you must follow for a successful installation of vCenter Linked mode & I will highligh the mostly missed one.
All the requirements for standalone vCenter Server systems apply to Linked Mode systems. In addition, to the following requirements:

The following requirements apply to each vCenter Server system that is a member of a Linked Mode group:

  1. DNS must be operational for Linked Mode replication to work.
  2. The vCenter Server instances in a Linked Mode group can be in different domains if the domains have a two-way trust relationship. Each domain must trust the other domains on which vCenter Server instances are installed.
Read More

VMware ESX & Virtual Center 3.5 upgrade guide

It might be the time for you to upgrade your VMware ESX servers to VMware 3.5U3 and Virtual Center 3.5U4.

You might even just want to upgrade to any version of VMware ESX & vCenter 3.5. Then this guide linked to below is all you need. It has a great step by step instruction of the process & better its provided by the solution Vendor VMWare :).

VMware ESX & Virtual Center Upgrade guideRead More

VMworld 2009 announce vSphere, vCenter Server Heartbeat, VMware vShield Zones

VMworld Europe 2009. VMware has used the VMworld Europe 2009 to announce two new products that will be available this year:

1- vCenter Server Heartbeat:

Comes to solve the problem arising from a possible collapse of the server that manages the VMware virtualized platforum, specifically vCenter Server earlier known by Virtual Center. The vCenter Server Heartbeat comes to provide High availability for the vCenter. Prior to vCenter Server Heartbeat you were only able to have one vCenter to manage your infrastructure if that vCenter fail VMware’s Live migration with VMotion, load balancing with Distributed Resource Scheduler (DRS), license management, and performance monitoring all cease to function.

Architecturally, Server Heartbeat is implemented as an active/passive vCenter servers, running on physical or virtual machines. In addition to server and network hardware, Server Heartbeat monitors the actual vCenter instance, its back-end database, and the underlying operating system. In the case of failure, the passive node takes over, and Heartbeat restarts the vCenter service. Failover can occur over both LANs and WANs.

I can sense some people already arguing that you could achieved the same result of vCenter heartbeat Server by running vCenter inside a virtual machine & VMware HA. If you had implemented that then you will notice three big limitations with that:

a- As HA is only supported in a single site then that redundancy for vCenter was only valid for a single site & you were not able to use it for DR.… Read More