<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://192.168.2.20/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Moving Virtual Machines Between Servers with Microsoft Virtualisation Technology (Virtual Server)</title><link>http://192.168.2.20/blogs/doverton/archive/2007/07/23/moving-virtual-machines-between-servers-with-microsoft-virtualisation-technology-virtual-server.aspx</link><description>I saw this and thought I would share it. Given the rumours around what can and cannot be done with Virtual Server and the technologies coming with Longhorn Windows Server 2008. I did not realise that we offered &amp;quot;Quick&amp;quot; migrations - a few seconds</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator><item><title>re: Moving Virtual Machines Between Servers with Microsoft Virtualisation Technology (Virtual Server)</title><link>http://192.168.2.20/blogs/doverton/archive/2007/07/23/moving-virtual-machines-between-servers-with-microsoft-virtualisation-technology-virtual-server.aspx#7684</link><pubDate>Tue, 23 Dec 2008 20:56:53 GMT</pubDate><guid isPermaLink="false">72050d9c-4f41-4a16-9f70-ebbf2c98a2c7:7684</guid><dc:creator>David Overton</dc:creator><description>&lt;p&gt;Alex,&lt;/p&gt;
&lt;p&gt;You are and you are not right. &amp;nbsp;One of my jobs in the past was building mission critical solutions and you always have to expect things to fail as part of the design, so even with this limitation in Hyper-V today a very highly available solution can be delivered - certainly as highly available as a solution based on a Live Migration scenario.&lt;/p&gt;
&lt;p&gt;However, to answer your point - yes, Microsoft&amp;#39;s own products will deliver this in the future. &amp;nbsp;Most users do not have a solution that is singuarly dependent on a server that if it fails will cost then a lot of money. &amp;nbsp;Live migration gives you no extra benefit vs a system failing, where as clustering and good design can.&lt;/p&gt;
&lt;p&gt;ttfn&lt;/p&gt;
&lt;p&gt;David&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://192.168.2.20/aggbug.aspx?PostID=7684" width="1" height="1"&gt;</description></item><item><title>re: Moving Virtual Machines Between Servers with Microsoft Virtualisation Technology (Virtual Server)</title><link>http://192.168.2.20/blogs/doverton/archive/2007/07/23/moving-virtual-machines-between-servers-with-microsoft-virtualisation-technology-virtual-server.aspx#7660</link><pubDate>Thu, 18 Dec 2008 16:24:47 GMT</pubDate><guid isPermaLink="false">72050d9c-4f41-4a16-9f70-ebbf2c98a2c7:7660</guid><dc:creator>Alex</dc:creator><description>&lt;p&gt;Seconds of down time can cause autosys transactions to drop for a second or more. A failed transaction job of the financial type could cost the company ALOT of money. &lt;/p&gt;
&lt;p&gt;Is microsoft working on a solution for this where there will be NO downtime moving VM&amp;#39;s from one host to another?&lt;/p&gt;
&lt;p&gt;Thank You,&lt;/p&gt;
&lt;p&gt;Alex&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://192.168.2.20/aggbug.aspx?PostID=7660" width="1" height="1"&gt;</description></item></channel></rss>