HA restart priority

Similar Questions

• Why a framework for vm cluster restart priority? and what is happening with the explanation of availability guide

  1.

  I can see why "by vm" restart priorities are to a parameter value. For example you can prioritize machine virtual startup order relative to other virtual machines so that you get your first AD and DNS servers etc.

  But what's the point of a cluster environment?  I guess this means how you want to fight your guests stay for these virtual machines running. for example you 32 at a time (maybe high definition), or start to 1 at a time (maybe low setting)

  Which brings me to the point 2

  2.

  It seems that availability guide is a bit confused about this subject and talks about specific vm priorities when he must speak of cluster priorities. So really, she explains vm priorities both times and explains any of cluster priorities.

  If you go to (vSphere availability Guide: creating and using VMware HA Clusters: creating a Cluster VMware HA: Virtual Machine Options: vm restart priority settings)

  He mentions first boot vm priority talks about startup relative , I deduce that it means her talk of priorities to restart each of the virtual machines in the virtual machine settings and not a cluster configuration.

  Then he said: ' the values for this parameter are: off, low, medium (default) and high "- but these are the settings for the cluster priority! If she was talking about relative vm settings, he'd say ' off, low, medium, high and use of the cluster (default) settings.

  It says so at the bottom of the page

  "Note - after you create a VMware HA cluster, you can override the default settings of cluster to restart priority and isolation response specific virtual machines..." »

  It's weird since the section above already speaks on startup for specific virtual machines

  The clustering is where you set the 'default' value essentially for virtual machines. After that, you must change this setting on a per-VM basis, as appropriate. Availability guide is indeed vague on this subject, and I would point out to our team of Tech-Pubs.

  Duncan

  Yellow - bricks.com | HA/DRS technical deepdive - the ebook

• DRS does not

  New installation of 5.5U1

  Licensing Enterprise permanent Plus - 2 CPU for each host - 3 guests

  Created under the cluster data center icon

  Active DRS

  • the fully automated, aggressive value
  • Select the unverified levels of individual virtual machine automation

  HA on

  • Home monitoring checked
  • VM restart Priority Medium
  • The host isolation response - leave it on
  • Admission Control NOT active
  • VM & App monitoring high sensitivity
  • Data store Heartbreaking - use of the warehouses of the specified list and automatically if necessary complement

  Turn off the management-

  Advanced options - not defined

  HA works as expected

  vMotion performs as expected, triggered manually

  8 VMs on host 1

  1 VMS on host 2

  0 VM on the host 3

  vSphere balanced DRS reports

  0 DRS recommendations

  DRS defects 0

  Try to manually start the DRS does not move the virtual machine is as expected

  Stress test VM with a CPU generator does not start a vMotion

  Can anyone suggest where to look for this problem of DRS? Thank you

  Note that there is little change in DRS [email protected]. In my view, the hosts with 8 VM is still not fully charged & DRS think same host is good enough.

  Reference:http://www.slideshare.net/VMworld/vmworld-2013-performance-and-capacity-management-of-drs-clusters

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=2059868

  VMware KB: Change the default behavior of vSphere distributed power management

  Strange activity DRS on ESXi 5.5

