<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Fault Tolerance on myvirtualcloud.net</title><link>https://myvirtualcloud.net/tags/fault-tolerance/</link><description>Recent content in Fault Tolerance on myvirtualcloud.net</description><generator>Hugo</generator><language>en-us</language><copyright>Andre Leibovici</copyright><lastBuildDate>Wed, 16 Sep 2009 04:18:07 +0000</lastBuildDate><atom:link href="https://myvirtualcloud.net/tags/fault-tolerance/index.xml" rel="self" type="application/rss+xml"/><item><title>(Take Care) vSphere Virtual Machine Upgrade Process</title><link>https://myvirtualcloud.net/take-care-vsphere-virtual-machine-upgrade-process/</link><pubDate>Wed, 16 Sep 2009 04:18:07 +0000</pubDate><guid>https://myvirtualcloud.net/take-care-vsphere-virtual-machine-upgrade-process/</guid><description>&lt;p&gt;I decided to name this post as "Take Care" as I found myself looking for promissed VSphere features that will not be avaiable in most Corporate environments therefore you should prepare yourself, and your environment.&lt;/p&gt;&#10;&lt;p&gt;While I as upgrading my VM's from 3.x to VSphere I based my work on this great step-by-step article from &lt;a href="http://twitter.com/scott_lowe" target="_blank"&gt;@scot_lowe&lt;/a&gt; Scott Lowe's (see link bellow). The main reason for upgrading was related to the ability to run the new VMXNET3, Paravirtualized SCSI and Hot-Add/Hot-Plug. I also wanted to customize my templates to use hardware v7.&lt;/p&gt;</description></item><item><title>VMware View Higher Levels of Availability</title><link>https://myvirtualcloud.net/vmware-view-higher-levels-of-availability/</link><pubDate>Sat, 12 Sep 2009 09:21:00 +0000</pubDate><guid>https://myvirtualcloud.net/vmware-view-higher-levels-of-availability/</guid><description>&lt;p&gt;I have been working with VMware View since version 2.0, and I have to admit that VMware has made significant improvements on version 3.1.&lt;/p&gt;&#10;&lt;p&gt;The Connection Broker availability has always been a point of discussion so VMware released a replica server mode. It works with ADAM&amp;#160; (Active Directory Application Mode) that is replicated to a secondary server and vice-versa. Despite that will solve the problems for most of the administrators I was imagining how I could improve the design proposed by VMware. &lt;br /&gt; &lt;br /&gt;I am administrating a large VSphere cluster and another small VI3 cluster (only two ESXi hosts). Due to application compatibility VMView had to stay on VI3 and this cluster is now dedicated to VMView as everything else has already been migrated to VSphere. (VMware promised compatibility with VSphere until the end of year).&lt;/p&gt;</description></item></channel></rss>