Solved

HA(High Availabilty) and Vcenter server Reboot.

Posted on 2013-11-07
4
4,590 Views
Last Modified: 2013-11-07
HA(High Availabilty) and Vcenter server Reboot.

I believe rebooting Vcenter server(Windows OS), would not have any impact on the VMs and ESX hosts.
in the article posted on this link,:
http://searchitchannel.techtarget.com/feature/Enabling-VMware-HA-DRS-Advanced-vSphere-features


 they talk about HA and they quote "In fact, if the vCenter Server goes down, HA clusters can still restart VMs on other hosts; however, information regarding availability of extra resources will be based on the state of the cluster before the vCenter Server went down."

I do not know what they mean. will the VMs be rebooted or they mean moved( when they say Restarted on the other host) ?

Any idea?

Thanks
0
Comment
Question by:jskfan
  • 2
  • 2
4 Comments
 
LVL 119
ID: 39630967
I do not know what they mean. will the VMs be rebooted or they mean moved( when they say Restarted on the other host) ?

This is correct, because VMware vCenter Server ONLY configures VMware HA, VMware HA is controlled by Agents which are installed on the ESXi hosts, and perform Master and Slave elections, it's the Master and Slave Agents which perform VMware HA.

The HA Agents on the hosts...

vSphere HA State - Master - A server which is elected as the master. This agent monitors the VMs on this server, and other operational Hosts, and it WILL attempt to restart VMs on failure.

vSphere HA State - Slave - This server is connected to the Master Agent, via the Management Network. The vSphere HA Protected VMs on this server are monitored by one or more vSphere HA Master Agents, and the agent will attempt to restart VMs after a failure.

vSphere HA Protected VM - vSphere will attempt to restart the VM after a supported failure of the VM.

VM is HA Protected on the following conditions:-

VM is in a vSphere HA enabled cluster.
VM is powered on successfully after a successful user power on.
vSphere HA has recorded that the power state is ON.

When an ESXi Host Server Fails (which is part of a VMware HA Cluster), all the Virtual Machines, which are hosted on that Host, also go down, e.g. fail.

A Host Failure could be:-

1. Pink/Purple Screen of Death - caused by memory fault.
2. Pink/Purple Screen of Death  - cause by cpu fault.
3. Power supply failure (if only a single power supply)

A Host Manual Shutdown, reboot, restart is not considered a host failure. Because it's a controlled shutdown.

So we have a Host which has failed, and ALL the VMs it was hosting are now DOWN!


When a host server fails, all the VMs which are on that host server will also FAIL. So a Host fails, all the VMs would go OFF (crash!). They cannot be Live Migrated or vMotiond or MOVED in advance, because how would the server know it's going to fail - it cannot!

So VMware HA, issues a restart of failed VMs, on the remaining hosts!

So, yes, the VMs are restarted, and yes the VMs are moved, because the host they were running on has failed, and no longer available in the cluster.

VMs running on new hosts, BUT they are not MOVED LIVE!!!! No vMotion! They do not really move anywhere, VMs are stored on shared storage, they do not move, but the process is executed on a different host!

So it depends on how you regard "move". They have moved, because they could of been on Host A, and now they are on Host B or Host C, or Host D but also Host A has gone! So they could no longer be running on Host A.

So, expect VMs to be restarted within 1-2minutes of a host failure.

If you are a VMware Admin, I would recommend Duncan's Books on Clustering here

vSphere 5.1 Clustering Deepdive

Any questions?
0
 

Author Comment

by:jskfan
ID: 39631106
hanccocka:

My concern was about the Vcenter.
I have restarted the Vcenter server, and in our Cluster HA and DRS are enabled.
I want just to make sure that when restarting Vcenter server , the VMs will not restart in other host as the article described it (unless if I misunderstood the article).

For the Failure of the host , I amaware of that,  HA will reboot the VMs in the other host within the cluster.

**Recently I put ESX host in maintenance mode, some VMs moved automatically and some did not move at all. I had to move them manually. Some VMs were turned off and as you mentioned in a different post "make sure  CD/DVD drive:1 not connected "  , I saw the VMs that were turned off showing  "Connected to ISO image on local disk".

So , I had to shut down the host with the VMs that were turned off still displayed under the host.
0
 
LVL 119

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points
ID: 39631433
Restarting vCenter server, is safe.

Host failure, causes VMs to restart, not vCenter Server.

If cdroms/floppy drives are connected this is to be expected, as you have found, learn good VMware Administrator practices, and remove floppy and cdroms before putting a server into Maintenence Mode.

There is another option, which states Moves VM that are turned off, tick box, when you issue an Enter Maintenance Mode.
0
 

Author Closing Comment

by:jskfan
ID: 39632062
Excellent hanccocka !!!
0

Featured Post

Create the perfect environment for any meeting

You might have a modern environment with all sorts of high-tech equipment, but what makes it worthwhile is how you seamlessly bring together the presentation with audio, video and lighting. The ATEN Control System provides integrated control and system automation.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
NAS Solution for VMware ESXi 2 80
Remote access to ESXi 6 free with USB modem 5 55
HOw To Install Docker on VMware Workstation 19 182
Internal CA server 6 50
This article will show you how to create an ISO CD-ROM/DVD-ROM image (*.iso), and MD5 checksum signature, for use with VMware vSphere Hypervisor 6.5 (ESXi 6.5). It's a good idea to compare checksums, because many installations fail because of a corr…
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to install vSphere Update Manager  Console to Windows system:  Install vSphere Update Manager: Configure vSphere Update Manager plug-in in vSphere Client: Verify vSphere Update Manager settings in vSphere Client:
Teach the user how to install log collectors and how to configure ESXi 5.5 for remote logging Open console session and mount vCenter Server installer: Install vSphere Core Dump Collector: Install vSphere Syslog Collector: Open vSphere Client: Config…

821 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question