Quantcast
Channel: VMware Communities : All Content - All Communities
Viewing all articles
Browse latest Browse all 175326

Upgrading vCenter Server 5.1 to vCenter Server 5.1 Update 1 when SQL Database is Remote and vCenter Server Heartbeat is Installed

$
0
0

Hi Guys,

 

I am in the middle of an upgrade of vSphere 5.1 to vSphere 5.1 Update 1. I have vCenter protected by HB and SQL on a separate machine (also protected by HB) I am also running Syslog, Update manager and Authentication Proxy on vCenter.

 

I have successfully upgraded HB on all 4 nodes (2 x vCenter & 2 x SQL) and started the upgrade of vCenter and components on the secondary server as per •vCenter Server Heartbeat 6.5 Update 1 Installation on Windows Server 2008 When the Secondary Server is Virtual (PDF)  http://www.vmware.com/pdf/vcenter-server-heartbeat-65-u1-installation-windows-2008-virtual-guide.pdf

 

 

I have got to step 3.c

3 Change the server role to Primary/active:

a Launch the vCenter Server Heartbeat Configure Server wizard and click the Machine tab. Change the server role for the current (Primary) server to Active and click Finish.

b Using the Service Control Manager, start the VMware vCenter Server Heartbeat service.

c Using the vCenter Server Heartbeat Console, verify that all status icons on the Server: Summary page are green indicating that the Start process has completed and all protected services are started.

d Using the Service Control Manager, stop the VMware vCenter Server Heartbeat service.

 

As the vCenter service does not start I am stuck at this point. As far as I am concerned the error is perfectly logical. I have updated vCenter using the secondary server and then I am trying to connect (as per guide) with another version which fails.

 

If I continue with the services stop and launch  the SSO installer it tries to perform an uninstall!

 

Am I missing something in this upgrade?

 

Regards


Ciaran


Viewing all articles
Browse latest Browse all 175326

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>