vCenter Server Heartbeat Protection Levels

This product protects the vCenter Server by two instances, one of them send alive messages (basically pings) over the VMware Channel, and in case of failure, initiating and automatic switchover.

The 5 levels protected by Hearbeat are:


-Server Protection – vCenter Server Heartbeat provides continuous availability to end users through a
hardware failure scenario or operating system crash. Additionally, vCenter Server Heartbeat ensures
users are provided with a replica server should the production server fail.

-Network Protection – vCenter Server Heartbeat proactively monitors the network by polling up to three
predefined nodes to ensure that the active server is visible on the network.

-Application Protection – vCenter Server Heartbeat maintains the application environment ensuring that
applications and services stay alive and available on the network.

-Performance Protection – vCenter Server Heartbeat proactively monitors system performance attributes
to ensure the system administrator is notified of problems. Additionally, it can be configured to take

-Data Protection – vCenter Server Heartbeat intercepts all data written by users and applications, and
maintains a copy of the data on the passive server that can be used in the event of a failure.

Apple patenta una tarjeta SIM que le daría el control del cliente frente a las operadoras

Un motivo mas para no vivir y morir con la manzanita a cuestas...

"Apple ha patentado una tarjeta SIM virtual que, embebida en los teléfonos móviles, quitaría el contr...

http://www.elpais.com/articulo/tecnologia/Apple/patenta/tarjeta/SIM/le/daria/control/cliente/frente/operadoras/elpeputec/20111114elpeputec_1/Tes
PABLO CRUCES
http://virtualshocks.blogspot.com

Enviado desde mi BlackBerry® de Vodafone

VMware Converter Standalone 5 does not support conversion over a WAN

In the new version 5 of vSphere, Converters is missing like a plugin, you need to install it only Standalone mode. It´s annoying for me that conversions over wan might be done in local and move after to the destination site..... even when vmotion increase the latency from 5ms to 10ms in the new vSphere 5

About X2V over WAN:


Timeout on SSL handshake when converting over a WAN link
Converter Standalone does not support conversion over a WAN. When trying to perform a conversion over a WAN link, you might experience an SSL timeout because the timeout for SSL handshakes is two minutes.
Workaround:

1. To avoid the two-minute handshake, perform a conversion to a hosted destination machine (for example, Workstation) in the same LAN.
2. Copy the temporary virtual machine and send it over the WAN to the remote site.
   If the intended destination is a Workstation virtual machine, this completes the process.
3. If the intended destination is ESX, import the Workstation virtual machine to the ESX server.

vCenter Server Heartbeat 6.4 Split-Brain Avoidance

   El problema que puede ocurrir al tener dos sites con vCenter protegido con Heartbeat, es que se llegue a perder la conectividad entre ambos y se produzca una bicefalia o split-brain, en la que ambos vCenter se creen que tienen el control de la infraestructura. 

Para evitarlo, VMware nos deja una serie de pasos en la configuración respecto a la prevencion del failover:

 "To enable Split-brain Avoidance, open the Server: Monitoring page in the vCenter Server Heartbeat Console, click Configure Failover, and select Prevent failover if channel heartbeat is lost but Active server is still visible to other servers (recommended)."

Tambien debemos configurar una serie de ip´s de gestion para que entre ambos sites se hagan ping las ethernet para comprobar el estado entre el site pasivo y el activo:

1 Open the network properties for the Principal (Public) network connection.


2 Double-click TCP/IP to display the properties.


3 Click Advanced.


4 Enter an additional (currently unused) IP address in the table.

5 Reposition the IP addresses in the list so that the additional (Management) IP address appears first, and the Principal (Public) network address (by which clients connect to the server) appears second.

6 Click OK on all three dialogs to accept the configuration changes to the network connection.


7 After completing all of the steps click Next or Finish.

El servidor activo debera responder antes del valor de tiempo fijado en el "Failover timeout" para prevenir que el failover ocurra, que esta fijado en 60 segundos por defecto.

1 Click Configure Failover to open the Server Monitoring: Failover Configuration dialog.


2 Type a new numeric value (seconds) in the Failover timeout text box or use the arrow buttons to set a new value.


3 Mark or clear the check boxes to select the actions to take if the specified Failover timeout is exceeded. Click OK to finish.