<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Hyper-V Backup Solution</title>
	<atom:link href="http://www.backupassist.com/blog/support/hyper-v-backup-solution/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.backupassist.com/blog/support/hyper-v-backup-solution/</link>
	<description>BackupAssist blog</description>
	<lastBuildDate>Sun, 22 Jan 2012 22:14:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Brian Collis</title>
		<link>http://www.backupassist.com/blog/support/hyper-v-backup-solution/comment-page-1/#comment-504</link>
		<dc:creator>Brian Collis</dc:creator>
		<pubDate>Fri, 17 Sep 2010 17:26:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.backupassist.com/blog/support/hyper-v-backup-solution/#comment-504</guid>
		<description>Hi Jeff
Look at putting your VM&#039;s or at least the data vhd on an iSCSI box.  When the first server fails and you start the second server, all the data will be current at the time of the 1st server failing.  It would also reduce traffic caused by the &quot;live&quot; backup between servers.  A neat box I have come across that supports iSCSI, and is not expensive is the Ctera C200.  (have not used it in this senario, and it does a lot more than just iSCSI).  If you don&#039;t want to use external hardware you could use FRS included with Server 2003/2008.  Configure an DFS/FRS share on the two servers.  Point your clients to the FRS, they will find the closest/working server publishing the DFS share point.  (DFS/FRS replicate file changes between all servers hosting the DFS share)
Hi Jeff
Look at putting your VM&#039;s or at least the data vhd on an iSCSI box.  When the first server fails and you start the second server, all the data will be current at the time of the 1st server failing.  It would also reduce traffic caused by the &quot;live&quot; backup between servers.  A neat box I have come across that supports iSCSI, and is not expensive is the Ctera C200.  (have not used it in this scenario, and it does a lot more than just iSCSI).  If you don&#039;t want to use external hardware you could use FRS included with Server 2003/2008.  Configure an DFS/FRS share on the two servers.  Point your clients to the FRS, they will find the closest/working server publishing the DFS share point.  (DFS/FRS replicate file changes between all servers hosting the DFS share)

Brian Collis
Computer Net-WORKS Ltd</description>
		<content:encoded><![CDATA[<p>Hi Jeff<br />
Look at putting your VM&#8217;s or at least the data vhd on an iSCSI box.  When the first server fails and you start the second server, all the data will be current at the time of the 1st server failing.  It would also reduce traffic caused by the &#8220;live&#8221; backup between servers.  A neat box I have come across that supports iSCSI, and is not expensive is the Ctera C200.  (have not used it in this senario, and it does a lot more than just iSCSI).  If you don&#8217;t want to use external hardware you could use FRS included with Server 2003/2008.  Configure an DFS/FRS share on the two servers.  Point your clients to the FRS, they will find the closest/working server publishing the DFS share point.  (DFS/FRS replicate file changes between all servers hosting the DFS share)<br />
Hi Jeff<br />
Look at putting your VM&#8217;s or at least the data vhd on an iSCSI box.  When the first server fails and you start the second server, all the data will be current at the time of the 1st server failing.  It would also reduce traffic caused by the &#8220;live&#8221; backup between servers.  A neat box I have come across that supports iSCSI, and is not expensive is the Ctera C200.  (have not used it in this scenario, and it does a lot more than just iSCSI).  If you don&#8217;t want to use external hardware you could use FRS included with Server 2003/2008.  Configure an DFS/FRS share on the two servers.  Point your clients to the FRS, they will find the closest/working server publishing the DFS share point.  (DFS/FRS replicate file changes between all servers hosting the DFS share)</p>
<p>Brian Collis<br />
Computer Net-WORKS Ltd</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Nay</title>
		<link>http://www.backupassist.com/blog/support/hyper-v-backup-solution/comment-page-1/#comment-408</link>
		<dc:creator>Jeff Nay</dc:creator>
		<pubDate>Thu, 22 Oct 2009 15:32:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.backupassist.com/blog/support/hyper-v-backup-solution/#comment-408</guid>
		<description>I am looking for a live backup method that would include backing up a VM hosted on one Hyper-V Server to another Hyper-V Server capable of hosting the VM should a failure occure on the first host, the second host would have a live up to date copy of the VM that could easily be started. This would allow for an simple failover method without clustering.

I would of course also want to keep a historical backups of that VM on external drives.</description>
		<content:encoded><![CDATA[<p>I am looking for a live backup method that would include backing up a VM hosted on one Hyper-V Server to another Hyper-V Server capable of hosting the VM should a failure occure on the first host, the second host would have a live up to date copy of the VM that could easily be started. This would allow for an simple failover method without clustering.</p>
<p>I would of course also want to keep a historical backups of that VM on external drives.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

