<?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/"
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: IBM DS4700 Model 70, VMware ESX 3.5 and Site Recovery Manager</title>
	<atom:link href="http://daveveness.wordpress.com/2009/01/09/ibm-ds4700-model-70-vmware-esx-35-and-site-recovery-manager/feed/" rel="self" type="application/rss+xml" />
	<link>http://daveveness.wordpress.com/2009/01/09/ibm-ds4700-model-70-vmware-esx-35-and-site-recovery-manager/</link>
	<description>Yes.. another IT guy with a blog....</description>
	<lastBuildDate>Fri, 25 Sep 2009 00:46:29 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andre</title>
		<link>http://daveveness.wordpress.com/2009/01/09/ibm-ds4700-model-70-vmware-esx-35-and-site-recovery-manager/#comment-9</link>
		<dc:creator>Andre</dc:creator>
		<pubDate>Fri, 25 Sep 2009 00:46:29 +0000</pubDate>
		<guid isPermaLink="false">http://daveveness.wordpress.com/?p=10#comment-9</guid>
		<description>G&#039;day Dave,

I hope you and your other half are doing well.

This was definitely a very interesting project under some pretty tight timelines. Good on you for putting this out there. I only came across this site randomly looking for something else. It will definitely add value for anyone else looking to implement a similar solution as at the time saying doco was light is a bit of an understatement. Dave definitely knows his stuff guys.

Regards,

Andre</description>
		<content:encoded><![CDATA[<p>G&#8217;day Dave,</p>
<p>I hope you and your other half are doing well.</p>
<p>This was definitely a very interesting project under some pretty tight timelines. Good on you for putting this out there. I only came across this site randomly looking for something else. It will definitely add value for anyone else looking to implement a similar solution as at the time saying doco was light is a bit of an understatement. Dave definitely knows his stuff guys.</p>
<p>Regards,</p>
<p>Andre</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave V</title>
		<link>http://daveveness.wordpress.com/2009/01/09/ibm-ds4700-model-70-vmware-esx-35-and-site-recovery-manager/#comment-5</link>
		<dc:creator>Dave V</dc:creator>
		<pubDate>Tue, 21 Apr 2009 10:44:27 +0000</pubDate>
		<guid isPermaLink="false">http://daveveness.wordpress.com/?p=10#comment-5</guid>
		<description>Sorry for the late responses on the above comments;

Erik, the customers requirements were to optimise the available space in the DR SAN for some other backup purposes. Agreed on your points, ideally, given the right environment, the best protection would be provided by using sync replication and matching RAID sets. The performance on the Prod side was of the most priority and therefore the decision was to use Async replication.

Imran, yes we had to break away from best practice and merge the fabrics. Unfortunate outcome, and would definately not recommend using a Model 70 to do SRM.

Thank you both for the comments!</description>
		<content:encoded><![CDATA[<p>Sorry for the late responses on the above comments;</p>
<p>Erik, the customers requirements were to optimise the available space in the DR SAN for some other backup purposes. Agreed on your points, ideally, given the right environment, the best protection would be provided by using sync replication and matching RAID sets. The performance on the Prod side was of the most priority and therefore the decision was to use Async replication.</p>
<p>Imran, yes we had to break away from best practice and merge the fabrics. Unfortunate outcome, and would definately not recommend using a Model 70 to do SRM.</p>
<p>Thank you both for the comments!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Imran</title>
		<link>http://daveveness.wordpress.com/2009/01/09/ibm-ds4700-model-70-vmware-esx-35-and-site-recovery-manager/#comment-4</link>
		<dc:creator>Imran</dc:creator>
		<pubDate>Mon, 20 Apr 2009 13:52:28 +0000</pubDate>
		<guid isPermaLink="false">http://daveveness.wordpress.com/?p=10#comment-4</guid>
		<description>Hi I should have read this before I got stuck with the same prblems. Can i ask what you did about problem number 1. I have a same situation where i have 1 port availble per controller connected to seperate switches. Do i have to merge the fabrics?</description>
		<content:encoded><![CDATA[<p>Hi I should have read this before I got stuck with the same prblems. Can i ask what you did about problem number 1. I have a same situation where i have 1 port availble per controller connected to seperate switches. Do i have to merge the fabrics?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik Zandboer</title>
		<link>http://daveveness.wordpress.com/2009/01/09/ibm-ds4700-model-70-vmware-esx-35-and-site-recovery-manager/#comment-3</link>
		<dc:creator>Erik Zandboer</dc:creator>
		<pubDate>Fri, 20 Feb 2009 09:37:22 +0000</pubDate>
		<guid isPermaLink="false">http://daveveness.wordpress.com/?p=10#comment-3</guid>
		<description>Hi,

You state that you have a mix of RAID10/RAID5 on the production site, and that you could consider to replicate to all RAID5 for storage optimization. But beware!!! If your replication is synchronous, you will loose performance (each write to RAID10 has to be committed to the RAID5 on the DR site as well before the write completes). Caching on the DR site will help some, but not in the end as cache fills up.

Asynchronous replication... I would stay away from it (I have experience with Sun x6140 which is basically the same unit I think), and asynchronous replication leaves you nowhere when the WAN &quot;breaks&quot; all of a sudden... (some blocks replicated, others not)... Not what you want when you implement for DR. Just my 2cts.</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>You state that you have a mix of RAID10/RAID5 on the production site, and that you could consider to replicate to all RAID5 for storage optimization. But beware!!! If your replication is synchronous, you will loose performance (each write to RAID10 has to be committed to the RAID5 on the DR site as well before the write completes). Caching on the DR site will help some, but not in the end as cache fills up.</p>
<p>Asynchronous replication&#8230; I would stay away from it (I have experience with Sun x6140 which is basically the same unit I think), and asynchronous replication leaves you nowhere when the WAN &#8220;breaks&#8221; all of a sudden&#8230; (some blocks replicated, others not)&#8230; Not what you want when you implement for DR. Just my 2cts.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