• HA and auto start / stop

  for the virtual machines that are part of the HA cluster is still not possible to control the parameters of start/stop automatic start and delay?

  any plans for it in vsphere 6?

  Since the Center of Documentation of vSphere

  If the failure of a host and its virtual machines need to be restarted, you can control the order in which this is done with the restart VM priority setting. You can also configure how vSphere HA responds if hosts and how vSphere HA responds so guests lose connectivity network management with other hosts using the host isolation response parameter.

  These settings apply to all the virtual machines in the cluster in the event of a host failure or isolation. You can also configure exceptions for specific virtual machines. See individual vSphere HA to customize the behavior of a Virtual Machine.

  VM Restart priority

  VM restart priority determines the relative order in which virtual machines are placed on new hosts after a failure of the host. These virtual machines are delivered to market, with the highest priority of the VMS attempted first and continuing those who have priority low until all virtual machines are rebooted, or no resources cluster more isn't available. Note that if vSphere HA fails to power on a virtual machine of high priority, he engages to try any lower priority level of virtual machines. For this reason, the priority of restarting VM cannot be used to assert a priority to restart for a multiple application of the virtual machine. In addition, if the number of host failures exceeds what admission control allows, virtual machines with the priority the lower cannot be restarted until that more resources will be available. Virtual machines are restarted on the hosts of failover, if specified.

  The values for this parameter are: off, low, medium (default), and high. If you select off, vSphere HA is disabled for the virtual machine, which means it is not restarted on other ESXi hosts if a host fails. The disabled parameter is ignored by the vSphere HA VM/Application monitoring function, as this function protects virtual machines against failure at the level of the operating system and not the failures of virtual machine. In case of failure at the level of the operating system, the OS is reset by vSphere HA and the virtual machine is running on the same host. You can change this setting for each of the virtual machines.

  ------

  The thing with VM restart the priority that it is currently the order that the boot of VMS is attempted after an HA event. It is not a guarantee that the virtual machines will start in a particular order. It can work well for your environment. I recommend you to test if you can.

  Here's a post from www.yellow-bricks.com about restart priorities and some of the issues in more detail with them:

  I put priorities of reboot but still my VMs seem to be lit in a different order

  And here is a rough idea of what we're looking to future:

  http://www.yellow-bricks.com/2013/09/13/ha-futures-restart-order/

  I hope this helps.

