driskollt
asked on
Exchange 2010 DAG and third-party replication mode
I'm just doing some research before an implementation in a few months...
When you enable third-party replication for a DAG, does it disable all of the Exchange replication features?
I was wondering if it was possible to:
Have a local DAG copy replicated using the built-in Exchange replication, but have the remote copy replicated using third-party replication.
When you enable third-party replication for a DAG, does it disable all of the Exchange replication features?
I was wondering if it was possible to:
Have a local DAG copy replicated using the built-in Exchange replication, but have the remote copy replicated using third-party replication.
Glen Knight
Why would you want to and what 3rd party tool would you be using?
ASKER
We use RecoverPoint for our Exchange replication. We use it because it saves a ton of bandwidth, as well as gives us instantaneous access to different points-in-time which gives us a quick method to recover from in the event of data corruption.
I know EMC has an enabler for Exchange 2010 to handle all of the Exchange functions, but I mainly want to know if third-party replication and the built-in replication are even an option for a DAG. Or is it one or the other?
I know EMC has an enabler for Exchange 2010 to handle all of the Exchange functions, but I mainly want to know if third-party replication and the built-in replication are even an option for a DAG. Or is it one or the other?
I would suggest it's one or the other, doubling up the replication is destined for trouble.
It is totally possible, I do have customers that use exchange 2010 in different location with third-party replication tools like SAN replication
what you should know is that
Ithird-party data replication should support the Third Party Replication API in Exchange 2010,
you must create the DAG in third party replication mode by using the New-DatabaseAvailabilityGr
what you should know is that
Ithird-party data replication should support the Third Party Replication API in Exchange 2010,
you must create the DAG in third party replication mode by using the New-DatabaseAvailabilityGr
ASKER
I'm figuring it probably is one or the other too but I can't find anything that says definitively.
oh and yes the built-in exchange replication will be disabled (i.e log shipping)
it is, once the dag is created with ThirdPartyReplication parameter the log shipping is disabled
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Thanks.
I saw both of those articles but just wanted to hear from some people who have actually worked on Exchange 2010.
Most people I query about anything 2010 are pretty much unaware right now.
I'll testlab everything in a couple of weeks, tinker around and break a few things.
I saw both of those articles but just wanted to hear from some people who have actually worked on Exchange 2010.
Most people I query about anything 2010 are pretty much unaware right now.
I'll testlab everything in a couple of weeks, tinker around and break a few things.
ASKER
I got the official answer from EMC.
Synchronous replication is required for use with Replication Enabler for Exchange. It's a requirement of Microsoft - If you're using third party mode, then synch is required. I can always replicate asynch my data, it just can't be a DAG copy in third party mode.
It looks like I'll probably end up using DAG for my local replicatiion, and RecoverPoint for my remote site and ESEUTIL to recover the remote database. I've tested that and it's a quick failover process for the remote copy.
Synchronous replication is required for use with Replication Enabler for Exchange. It's a requirement of Microsoft - If you're using third party mode, then synch is required. I can always replicate asynch my data, it just can't be a DAG copy in third party mode.
It looks like I'll probably end up using DAG for my local replicatiion, and RecoverPoint for my remote site and ESEUTIL to recover the remote database. I've tested that and it's a quick failover process for the remote copy.