>Why do you call CCR a DR solution? shouldnt it be a combination of DR and
>HA? from my udnerstanding if i am using CCR, i have two seperate CMS that
>dont share any data. If CCR is reunning on Windows server 2008, then cant i
>setup the CMS in different datacenters? wouldt this be considered DR and HA?
No way Skip, CCR is HA, not DR. I double checked and that's what I
said, or at least what I intended to say.
CCR is not intended to be DR. Sure, if you want to set up CCR in two
data centers you need to do that as part of an overall infrastructure
strategy. You've been around long enough not to fall into the newbie
trap of blinkering yourself to solving something purely for Exchange
and not look at the wider picture.
If you have a well connected pair of data centers (and you really,
really, need that if you are planning on using CCR because you also
need the same level of connectivity for your Oracle, SQL, SAP and file
sharing requirements) then CCR is in the "same" data center; it's just
that you're in two buildings separated by a big fat glass pipe. If
your connection between A and B isn't too good then you run the risk
of diverging and CCR is the last thing you want to look at.
Big picture skip, you know the score.
skip - 23 Jul 2008 18:13 GMT
Mark
Can CCR be configured as active/passive? if so then couldnt i run the active
CMS in datacenter A and the passive CMS in datacenter B. In the unlikely
event datacenter A experiences a complete melt down, then shouldnt i be able
to fail over to the CMS in datacenter B? i know i would need DNS, AD, HT
and CAS server in each datacenter, but if i can do this i would think this
would be considered a DR solution? Where am i going wrong with this?
>>Why do you call CCR a DR solution? shouldnt it be a combination of DR and
>>HA? from my udnerstanding if i am using CCR, i have two seperate CMS that
[quoted text clipped - 19 lines]
>
> Big picture skip, you know the score.