• PowerCLI script to migrate virtual machines to the new vCenter environment

  Hello world

  in the next few weeks, we need about migrate 700 VMs (Windows/Linux) server to a new environment (new vCenter, new hosts, but VMs will remain on same data warehouses). VMs will be migrated not in one batch, but rather from time to time (which, however, can understand the need to migrate some 10s of virtual machines at the same time).

  Cluster names and folder structure will be identical to the old and the new vCenters. As host in the new vCenter names differ from those in the old vCenter, thought to provide a table of 'translation', which tells the script to save a given VM on host B (new vCenter) when having been registered in order to host a (old vCenter) and so on.

  I thought writing a PowerCLI script which, broadly speaking, can accomplish the following steps:

  • Connect to vCenterOld and vCenterNew
  • Correspondence table of host to read from a file (see step "register VM vCenterNew below)

  Then, in a loop:

  • Ask VM name
  • Get the settings of the virtual machine: Datastore/path, network/Portgroup, HA restart priority, host, folder, note
  • View the parameters and the VM name and request confirmation migrate the virtual machine
  • Turn off VM (closed OS gracefully, but force power off if power status is still not equal 'off' after a time given)
  • To unsubscribe from VM vCenterOld (removal of inventory)
  • Registry of the VM to the data store vCenterNew (assumptions: same folder as vCenterOld, host names are different, but for each source in vCenterOld host a host of destination in vCenterNew for you join the virtual machine to can be provided, that is, CSV)
  • The value of VM portgroup (same name as in vCenterOld)
  • Set VM HA restart priority
  • PowerON VM
  • Wait / check the VM (for example, ping) connectivity / continue immediately if the virtual machine is accessible or after a certain time if the virtual machine is still inaccessible
  • Confirm that the virtual machine has been migrated successfully, OR ask the user to check the connectivity of the virtual machine

  Now to my questions:

  • Is anyone know about an existing script that does something similar or contains parts that can be useful to compile a script like this?
  • How can vCenter two connections at the same time been managed within a PowerCLI script - or doesn't work at all and a connect/disconnect to/from the two vCenters must be completed for each virtual computer?

  Many thanks for any help.

  The following seems to work for me

  $vm = Get-VM -Name MyVM$nic = Get-NetworkAdapter -VM $vm $vdPG = $nic | select -ExpandProperty NetworkName
  
  Get-VDPortgroup -Name $vdPG
  

• Need to move virtual machines and power over the other ESXi HA and issues of Configuration of power

  Dears

  Need to move virtual machines and power on ESXi others using the HA and Power Options

  So what are the Options I need activate and deactivate:

  Turn on Vsphere HA

  Activate the tracking host

  Admission control (disabled)

  VM Machine Options

  VM restart priority (medium)

  Response from the host of off the power isolation

  VM monitoring (people with disabilities)

  Monitoring of (high) sensitivity

  Heartbeat of data store (select one of cluster data warehouses taking into account my preferences) of the data store is checked

  On each:

  Start/stop of the virtual machine is turned off

  Please indicate the required Options and on virtual machines, we are not turning on?

  Just to be clear, that VMware HA will only restart the VMS if ESXi hosts fails - or surveillance of the VM is turned on which will be monitors VMs will they crash or suspend and restart the virtual machine affected.

  and just to be clear, that the response of insulation parameter has nothing to do whther THAT HA will work or not - it does come into play if the ESXi host is isolated of the HA - Cluster

  xMotion works only between active ESXi hosts that can communicate with the server vCenter - and if the ESXi host broke down or became isolated and vMotion may not work.

  vMotion is automated with DRS that vMotion will a VM who need more resources to an ESXi host with enough reosurces.

• delete an of HA virtual machine

  Hello

  How can I make a machine do not participate in HA?  ESXi 5.0, vCenter, cluster with two hosts, blah blah etc running.

  Thank you.

  You mean that you do not want HA restart a virtual machine failure? You can set the "restart priority" this VM to "disabled" in the cluster editing UI.

  Elisha

• VSphere 5.0 agent vm

  Thank you all,

  What is the use of agent 5.0 vm. What is the best practice configuration.

  Thank you

  SIV

  A virtual agent is a virtual machine that performs a specific function for the virtual infrastructure. An example of a VM agent would be for example a vShield device Endpoint is an antivirus solution. By "tagging" this VM as VM agent ensure that this virtual machine gets power first in the event of a host failure. We do this to ensure that the service is available before all other virtual machines.

  It's the current order:

  • Agent of virtual machines
  • Secondary virtual machines of FT
  • Virtual machines configured with a reboot of the top priority,
  • Virtual machines configured with a medium restart priority
  • Restart of Virtual Machines configured with low priority

• Recovery of the cluster VSA problems

  Hello

  A power outage left our vcenter server machine somehow a mess (or at least the DB used by vcenter is)

  So, given my complete lack of knowledge DBA and try to get things back running, I went to control panel and uninstalled) 1 vcenter, 2) unit of vsa, 3) the vcenter client and 4) sqserverl-express from Microsoft of the machine software. I assumed that to uninstall this way, any possible trace of the installation must be deleted or substituted at least when reinstalling. (can someone please confirm/deny this hypothesis, thanks!)

  I continued to reinstall all the software and then tried the recovery procedure 'retrieve an existing Cluster of VSA", as described in the documentation centre 5 vsphere.

  At first glance, this seems to work.

  But now it seems that the recovery has not reproduced the "VSA HA Cluster" self, but simple imported all VM directly under the recreated VSA Datacenter. If I look at the 0 VSA, VSA-1 and VSA-2 VMs now, then the vSphere HA protection seems State "n/a".

  Also two other virtual machines that I had installed under the cluster work but aren't protected HA anymore.

  Trying to create a new cluster fails because my ESX 3 hosts are already known to the system under the data center...

  I did something wrong during the recovery and is it possible to repair the damage, or am I better take a return of my 2 virtual machines (using standalone converter tool?) and simply reinstall my 3 servers ESX and vcenter again, as I described at the beginning of this message?

  Thanks for any help on this.

  Hi David,

  At this point, the best thing to do is probably to create the HA Cluster yourself. The steps are not too complex:

  1. right-click on the domain controller where the hosts/vms resident => New Cluster...

  2. Enter the name

  3. check 'Turn on vSphere HA' (you could also turn on vSphere DRS if you have the useful, likely license)

  4 @ VM Options:

  -Activate the tracking host

  -Enable admission control

  -Set the control strategy for admission to 33 percent of the cluster resounces reserved as space failover capability (50% if you have a 2 cluster nodes)

  -Click next and the VM Restart priority average value and response of isolation to "shut down the computer.

  5 @ VM followed, define "VM Monitoring" to "Followed only VM" and "control of sensitivity to the average value.

  6 @ VMware EVC window, I would say that allows EVC (but this is not necessary). This will ensure that all hosts in your cluster are able to Vmotion. Please, make the selections of approirate (v.s. intel amd and so on) and then proceed.

  7 @ location of VM swap file, please select 'store the swap file in the same directory as the virtual machine (recommended).

  8 @ ready to fill, review your selections and click "Finish".

  9. with the created Cluster HA, just drag and drop your ESXi in the cluster hosts.

  10. go back into the settings of Cluster HA. Right-click on the cluster-online 'change settings '.

  -Under vSphere HA-online virtual Machien Options, please disable VM priority Restart for all virtual machines of VSA

  That's all. You should be all set.

  FYI: @ step 9, if you can't drag and drop your ESXi host, and he complains about your CVS settings, you can go into the HA Cluster settings and change the CVS options as your hosts will be allowed in the cluster.

  I hope that this solves the problem for you. If you have any other questions, feel free to ask.

