Re: MSCS DR

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

We would be using snapshot clones. EMC told me that synchronous
replication was not supported in any way shape or form!!!

I will check out the link

Thanks

AJ
John Fullbright [MVP] wrote:
Async replication of live data? fully supported? I guess you haven't read
KB 895847.

"Support policies for the different kinds of replication mechanism

Asynchronous replication

Any data that has been replicated asynchronously is supported only by the
storage vendor. When you replicate Exchange data by using asynchronous
replication, the vendor who provides your replication mechanism must support
the Exchange data at the replication destination. We make no claims as to
the reliability of or the performance of Exchange solutions that use
asynchronous replication. We use the following criteria to support
Exchange-related issues that you may experience in an environment where you
use asynchronous replication: "

Is that what you mean by "fully supported"?

The only way that I know of to use async replication in a fully supported
solution is to use data that is not live - ie. snapshots. You can see this
here:

http://www.microsoft.com/technet/technetmag/issues/2006/10/FailoverClusters/default.aspx

Note the concluding comment: "We achieved our goal of building failover
clusters for Exchange to provide a disaster recovery solution that has a
relatively high RTO and RPO, is fully supported by Microsoft, and avoids the
complexity of full geoclustering."





"AndyJ" <andyjones99@xxxxxxxxxxxxx> wrote in message
news:1163149156.984465.72970@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello All

I am posting in this forum in hope that an MSCS expert can help me out
here. I posted in the Exchange forum but didn't get the answers I was
after so here goes:

Here is the scenario:

We have an Exchange 2003 cluster stretched across two locations in an
Active/Passive configuration. Both cluster nodes talk to the primary
SAN array. The primary SAN is mirrored to the DR location using Aysnc
replication (logs, stores and Quorom) and this is fully supported by MS
at this point.

Here is the question:

In the event that we loose the primary site (A node and SAN) will I be
able to present the DR SAN disk array to the node in the DR location
and bring the EVS up?

I am thinking that MSCS might see the DR disks as a new disk resource
and will choke on this.

Any thoughts. I have been discussing this with the storage vendor but
they cannot answer this question.

Thanks

AJ


.

Relevant Pages

  • Re: MSCS DR
    ... but LifeKeeper for Exchange can easily be ... quality of the support they receive from the vendor, ... an incompatibility with the third-party replication mechanism. ... CX400 arrays so it looks as though we will be looking at Replistor ...
    (microsoft.public.windows.server.clustering)
  • Re: MSCS DR
    ... more money for a decent standalone DR Exchange box. ... all Exchange DR recovery and synchronous replication is not supported ... "Support policies for the different kinds of replication mechanism ... Asynchronous replication ...
    (microsoft.public.windows.server.clustering)
  • Re: MSCS DR
    ... more money for a decent standalone DR Exchange box. ... all Exchange DR recovery and synchronous replication is not supported ... "Support policies for the different kinds of replication mechanism ... Asynchronous replication ...
    (microsoft.public.windows.server.clustering)
  • Re: MSCS DR
    ... Regarding your question, EMC have ... more money for a decent standalone DR Exchange box. ... all Exchange DR recovery and synchronous replication is not supported ... "Support policies for the different kinds of replication mechanism ...
    (microsoft.public.windows.server.clustering)
  • Re: MSCS DR
    ... Regarding your question, EMC have ... more money for a decent standalone DR Exchange box. ... all Exchange DR recovery and synchronous replication is not supported ... "Support policies for the different kinds of replication mechanism ...
    (microsoft.public.windows.server.clustering)