<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Get a feel for enterprise block level replication using drbd</title>
	<atom:link href="http://martincarstenbach.wordpress.com/2012/07/02/get-a-feel-for-enterprise-block-level-replication-using-drbd/feed/" rel="self" type="application/rss+xml" />
	<link>http://martincarstenbach.wordpress.com/2012/07/02/get-a-feel-for-enterprise-block-level-replication-using-drbd/</link>
	<description>Trying to explain complex things in simple terms</description>
	<lastBuildDate>Sun, 19 May 2013 17:16:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: goran</title>
		<link>http://martincarstenbach.wordpress.com/2012/07/02/get-a-feel-for-enterprise-block-level-replication-using-drbd/#comment-2413</link>
		<dc:creator><![CDATA[goran]]></dc:creator>
		<pubDate>Fri, 13 Jul 2012 12:10:57 +0000</pubDate>
		<guid isPermaLink="false">http://martincarstenbach.wordpress.com/?p=1405#comment-2413</guid>
		<description><![CDATA[Hi Martin,

I absolutely agree with your statement &quot;it is ultimately the DBA’s responsibility to get the system back&quot; ... and everybody expect that from us!

As of this, I am pretty resistant on using storage replication ... my prefered option is DataGuard.

I had a horror story couple a years ago when our team was persuaded by storage guys to use it for replicating database from Frankfurt to Munich (Germany) ... and never again.

Unless I have a very very deep insight into details of underlaying storage technology and thoroughly tested, I choose safe way: DataGuard ... in case I can decide which solution ... if not, then good luck ;-)

Further, from organization point it&#039;s better to have competence and responsibility in only one team for switch/failover rather then having it spread across different organizational units.

regards,
goran]]></description>
		<content:encoded><![CDATA[<p>Hi Martin,</p>
<p>I absolutely agree with your statement &#8220;it is ultimately the DBA’s responsibility to get the system back&#8221; &#8230; and everybody expect that from us!</p>
<p>As of this, I am pretty resistant on using storage replication &#8230; my prefered option is DataGuard.</p>
<p>I had a horror story couple a years ago when our team was persuaded by storage guys to use it for replicating database from Frankfurt to Munich (Germany) &#8230; and never again.</p>
<p>Unless I have a very very deep insight into details of underlaying storage technology and thoroughly tested, I choose safe way: DataGuard &#8230; in case I can decide which solution &#8230; if not, then good luck ;-)</p>
<p>Further, from organization point it&#8217;s better to have competence and responsibility in only one team for switch/failover rather then having it spread across different organizational units.</p>
<p>regards,<br />
goran</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Bach</title>
		<link>http://martincarstenbach.wordpress.com/2012/07/02/get-a-feel-for-enterprise-block-level-replication-using-drbd/#comment-2350</link>
		<dc:creator><![CDATA[Martin Bach]]></dc:creator>
		<pubDate>Thu, 05 Jul 2012 21:14:45 +0000</pubDate>
		<guid isPermaLink="false">http://martincarstenbach.wordpress.com/?p=1405#comment-2350</guid>
		<description><![CDATA[Thank you!

And you were right, I have updated the post.

Martin]]></description>
		<content:encoded><![CDATA[<p>Thank you!</p>
<p>And you were right, I have updated the post.</p>
<p>Martin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kabbo</title>
		<link>http://martincarstenbach.wordpress.com/2012/07/02/get-a-feel-for-enterprise-block-level-replication-using-drbd/#comment-2336</link>
		<dc:creator><![CDATA[Kabbo]]></dc:creator>
		<pubDate>Wed, 04 Jul 2012 19:27:10 +0000</pubDate>
		<guid isPermaLink="false">http://martincarstenbach.wordpress.com/?p=1405#comment-2336</guid>
		<description><![CDATA[Hi Martin,

As usual, I always read your very nice and up to date articles, bravo to you and keep up the good job of informing your fellow Database Analysts  like myself. I just notice a very tiny &quot;typo&quot;, I believe. You might want look at this:

The domUs are Oracle Linux 6.2 with kernel 2.6.32-300.3.1.el6uek.x86_64, named ol62drbd1 and ol62drbd1.   The second hostname should be ol62drbd2, as opposed to 1. 

thanks,
Kabbo]]></description>
		<content:encoded><![CDATA[<p>Hi Martin,</p>
<p>As usual, I always read your very nice and up to date articles, bravo to you and keep up the good job of informing your fellow Database Analysts  like myself. I just notice a very tiny &#8220;typo&#8221;, I believe. You might want look at this:</p>
<p>The domUs are Oracle Linux 6.2 with kernel 2.6.32-300.3.1.el6uek.x86_64, named ol62drbd1 and ol62drbd1.   The second hostname should be ol62drbd2, as opposed to 1. </p>
<p>thanks,<br />
Kabbo</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Noons</title>
		<link>http://martincarstenbach.wordpress.com/2012/07/02/get-a-feel-for-enterprise-block-level-replication-using-drbd/#comment-2317</link>
		<dc:creator><![CDATA[Noons]]></dc:creator>
		<pubDate>Tue, 03 Jul 2012 04:47:14 +0000</pubDate>
		<guid isPermaLink="false">http://martincarstenbach.wordpress.com/?p=1405#comment-2317</guid>
		<description><![CDATA[Martin, modern storage-level replication applied to databases uses a concept called &quot;consistency groups&quot; for synchronous replication that ensures some if not most of the disaster scenarios you described will not happen without awareness of a problem being there.
It is essential to learn the details of all that is possible nowadays in modern SAN h/w and sw before claiming that it can or cannot be done or is &quot;dangerous&quot; or not.  
I do recall the horror stories of youre, let me assure you most of those scenarios are gone.  It is a complex and wide field, believe me: I&quot;ve been dabbling on it for the last 3 years and although I don&#039;t profess to &quot;know-it-all&quot;, I do recognize it encompasses a lot more than I initally thought.
And there is more than just synchronous replication possible.  Asynchronous is very viable and reliable method for things like s/w storage, archive logs, FRA, etcetc.
Particularly if preceeded by the caution of taking a snapshot on the remote site before effecting the replication - a la &quot;before image&quot;.  And so on.  
A lot can be said about this subject, thanks for taking the step to talk about it.]]></description>
		<content:encoded><![CDATA[<p>Martin, modern storage-level replication applied to databases uses a concept called &#8220;consistency groups&#8221; for synchronous replication that ensures some if not most of the disaster scenarios you described will not happen without awareness of a problem being there.<br />
It is essential to learn the details of all that is possible nowadays in modern SAN h/w and sw before claiming that it can or cannot be done or is &#8220;dangerous&#8221; or not.<br />
I do recall the horror stories of youre, let me assure you most of those scenarios are gone.  It is a complex and wide field, believe me: I&#8221;ve been dabbling on it for the last 3 years and although I don&#8217;t profess to &#8220;know-it-all&#8221;, I do recognize it encompasses a lot more than I initally thought.<br />
And there is more than just synchronous replication possible.  Asynchronous is very viable and reliable method for things like s/w storage, archive logs, FRA, etcetc.<br />
Particularly if preceeded by the caution of taking a snapshot on the remote site before effecting the replication &#8211; a la &#8220;before image&#8221;.  And so on.<br />
A lot can be said about this subject, thanks for taking the step to talk about it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