• VM doesn't have a vmotion after that host was isolated.

  Hello world!

  We have recovered from it, but had to manually!

  One of our hosts running 4.1 became isolated, because vsphere always showed the host, but we could not even place the host mode now as most of the features are grayed out. Host showed as disconnected in vsphere. clicking on CONNECT has not set the it. Reboot the host, the host came back with an error «file missing startup...» ", and we had to use the REPAIR cd to get it restored.

  My question is, why didn't all of vmotion of our VM for the other two hosts when this host became isolated?

  HA is enabled,

  VMware HA is checked to activate the tracking host.

  Admission control is enabled

  Admission control policy is set: chess host tolerates the value: 1

  Virtual Machine options are: cluster parameters: vm restart priority: are AVERAGE and response of isolation the host is set to Power Off.

  Monitoring of the VM is: VM monitoring only and the sensitivity is set to MEDIUM.

  We use Vsphere Essentials Plus 4.1 on 3 HP DL 365 G5 hosts and an EMC Clariion SAN.

  Thank you!

  Peter

  Your DNS server on the host that is down?  I had a simiar situation where both of my primary and secondary DNS servers have been on the host that is down.  vCenter eventially lost communication with guests because he could not resolve names.  Restart the host did not work because they were stopping the process of HA. vCenter could not restart on the other hosts because of the DNS problem.  I had to open a web console on the first host to start the DNS servers manually.

  I now have a rule of DRS Setup so that my DNS servers cannot be on the same host.  I also put the names of all my hosts in the host file on my server vCenter.

• Problemas HA/DRS

  Hola a todos,

  Me gustaria ver if any of los present me stupid I have as you can row a problema HA/DRS

  Explico cual es the situation:

  -3 3.5 ESXServer Servidores con activo HA/DRS.

  -Isolate the answer "Shutdown VM"

  -VM restart priority "Low".

  -Number of failures of the host in the cluster can tolerate '1 '.

  In el mismo tengo una servidores infrastructure + workstations (virtual + VDI servers)

  Servidores en HA tengo 3 "High priority" Servidor DOMINIO + 2 VM VDI, the rest of maquinas office servidores

  Las tengo in priority "low".

  El problema lo tengo hacer al the tests of 0 in el sistema (Corte de LUZ suddenly, Servidores y storage).

  Sin El storage levanta any problema y los servidores ESX lo hacen también, el problema esta en when

  Levanta el primer ESX Server no hace nada con las maquinas are in "Priority" las mueve or las arranca.

  Espera a estar el 2º ESXServer activo para start a levantar Máquinas sin tomar cuenta las d.c.,1999 dadas en HA

  por lo that al final is levantan of VDI sin estar servidores DNS/DHCP/DOMINIO antes las maquinas y rebienta todo.

  Questions:

  -Es posible hacer crear dependencias between maquinas? (Me he remirado the documentation toda y no encuentro training)

  Arum: Hasta that none is levanten las maquinas "VM1, VM2, VM3... no levantar el maquinas restaurant.

  -Exist documents donde alguna to detail todas las HA/DRS advanced options (Las configurable Advanced options...)

  MUCHAS gracias a todos.

  igarcia

  Hola Igarcia,

  No molestas, mas are, all learn of todos. If you have good configurado HA, "lujo" works, decir, para are lo, para protegerte contra fallos hardward y con nueva version vSphere tambien you "protected" contra fallos del OS del MV comments.

  Saludos,

  Jose Maria Gonzalez,

  Founder and president of JmGVirtualConsulting.com

  -

• vCentre Server on a host ESX in HA...

  Hi... I'm still beginner on this platfrm... wanted to know if vCentre Server 4 can be installated practically on a host ESX 4 or not... and if the same ESX host may be part of the band HA.

  In this case, what happens if the HOST fails... will the vCentre also circulate and work normally at different of the box as the other guests or we might face problem...?

  Thanks in advance for the answer...

  UPG

  Hi upg3,

  In terms of HA - even if it is configured by VC - he is actally managed by the animators themselves (it is re-brand aam of legato...), so the guests themselves can manage failover - even in the case of a lost VC.

  Take a look at your environment with cluster parameters. HA VM restarting priority.  You will need to take a look at your environment and train yourself that restart works to order for you, for example in my environment we also have physical DC and DNS, so it is not as important for them to come before VC.   If you have a VM SQL backend for VC - obviously happen before VC itself...  AV and Citrix etc - well, it's up to you!

  While looking to HA - take a look at the affinity setting VM for your DNS and DCs VM servers if you think it is suitable...

  Dan

• Custom view get-inventory returns nothing

  Here is an excerpt of what I'm trying to accomplish (I filter certain fields/results)

  Get-Inventory | %{
       $type = $_.Id
       if($_.Id.Contains("-")) {
            $type =  $type.Substring(0, $type.IndexOf("-"))
       }
  
       switch ($type) {
            "ClusterComputeResource" {
                 select  @{name="[MACHINE_NAME]"; expression={$server}},
                           @{name="[PATH]Id"; expression={$_.Id}},
                           @{name="[PATH]Name"; expression={$_.Name}},
                           @{name="Name"; expression={$_.Name}},
                           @{name="HA Enabled"; expression={$_.HAEnabled}},
                           @{name="HA Admission Control Enabled"; expression={$_.HAAdmissionControlEnabled}},
                           @{name="HA Failover Level"; expression={$_.HAFailoverLevel}},
                           @{name="HA Restart Priority"; expression={$_.HARestartPriority}},
                           @{name="HA Isolation Response"; expression={$_.HAIsolationResponse}},
                           @{name="DRS Enabled"; expression={$_.DrsEnabled}},
                           @{name="DRS Automation Level"; expression={$_.DrsAutomationLevel}},
                           @{name="VM Swapfile Policy"; expression={$_.VMSwapfilePolicy}},
                           @{name="Custom Fields"; expression={$_.CustomFields}},
                           @{name="Type"; expression={$type}}
            }
            "HostSystem" {
                 select  @{name="[MACHINE_NAME]"; expression={$server}},
                           @{name="[PATH]Id"; expression={$_.Id}},
                           @{name="[PATH]Name"; expression={$_.Name}},
                           @{name="Name"; expression={$_.Name}},
                           @{name="State"; expression={$_.State}},
                           @{name="VM Swapfile Datastore Id"; expression={$_.VMSwapfileDatastoreId}},
                           @{name="VM Swapfile Policy"; expression={$_.VMSwapfilePolicy}},
                           @{name="Custom Fields"; expression={$_.CustomFields}},
                           @{name="Type"; expression={$type}}
            }
            ...
  

  It returns nothing every time.  If I just run Get-inventory I collect a lot of data.  My guess is that I do something wrong in a perspective of PowerShell, not a point of view CLI.

  Any ideas?

  It's because you're not 'feed' anything in the select cmdlet.

  And the Switch statement modifies the contents of the variable $_

  And to get the type that you can use the GetType method that exists on any object.

  Get-Inventory | % {
       $type = ($_ | Get-View).gettype().Name
       $obj = $_
       switch ($type) {
            "ClusterComputeResource" {
                 $obj | select @{name="[MACHINE_NAME]"; expression={$server}},
                 @{name="[PATH]Id"; expression={$obj.Id}},
                 @{name="[PATH]Name"; expression={$obj.Name}},
                 @{name="Name"; expression={$obj.Name}},
                 @{name="HA Enabled"; expression={$obj.HAEnabled}},
                 @{name="HA Admission Control Enabled"; expression={$obj.HAAdmissionControlEnabled}},
                 @{name="HA Failover Level"; expression={$obj.HAFailoverLevel}},
                 @{name="HA Restart Priority"; expression={$obj.HARestartPriority}},
                 @{name="HA Isolation Response"; expression={$obj.HAIsolationResponse}},
                 @{name="DRS Enabled"; expression={$obj.DrsEnabled}},
                 @{name="DRS Automation Level"; expression={$obj.DrsAutomationLevel}},
                 @{name="VM Swapfile Policy"; expression={$obj.VMSwapfilePolicy}},
                 @{name="Custom Fields"; expression={$obj.CustomFields}},
                 @{name="Type"; expression={$type}}
            }
            "HostSystem" {
                 $obj | select @{name="[MACHINE_NAME]"; expression={$server}},
                 @{name="[PATH]Id"; expression={$obj.Id}},
                 @{name="[PATH]Name"; expression={$obj.Name}},
                 @{name="Name"; expression={$obj.Name}},
                 @{name="State"; expression={$obj.State}},
                 @{name="VM Swapfile Datastore Id"; expression={$obj.VMSwapfileDatastoreId}},
                 @{name="VM Swapfile Policy"; expression={$obj.VMSwapfilePolicy}},
                 @{name="Custom Fields"; expression={$obj.CustomFields}},
                 @{name="Type"; expression={$type}}
            }
       }
  }
  

• VMware HA problem with isolated host.

  Hello, we have two IBM x 3850 M2 running ESX 3.5 U4 (153875).  Both are attached via NAS (NFS) to an IBM N3600 (Netapp FAS2050C).  Each server has two NETWORK adapter configured on their system console vSwitches (team) and there is an additional private network running for the storage and vMotion (with two NIC of each).

  We have DRS and HA enabled for our cluster with two nodes with the following parameters of HA:

  • Host allowed failures: 1

  • Enable the VMs to be powered even if they violate constraints of availability

  • VM restart priority: medium

  • The host Isolation response: stop the virtual machine

  • Enable VM monitoring (high)

  If I pull the power on one of the hosts, virtual machines are automatically provisioned on the host survivor as expected.  However, if I simulate double NIC failure on one of the hosts by unplugging both the System Console env, we lack in the following behavior:

  1. On the host that has been isolated (prodsys-vm1), the logs indicate that the server has detected it is isolated and begins to shut down its virtual machine.

  2. The host of survivor (prodsys-vm2) notes that prodsys-vm1 disappeared.

  3. prodsys-vm2 saves the VM "isolated" and tries to turn on.  The following error message is observed for each VM has failed:

  [2009-07-24 13:00:17.352 'vm:/vmfs/volumes/2e5dc29c-712e74ba/Test System/Test System.vmx' 3076461472 info] Question info: Cannot open the disk '/vmfs/volumes/2e5dc29c-712e74ba/Test System/Test System.vmdk' or one of the snapshot disks it depends on.
  Reason: Device or resource busy., Id: 0 : Type : 2, Default: 0, Number of options: 1
  [2009-07-24 13:00:17.352 'BaseLibs' 21044144 info] Disconnect check in progress: /vmfs/volumes/2e5dc29c-712e74ba/Test System/Test System.vmx
  [2009-07-24 13:00:17.367 'ha-eventmgr' 3076461472 info] Event 82 : Message on Test System on prodsys-vm2.esri.com in ha-datacenter: Cannot open the disk '/vmfs/volumes/2e5dc29c-712e74ba/Test System/Test System.vmdk' or one of the snapshot disks it depends on.
  Reason: Device or resource busy.
  

  1. prodsys-vm2 then unregisters each virtual computer.

  2. Wait several minutes, but no other attempts are made to register and/or marketing the virtual machine failed.

  3. Now, if I register manually an of from the prodsys-vm2 failed VM console, it is immediately and without further interaction with me under tension.  In addition, this seems to trigger the re-registration of VM chess which is then subsequently automatically switched on without error.

  The obvious conclusion here is that prodsys-vm2 does not prodsys-vm1 enough time to stop the virtual machine before trying to restart.  I imagine that this could potentially be adjusted by getting the das.failuredetectiontime (I see a recommendation of the 1960s).

  A few questions though:

  • Why don't prodsys-vm2 try again to register and start the virtual machine failed after the first attempt?

  • Why when I joined one manually it suddenly decided to register and start up of the rest on its own?

  • Is it possible to keep my time failuredetection low (for faster recovery) and still be able to avoid this situation?  I could see a situation where maybe even 60s would be high enough.  It seems that this should be handled with more elegance that just get a time-out value...

  Of course, there are some fixes that might apply to our facilities and those who can give a try.  Will also lift it in support, but hoping someone out there might have some ideas.

  Thank you!

  Sorry,

  I forgot the second half of this message:

  VMware High Availability (HA)

  Virtual Machines using a NFS data store could fail after an HA failover event

  When you have the overcommitment of memory with virtual machines on a NFS datastore, it creates a vswp file, which is a size swap file non-zero. In this scenario if HA failover events occur and the AP are defined on THAT VM leave power on, you may have a failure of virtual machine on the host where the virtual machine was originally executed before the HA event.

  If you don't have an overcommitment of memory with virtual machines on a datastore NFS, so HA failover events occur with the parameter THAT VM leave it turned on, in addition to the migration of the virtual machine running on the original host may fail.

  Solution: Apply Patch ESX350-200905401-BG to ESX Server 3.5 and hosts Patch ESXe350-200905401-I-BG of ESX Server 3i version 3.5 host computers.

  When a Virtual Machine running on a NAS data store is configured to be stopped or left turned on in response to the isolation of the host, the Virtual Machine may attempt to run simultaneously on two hosts an event of network isolation

  Multiple network that causes failure host isolation and loss of access to the network for the data store, if a virtual machine is configured with the setting stop VM or VM leave it turned on in case of isolation of the host, the virtual machine may not respond indefinitely. As HA tries to turn off the virtual machine and restart on another host, two instances of the virtual machine may appear in the VI Client. There is no data corruption, because HA and VMFS properly control access to the data of the virtual machine, but the original virtual machine becomes inadmissible. After access to the data store is restored on the isolated host, the original virtual machine can be manually powered down.

  Solution: In environments NFS or iSCSI, select power off the virtual machine as the response of virtual machine in a cluster by default if a host is isolated.

• Set the priority to restart HA of a csv file

  Hello

  I have a problem HA restart the priority of a CSV on the VMs.

  My share of script is like this:

  If ($Export)

  {

  # Export to CSV

  $mycluster = get-Cluster-name $Cluster

  $mycluster. ExtensionData.Configuration.DasVmConfig |

  Select @{N = "VM"; E = {Get-view $_.} Key - the name of the property. {{Select - ExpandProperty name}}.

  @{N = "RestartPriority"; E={$_. RestartPriority}} |

  {Csv Export $Path\HARestartPrio.csv - NoTypeInformation - UseCulture}

  If ($Set)

  {

  # Put csv

  $Import = import-Csv $Path\HARestartPrio.csv

  foreach ($line in $Import)

  {set-VM - vm $line. "" VM "-HARestartPriority $line. {{"" RestartPriority "-confirm: $false}}

  When I put the priority, the CLI will give an error:

  The parameter HARestartPriority can not check. The Argument is Null or is empty

  What is the problem in my script? You have any ideas?

  It is not the Export-Csv is the problem in my humble opinion, you must also specify the Import-Csv cmdlet UseCulture switch.